Mailybox
check dmarcdiagnose a bounce
Home / Domain reports / instagram.com
Public email posture · checked 2026-09-20

instagram.com: DMARC, SPF and MX report

What public DNS says about how instagram.com authenticates and routes email — read the way a receiving mail server reads it, with every change recorded since 2026-09-19.

grade A · enforcing DMARC with SPF hard failTranco rank 111 snapshot
Observed configurationPublic DNS only. Nothing here required access to instagram.com.
DMARCp=reject
SPF-all
SPF lookups6/10
MX4
DKIM selectors1
MTA-STSno
RecordValue
MX10 mxa-00082601.gslb.pphosted.com · 10 mxb-00082601.gslb.pphosted.com · 20 mx0a-00082601.pphosted.com · 20 mx0b-00082601.pphosted.com
SPFv=spf1 include:facebookmail.com include:_spf.fb.com -all
DMARCv=DMARC1; p=reject; rua=mailto:a@dmarc.facebookmail.com; pct=100
DKIM selectorssmtpapi
MTA-STS / TLS-RPT / BIMIno / no / no
Providersinbound: Proofpoint
Nameserversa.ns.instagram.com, b.ns.instagram.com, c.ns.instagram.com, d.ns.instagram.com
Run a live DMARC checkBuild the digital twinLive tools re-query DNS now; this report is the 2026-09-20 snapshot.

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

instagram.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.

Inspect the effective policy

DKIM selectors are published

One selector resolves under _domainkey.instagram.com: smtpapi. Selector names often identify the sending platform, and each represents a signing key that can produce an aligned DKIM path for DMARC — the path that survives forwarding.

Inspect the keys

No transport-security policy

instagram.com does not publish MTA-STS, so senders negotiate TLS opportunistically and fall back to clear text if an attacker strips the upgrade. Publishing TLS-RPT first, then MTA-STS in testing mode, adds transport protection for inbound mail without risk to delivery.

Plan an MTA-STS rollout

Change history

No change has been observed since the first snapshot on 2026-09-19. 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-20; caches and split-horizon DNS can show different values elsewhere.

If you operate instagram.com and want a record corrected or the report removed, contact Mailybox.