Identity
46
C
proofpoint.com
Posture Score: 79/100
Scanned May 8, 2026 at 4:08 PM UTC
Score History
Attack Surface
92
Reputation
100
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 's2'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Weak DKIM RSA key (~1296 bits) for selector 'cm'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
Inconsistent DNS responses across nameservers
Authoritative nameservers return different answers for the same query.
💡 Verify zone transfers are working correctly and all nameservers serve the same zone data.
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.proofpoint.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.
Void lookup: include:%{ir}.%{v}.%{d}.spf.has.pphosted.com
The mechanism include:%{ir}.%{v}.%{d}.spf.has.pphosted.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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.
IPv6 MX address not accepting SMTP: 2620:100:9001:b9::1
The MX server mxa-00148501.gslb.pphosted.com has AAAA record 2620:100:9001:b9::1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2620:100:9005:b9::1
The MX server mxa-00148501.gslb.pphosted.com has AAAA record 2620:100:9005:b9::1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2620:100:9005:b9::1
The MX server mxb-00148501.gslb.pphosted.com has AAAA record 2620:100:9005:b9::1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2620:100:9001:b9::1
The MX server mxb-00148501.gslb.pphosted.com has AAAA record 2620:100:9001:b9::1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2620:100:9001:b9::1
The MX server mx0a-00148501.pphosted.com has AAAA record 2620:100:9001:b9::1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2620:100:9005:b9::1
The MX server mx0b-00148501.pphosted.com has AAAA record 2620:100:9005:b9::1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
SPF has ip4 mechanisms but no ip6
The SPF record authorizes IPv4 addresses but not IPv6. Your MX servers have AAAA records, so IPv6 mail delivery is possible without SPF authorization.
💡 Add ip6: mechanisms to the SPF record for your IPv6 mail server addresses.
Shared IP 67.231.152.185 used by multiple MX servers
The IP 67.231.152.185 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 67.231.144.185 used by multiple MX servers
The IP 67.231.144.185 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
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"
Very low TTL on A records: 180s
2 A records have a TTL of 180s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on AAAA records: 180s
2 AAAA records have a TTL of 180s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
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.
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.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
Open mail ports on mxa-00148501.gslb.pphosted.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: 2018114947, Refresh: 28800s, Retry: 7200s, Expire: 604800s, Min TTL: 1200s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodo.com, thawte.com
Attack Surface Findings
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.
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.
13 subdomain(s) discovered for proofpoint.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 proofpoint.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
HSTS enabled with preload on proofpoint.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://proofpoint.com/.well-known/security.txt.
TLS certificate valid for 95 days
Certificate for proofpoint.com expires on 2026-08-11.
Certificate issued by Sectigo Public Server Authentication CA OV R36
The certificate for proofpoint.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for proofpoint.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for proofpoint.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for proofpoint.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on proofpoint.com.
Domain valid for 91 days
Domain proofpoint.com expires on 2026-08-08.
Domain transfer and delete locks enabled
Domain proofpoint.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.proofpoint.com
HTTPS request to https://webmail.proofpoint.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 2001-08-08 | Expires: 2026-08-08 | Updated: 2024-07-07
WHOIS privacy protection not detected
Domain proofpoint.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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 missing
→
DMARC Policy
DMARC policy: reject
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: mxa-00148501.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-00148501.gslb.pphosted.com
Mail server at 67.231.152.185
→
PTR Record
Reverse DNS: mx0b-00148501.pphosted.com
Mail Server Identity: mxb-00148501.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-00148501.gslb.pphosted.com
Mail server at 67.231.144.185
→
PTR Record
Reverse DNS: mx0a-00148501.pphosted.com
Mail Server Identity: mx0a-00148501.pphosted.com
PTR record proves mail server legitimacy
MX: mx0a-00148501.pphosted.com
Mail server at 67.231.144.185
→
PTR Record
Reverse DNS: mx0a-00148501.pphosted.com
Mail Server Identity: mx0b-00148501.pphosted.com
PTR record proves mail server legitimacy
MX: mx0b-00148501.pphosted.com
Mail server at 67.231.152.185
→
PTR Record
Reverse DNS: mx0b-00148501.pphosted.com
Mail Server Reputation: mxa-00148501.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00148501.gslb.pphosted.com
Mail server at 67.231.152.185
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00148501.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00148501.gslb.pphosted.com
Mail server at 67.231.144.185
→
RBL Status
Not blacklisted
Mail Server Reputation: mx0a-00148501.pphosted.com
RBL check ensures server is not blacklisted
MX: mx0a-00148501.pphosted.com
Mail server at 67.231.144.185
→
RBL Status
Not blacklisted
Mail Server Reputation: mx0b-00148501.pphosted.com
RBL check ensures server is not blacklisted
MX: mx0b-00148501.pphosted.com
Mail server at 67.231.152.185
→
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
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
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/proofpoint.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan proofpoint.com Again