Identity
30
C
wp.com
Posture Score: 73/100
Scanned May 27, 2026 at 6:27 AM UTC
Attack Surface
94
Reputation
96
Identity Findings
Invalid TLS certificate on mx1.dfw.wordpress.com
The TLS certificate presented by the mail server is expired or invalid.
💡 Renew or replace the TLS certificate on the mail server.
Invalid TLS certificate on mx1.bur.wordpress.com
The TLS certificate presented by the mail server is expired or invalid.
💡 Renew or replace the TLS certificate on the mail server.
TLS certificate hostname mismatch on mx1.dfw.wordpress.com
Certificate subject '*.automattic.com' does not match hostname 'mx1.dfw.wordpress.com'. SANs: *.automattic.com, automattic.com
💡 Obtain a TLS certificate that matches the mail server hostname.
TLS certificate hostname mismatch on mx1.bur.wordpress.com
Certificate subject '*.automattic.com' does not match hostname 'mx1.bur.wordpress.com'. SANs: *.automattic.com, automattic.com
💡 Obtain a TLS certificate that matches the mail server hostname.
FCrDNS failure: no PTR for 192.0.81.161 (mx1.dfw.wordpress.com)
The IP 192.0.81.161 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS mismatch: 192.0.115.113 → 113-115-0-192.1912.me does not resolve back
PTR for 192.0.115.113 is 113-115-0-192.1912.me, but 113-115-0-192.1912.me does not resolve back to 192.0.115.113.
💡 Ensure the PTR hostname resolves back to the original IP address.
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.wp.com
No PTR record for MX IP: 192.0.81.161
The IP 192.0.81.161 (for mx1.dfw.wordpress.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
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.wp.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: 113-115-0-192.1912.me
The PTR record for 192.0.115.113 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.wp.com
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@wp.com").
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 (39 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).
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
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.
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.dfw.wordpress.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: 2023013000, Refresh: 28800s, Retry: 7200s, Expire: 604800s, Min TTL: 86400s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489
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 10 record(s)
The DNS server responds to ANY queries with 10 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.
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.
0 subdomain(s) discovered for wp.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 wp.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.wp.com, resolving to 192.0.78.24, 192.0.78.25. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.wp.com responded with HTTP 404.
Reputation Findings
Wildcard MX records detected
Domain wp.com has wildcard MX records, which can be abused for spam or phishing.
💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on wp.com
Strict-Transport-Security: max-age=31536000; preload
HSTS enabled with preload on webmail.wp.com
Strict-Transport-Security: max-age=31536000; preload
security.txt present
Found security.txt at https://wp.com/.well-known/security.txt.
TLS certificate valid for 36 days
Certificate for wp.com expires on 2026-07-02.
Certificate issued by E7
The certificate for wp.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for wp.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for wp.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for wp.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on wp.com.
Domain valid for 671 days
Domain wp.com expires on 2028-03-29.
Domain transfer and delete locks enabled
Domain wp.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for wp.com do not match known disposable email provider patterns.
Domain is 10652 days old
Domain wp.com was registered 1997-03-28.
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.dfw.wordpress.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx1.bur.wordpress.com) aligns with the MX hostname (mx1.bur.wordpress.com).
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.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1997-03-28 | Expires: 2028-03-29 | Updated: 2026-02-25
WHOIS privacy protection not detected
Domain wp.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: ep.com (has MX!), ap.com (has MX!), wo.com (has MX!), wl.com (has MX!), wpp.com (has MX!)
19 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 19. 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.dfw.wordpress.com
PTR record proves mail server legitimacy
MX: mx1.dfw.wordpress.com
Mail server at 192.0.81.161
→
PTR Record
No PTR record
⚠️ Mail server mx1.dfw.wordpress.com (192.0.81.161) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx1.bur.wordpress.com
PTR record proves mail server legitimacy
MX: mx1.bur.wordpress.com
Mail server at 192.0.115.113
→
PTR Record
Reverse DNS: 113-115-0-192.1912.me
Mail Server Reputation: mx1.dfw.wordpress.com
RBL check ensures server is not blacklisted
MX: mx1.dfw.wordpress.com
Mail server at 192.0.81.161
→
RBL Status
Not blacklisted
Mail Server Reputation: mx1.bur.wordpress.com
RBL check ensures server is not blacklisted
MX: mx1.bur.wordpress.com
Mail server at 192.0.115.113
→
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 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/wp.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan wp.com Again