Identity
0
D
babylon.com
Posture Score: 63/100
Scanned May 8, 2026 at 5:05 PM UTC
Attack Surface
94
Reputation
96
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.babylon.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@babylon.com").
Open recursion on nameserver: ns4.afternic.com
The nameserver ns4.afternic.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns4.afternic.com or restrict it to trusted networks only.
Open recursion on nameserver: ns3.afternic.com
The nameserver ns3.afternic.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns3.afternic.com or restrict it to trusted networks only.
Invalid DKIM syntax for selector 'default'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'selector1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'selector2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'google'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'dkim'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'mail'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'k1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 's1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 's2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'mandrill'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'amazonses'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'cm'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Invalid DKIM syntax for selector 'smtp'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
No STARTTLS support on
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.babylon.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@babylon.com").
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.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
FCrDNS checks passed
All MX server IPs have valid forward-confirmed reverse DNS.
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.
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.
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.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
SOA record parameters
Serial: 2025100100, Refresh: 28800s, Retry: 7200s, Expire: 604800s, Min TTL: 300s
Attack Surface Findings
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.
DNS ANY query returns 7 record(s)
The DNS server responds to ANY queries with 7 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
0 subdomain(s) discovered for babylon.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 babylon.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.babylon.com, resolving to 13.248.169.48, 76.223.54.146. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.babylon.com is publicly accessible.
Reputation Findings
Missing Strict-Transport-Security on babylon.com
The Strict-Transport-Security header is not set on https://babylon.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://babylon.com/.well-known/security.txt.
TLS certificate valid for 159 days
Certificate for babylon.com expires on 2026-10-14.
Certificate issued by GoDaddy TLS Intermediate CA DV - R1v1
The certificate for babylon.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for babylon.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for babylon.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for babylon.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on babylon.com.
Domain valid for 3370 days
Domain babylon.com expires on 2035-07-31.
Domain transfer and delete locks enabled
Domain babylon.com has clientTransferProhibited and clientDeleteProhibited locks.
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 contact lookup failed
Could not query abuse contact information.
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.babylon.com
HTTPS request to https://webmail.babylon.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 1998-08-01 | Expires: 2035-07-31 | Updated: 2026-03-15
WHOIS privacy protection enabled
Domain babylon.com has WHOIS privacy/redaction enabled.
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:
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:
Mail Server Identity:
PTR record proves mail server legitimacy
MX:
Mail server at
→
PTR Record
No PTR record
⚠️ Mail server () lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation:
RBL check ensures server is not blacklisted
MX:
Mail server at
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
Brand logo configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS failure reporting configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/babylon.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan babylon.com Again