What this configuration means
Each section below is shown because the observed records match its condition. The explanations are reviewed text selected by the data, not generated from it.
DMARC enforces rejection
googleapis.com publishes p=reject. Receivers that honour DMARC refuse mail using this domain in From unless SPF or DKIM aligns. This is the strongest published posture; it depends on every legitimate sender — including third-party platforms — having an aligned path, and on the aggregate reports the record requests to catch regressions.
SPF declares the domain sends no mail
The record is exactly v=spf1 -all: no source is authorized and everything fails. This is the correct posture for a domain that never sends, and combined with an enforcing DMARC policy it closes the domain to spoofing.
No MX record
googleapis.com publishes no mail exchanger. Under RFC 5321 a sender may fall back to the domain’s A or AAAA address and attempt SMTP delivery there, which usually reaches a web server that does not speak SMTP. If the domain is not meant to receive mail, a Null MX record (RFC 7505) tells senders so immediately.
No common DKIM selectors found
None of the selector names commonly used by major platforms resolve under _domainkey.googleapis.com. DKIM has no enumeration mechanism, so the domain may sign with a selector this check does not try; absence here is not proof that DKIM is unused. It does mean no platform with a conventional selector is publicly visible.
Change history
No change has been observed since the first snapshot on 2026-09-17. The domain is re-checked regularly and a new entry appears here when any record above changes.
How to read this report
The grade summarizes two records only: A means an enforcing DMARC policy with SPF hard fail; B enforcing DMARC with SPF; C monitoring-only DMARC or a weak SPF qualifier; D one of SPF or DMARC missing; F neither published. It is a prioritization aid for the public control plane, not a statement about deliverability, reputation or the security of the organization behind the domain.
DMARC policy is discovered with the RFC 9989 DNS tree walk, so a subdomain with no record of its own is reported with the organizational policy it inherits. DKIM selectors are discovered from common names only; a domain may sign with selectors this check does not try. Everything on this page comes from public DNS as observed on 2026-09-19; caches and split-horizon DNS can show different values elsewhere.
If you operate googleapis.com and want a record corrected or the report removed, contact Mailybox.