Identity
41
C
mondelezinternational.com
Posture Score: 76/100
Scanned May 18, 2026 at 1:04 AM UTC
Attack Surface
88
Reputation
100
Identity Findings
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.mondelezinternational.com
No STARTTLS support on custmx.cscdns.net:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.mondelezinternational.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.
Generic ISP PTR hostname: 198-58-121-58.ip.linodeusercontent.com
The PTR record for 198.58.121.58 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.mondelezinternational.com
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@mondelezinternational.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.
Very low TTL on SPF record: 82s
The SPF record has a TTL of 82s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 82s
3 TXT records have a TTL of 82s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (11 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.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
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.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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.
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.
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.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2012031666, Refresh: 28800s, Retry: 7200s, Expire: 604800s, Min TTL: 14400s
Attack Surface Findings
Non-responsive IP for dev.mondelezinternational.com: 31.222.135.96
The subdomain dev.mondelezinternational.com resolves to 31.222.135.96 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 31.222.135.96 is operational or remove the DNS record for dev.mondelezinternational.com.
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 internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
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.
3 subdomain(s) discovered for mondelezinternational.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 mondelezinternational.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on mondelezinternational.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://mondelezinternational.com/.well-known/security.txt.
TLS certificate valid for 40 days
Certificate for mondelezinternational.com expires on 2026-06-27.
Certificate issued by WR3
The certificate for mondelezinternational.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for mondelezinternational.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for mondelezinternational.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for mondelezinternational.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mondelezinternational.com.
No disposable email provider MX records
MX records for mondelezinternational.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for mondelezinternational.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 (custmx.cscdns.net) 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.mondelezinternational.com
HTTPS request to https://webmail.mondelezinternational.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for mondelezinternational.com.
Could not determine domain age
WHOIS creation date could not be parsed for mondelezinternational.com.
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: mondelezinternatinal.com (has MX!)
1 registered lookalike domain(s) that could be used for phishing against your brand. 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: custmx.cscdns.net
PTR record proves mail server legitimacy
MX: custmx.cscdns.net
Mail server at 198.58.121.58
→
PTR Record
Reverse DNS: 198-58-121-58.ip.linodeusercontent.com
Mail Server Reputation: custmx.cscdns.net
RBL check ensures server is not blacklisted
MX: custmx.cscdns.net
Mail server at 198.58.121.58
→
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 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
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/mondelezinternational.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mondelezinternational.com Again