facebook.net
At risk, with 3 things to fix
facebook.net scored 18/100 (grade F). The main issues are no MX records and no DMARC record, plus 1 more.
Checked 2026-10-04 02:07 UTC · fresh check
Publish a DMARC record
Starts DMARC in monitoring mode (p=none), so you can see who sends as facebook.net before enforcing a policy. Move to quarantine once the reports show only your own services.
_dmarc.facebook.net
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=none; adkim=r; aspf=r
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Add a new TXT record with the name and value above.
- Save, then come back and re-check. DNS changes can take up to a few hours to show.
All checks
MXCan servers find your inbox?No MX recordsFailing
- Fail: No MX records
facebook.net has no MX records and no A/AAAA fallback, so it cannot receive mail, including bounces and DMARC reports. Publish an MX record pointing at your mail provider.
SPFWho may send as you?No issues foundPass
Nothing to report.
DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
- Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under facebook.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for facebook.net.
DMARCWhat happens to fakes?No DMARC recordFailing
- Fail: No DMARC record
There is no v=DMARC1 TXT record at _dmarc.facebook.net. Without DMARC, receivers have no policy for mail that fails SPF and DKIM, and Gmail and Yahoo require one for bulk senders. Start with p=none and a rua address to collect reports.
How to fix this
AlignmentDoes it match your From?No issues foundPass
Nothing to report.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.facebook.net. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.facebook.net. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.facebook.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to facebook.net, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.facebook.net
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@facebook.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.facebook.net with the value v=TLSRPTv1; rua=mailto:<that address>.
Prepare BIMIinstruction
BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.
Applies to: default._bimi.facebook.net
- Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://facebook.net/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.facebook.net with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.