A95/100

instagram.com

Name: instagram.com email authentication report
Creator: MailAuthWatch
License: https://creativecommons.org/publicdomain/zero/1.0/

Solid. A couple of things could still be tighter. 2 items below, ordered by how much inbox they are costing you. Measured 0s ago from public DNS in 149 ms.

SPF PASSDKIM 1024-BITDMARC REJECTMX OK

Monitor this domain Re-run check

Fix these, in this order, or hand the list to your agent

ranked by impact

One DKIM key is 1024-bit.

Selector smtpapi._domainkey is under 2048 bits, which some receivers already downgrade.

Do this: rotate to a 2048-bit key at the sending service.

Aggregate reports are being sent to a domain that has not authorised yours.

dmarc.facebookmail.com has not published instagram.com._report._dmarc.dmarc.facebookmail.com, so receivers will discard aggregate reports sent there.

Do this: ask the report provider to publish the authorisation record, or use an address on your own domain.

Records found

SPF · TXT

v=spf1 include:facebookmail.com include:_spf.fb.com -all

DMARC · _dmarc.instagram.com

v=DMARC1; p=reject; rua=mailto:a@dmarc.facebookmail.com; pct=100

DKIM · 1 of 79 selectors

smtpapi._domainkey · 1024-bit

MX · Proofpoint

10 mxa-00082601.gslb.pphosted.com
10 mxb-00082601.gslb.pphosted.com
20 mx0a-00082601.pphosted.com
20 mx0b-00082601.pphosted.com

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 2 tasks in order, exact record values, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# Fix email authentication for instagram.com

You are working on the DNS and mail configuration for instagram.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade A (95/100).
Report: https://www.mailauthwatch.com/check/instagram.com

## What is published right now (do not assume anything else)
- SPF (TXT instagram.com): v=spf1 include:facebookmail.com include:_spf.fb.com -all   — valid, 6 of 10 lookups
- DMARC (TXT _dmarc.instagram.com): v=DMARC1; p=reject; rua=mailto:a@dmarc.facebookmail.com; pct=100
- DKIM: smtpapi._domainkey (1024-bit)
- MX: mxa-00082601.gslb.pphosted.com, mxb-00082601.gslb.pphosted.com, mx0a-00082601.pphosted.com, mx0b-00082601.pphosted.com  → Proofpoint
- Nameservers: a.ns.instagram.com, b.ns.instagram.com …  → DNS host not recognised

## Tasks, in order of impact
…

# Fix email authentication for instagram.com

You are working on the DNS and mail configuration for instagram.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade A (95/100).
Report: https://www.mailauthwatch.com/check/instagram.com

## What is published right now (do not assume anything else)
- SPF (TXT instagram.com): v=spf1 include:facebookmail.com include:_spf.fb.com -all   — valid, 6 of 10 lookups
- DMARC (TXT _dmarc.instagram.com): v=DMARC1; p=reject; rua=mailto:a@dmarc.facebookmail.com; pct=100
- DKIM: smtpapi._domainkey (1024-bit)
- MX: mxa-00082601.gslb.pphosted.com, mxb-00082601.gslb.pphosted.com, mx0a-00082601.pphosted.com, mx0b-00082601.pphosted.com  → Proofpoint
- Nameservers: a.ns.instagram.com, b.ns.instagram.com …  → DNS host not recognised

## Tasks, in order of impact
### 1. One DKIM key is 1024-bit.
Why: Selector smtpapi._domainkey is under 2048 bits, which some receivers already downgrade. 
Rotate to a 2048-bit key at the sending service.

### 2. Aggregate reports are being sent to a domain that has not authorised yours.
Why: dmarc.facebookmail.com has not published instagram.com._report._dmarc.dmarc.facebookmail.com, so receivers will discard aggregate reports sent there.
Ask the report provider to publish the authorisation record, or use an address on your own domain.

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access the DNS provider or Proofpoint, stop and say exactly what access you need.

## Verify
  dig +short TXT instagram.com
  dig +short TXT _dmarc.instagram.com
Then open https://www.mailauthwatch.com/check/instagram.com?fresh=1 and confirm:
  the grade is unchanged and no new issues appear. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.

Open in Claude Open in ChatGPT fix.md

Your agent, your DNS, your review. MailAuthWatch never changes records; it writes the plan and re-checks the result.

Grade history

Free checks keep nothing. Monitoring records every daily measurement and alerts you on change.

History goes back as far as your subscription.

SPF OK

v=spf1 include:facebookmail.com include:_spf.fb.com -all

DNS lookups: 6 of 10 allowed
Final mechanism: -all

OK No problems detected.

Include tree

6 / 10

instagram.com0

├─ include:_spf.fb.com+5

│ ├─ spf-00082601.pphosted.com

│ ├─ spf-00082603.pphosted.com

│ ├─ spf.protection.outlook.com

│ └─ _spf.google.com

└─ include:facebookmail.com+1

DKIM OK

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed.

Selector	Key	Record
`smtpapi`	RSA 1024-bit Weak	`k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r…`

WarningDKIM selector "smtpapi" uses a 1024-bit key. Rotate to 2048 bits.

DMARC OK

v=DMARC1; p=reject; rua=mailto:a@dmarc.facebookmail.com; pct=100

Policy: p=reject
Applies to: 100% of failing mail
Aggregate reports: mailto:a@dmarc.facebookmail.com

Warningdmarc.facebookmail.com has not published instagram.com._report._dmarc.dmarc.facebookmail.com, so receivers will discard aggregate reports sent there.

Mail exchange and extras

OK No problems detected.

MTA-STS: Not published optional: enforces TLS for inbound mail
TLS-RPT: Not published
BIMI: Not published optional: brand logo in inboxes, requires p=quarantine or reject

How the grade is calculated

Score 95/100. SPF present and valid. SPF ends with -all. DKIM found (1 selector). DMARC present and valid. DMARC policy is reject. DMARC aggregate reporting enabled. SPF contributes up to 35 points, DKIM up to 25, DMARC up to 40 (policy strength and reporting). Any critical issue caps the grade at C. Lookups that failed are shown as "not measured" and never counted as missing.

Check another domain:

Other recently graded domains

Public checks from the last few days. Every report is re-measured from DNS when opened.

live

DomainSPFDKIMDMARCGrade

spotify.com6 lookups2048-bitp=rejectA linkedin.com2 lookups1024-bitp=rejectA google.com1 lookupsnot foundp=rejectB live.com5 lookups2048-bitp=noneB amazon.com4 lookups1024-bitp=quarantineA github.com10 lookups2048-bitp=quarantineA gmail.com1 lookupsnot foundp=noneC microsoftonline.com6 lookupsnot foundp=rejectB salesforce.com4 lookups2048-bitp=rejectA mailauthwatch.com1 lookups1024-bitp=rejectA notion.so0 lookupsnot foundp=quarantineC gandi.net2 lookupsnot foundp=noneC