Identity
85
B
facebook.com
Posture Score: 85/100
Scanned May 27, 2026 at 6:28 AM UTC
Attack Surface
84
Reputation
85
Identity Findings
External report destination not authorized: dmarc.facebookmail.com
The rua= URI sends reports to dmarc.facebookmail.com, but no authorization record exists at facebook.com._report._dmarc.dmarc.facebookmail.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of dmarc.facebookmail.com to publish a TXT record at facebook.com._report._dmarc.dmarc.facebookmail.com containing 'v=DMARC1'.
External DMARC report destination not authorized: dmarc.facebookmail.com
The rua= URI points to dmarc.facebookmail.com but no authorization record exists at facebook.com._report._dmarc.dmarc.facebookmail.com.
💡 Ask the owner of dmarc.facebookmail.com to publish a TXT record at facebook.com._report._dmarc.dmarc.facebookmail.com with 'v=DMARC1'.
MTA-STS is in testing mode
The MTA-STS policy is in testing mode and not actively enforcing TLS.
💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
No CAA iodef tag configured
No iodef tag is present in the CAA records. CA policy violation reports will not be sent.
💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (33 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
MX records are valid
All MX records are properly configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM key revoked for selector 'default'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on smtpin.vvv.facebook.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 4207849484, Refresh: 14400s, Retry: 1800s, Expire: 604800s, Min TTL: 300s
Authorized certificate authorities
CAA records restrict certificate issuance to: digicert.com; account=271b0beda0771d006aa3a6c11b05187d456d6c239b46cb5241196095b09c92af
Attack Surface Findings
Non-routable IPv4 in public DNS: dev.facebook.com → 10.110.159.20
The subdomain dev.facebook.com resolves to non-routable IP 10.110.159.20, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
12 subdomain(s) discovered for facebook.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for facebook.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
TLS certificate expires in 7 days
Certificate for facebook.com expires on 2026-06-03 (7 days).
💡 Renew the TLS certificate urgently — it expires within 14 days.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on facebook.com
Strict-Transport-Security: max-age=15552000; preload
security.txt present
Found security.txt at https://facebook.com/.well-known/security.txt.
Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
The certificate for facebook.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for facebook.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for facebook.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for facebook.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on facebook.com.
Domain valid for 2863 days
Domain facebook.com expires on 2034-03-30.
Domain transfer and delete locks enabled
Domain facebook.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for facebook.com do not match known disposable email provider patterns.
Domain is 10651 days old
Domain facebook.com was registered 1997-03-29.
No wildcard MX records
No wildcard MX records detected for facebook.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (smtpin.vvv.facebook.com) uses with cipher including Forward Secrecy.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.facebook.com
HTTPS request to https://webmail.facebook.com failed or timed out.
WHOIS registration data
Registrar: RegistrarSafe, LLC | Created: 1997-03-29 | Expires: 2034-03-30 | Updated: 2025-04-23
WHOIS privacy protection not detected
Domain facebook.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: faceboko.com (has MX!), fwcebook.com (has MX!), fzcebook.com (has MX!), fafebook.com (has MX!), acebook.com
26 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 26. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy: reject
Mail Server Identity: smtpin.vvv.facebook.com
PTR record proves mail server legitimacy
MX: smtpin.vvv.facebook.com
Mail server at 66.220.149.251
→
PTR Record
Reverse DNS: msgin-regional-shv-01-rprn0.facebook.com
Mail Server Reputation: smtpin.vvv.facebook.com
RBL check ensures server is not blacklisted
MX: smtpin.vvv.facebook.com
Mail server at 66.220.149.251
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
Mode: testing
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✓
DMARC Policy
✓
BIMI Record
✗
CAA Records
✓
DNSSEC
✗
MTA-STS
✓
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/facebook.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan facebook.com Again