Email dan DNS for Firebase

medium6 checks

Email authentication protects the brand, not the website. SPF, DMARC, DKIM, DNSSEC and CAA are cheap controls that stop spoofing and rogue certificates.

What Firebase must have

  • SPF record ending in -all with every legitimate sender listed
  • DMARC published, moving from p=none to quarantine then reject
  • DKIM signing enabled on the mail provider
  • DNSSEC signed at the registrar
  • CAA record restricting which CAs may issue certificates
  • MTA-STS and TLS-RPT for inbound mail

How to fix it

  1. 1Publish DMARC in monitoring mode first, then tighten after reviewing reports
  2. 2Add CAA for the CA you actually use, usually letsencrypt.org

Firebase context

Google backend platform (Firestore, Auth, Storage) used by web and mobile apps.

Security rules must be verified; open Firestore/Storage rules are a classic data-leak finding.