Identity
52
F
pphosted.com
Posture Score: 59/100
Scanned May 29, 2026 at 6:46 AM UTC
Score History
Attack Surface
48
Reputation
77
Identity Findings
Subdomains have no DMARC enforcement
sp=none explicitly allows unauthenticated mail from subdomains.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
Inconsistent SOA serials across nameservers
Nameservers return different SOA serial numbers, indicating zone transfer lag or failure.
💡 Verify zone transfers are working correctly between primary and secondary nameservers.
SOA serial mismatch across nameservers
Nameservers report different SOA serial numbers, indicating zone transfer lag or failure.
💡 Check zone transfer configuration and ensure all secondary nameservers are receiving updates.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.pphosted.com
Subdomain policy (sp=none) is weaker than domain policy (p=reject)
The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.
💡 Set sp=reject or remove sp= to inherit the domain policy.
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.pphosted.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 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@pphosted.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.
IPv6 MX address not accepting SMTP: 2620:100:9005:b9::1
The MX server mx1.proofpoint.com.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 mx1.proofpoint.com.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 mx2.proofpoint.com.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 mx2.proofpoint.com.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.
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.
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 (170 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.
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.
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.
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.
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.
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 mx1.proofpoint.com.gslb.pphosted.com
Detected open mail-related ports: 25
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: 2026999571, Refresh: 1200s, Retry: 120s, Expire: 2419200s, Min TTL: 600s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodo.com, thawte.com
Attack Surface Findings
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
NSEC used instead of NSEC3 (zone enumeration possible)
The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.
💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.
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 email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
6 subdomain(s) discovered for pphosted.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 pphosted.com and its subdomains. Each certificate reveals subdomain names.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Could not retrieve TLS certificate
Failed to connect to pphosted.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
Domain expires in 42 days
Domain pphosted.com expires on 2026-07-11 (42 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
Domain transfer and delete locks enabled
Domain pphosted.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for pphosted.com do not match known disposable email provider patterns.
Domain is 6897 days old
Domain pphosted.com was registered 2007-07-11.
No wildcard MX records
No wildcard MX records detected for pphosted.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 (mx1.proofpoint.com.gslb.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mx1.proofpoint.com.gslb.pphosted.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 pphosted.com
HTTPS request to https://pphosted.com failed or timed out.
Could not connect to webmail.pphosted.com
HTTPS request to https://webmail.pphosted.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 2007-07-11 | Expires: 2026-07-11 | Updated: 2026-01-28
WHOIS privacy protection not detected
Domain pphosted.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: pposted.com (has MX!), plhosted.com (has MX!), phosted.com
3 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 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: mx1.proofpoint.com.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mx1.proofpoint.com.gslb.pphosted.com
Mail server at 67.231.152.185
→
PTR Record
Reverse DNS: mx0b-00148501.pphosted.com
Mail Server Identity: mx2.proofpoint.com.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mx2.proofpoint.com.gslb.pphosted.com
Mail server at 67.231.144.185
→
PTR Record
Reverse DNS: mx0a-00148501.pphosted.com
Mail Server Reputation: mx1.proofpoint.com.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mx1.proofpoint.com.gslb.pphosted.com
Mail server at 67.231.152.185
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.proofpoint.com.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mx2.proofpoint.com.gslb.pphosted.com
Mail server at 67.231.144.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
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-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
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/pphosted.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan pphosted.com Again