Identity
25
F
wpastra.com
Posture Score: 39/100
Scanned May 27, 2026 at 11:48 PM UTC
Attack Surface
92
Reputation
0
Identity Findings
TLSA records without DNSSEC for linda.mx.cloudflare.net
DANE requires DNSSEC. Without it, TLSA records provide no security benefit and can be spoofed.
💡 Enable DNSSEC for the domain before relying on DANE/TLSA.
TLSA records without DNSSEC for amir.mx.cloudflare.net
DANE requires DNSSEC. Without it, TLSA records provide no security benefit and can be spoofed.
💡 Enable DNSSEC for the domain before relying on DANE/TLSA.
TLSA records without DNSSEC for isaac.mx.cloudflare.net
DANE requires DNSSEC. Without it, TLSA records provide no security benefit and can be spoofed.
💡 Enable DNSSEC for the domain before relying on DANE/TLSA.
External report destination not authorized: bsf.io
The rua= URI sends reports to bsf.io, but no authorization record exists at wpastra.com._report._dmarc.bsf.io. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of bsf.io to publish a TXT record at wpastra.com._report._dmarc.bsf.io containing 'v=DMARC1'.
External report destination not authorized: bsf.io
The ruf= URI sends reports to bsf.io, but no authorization record exists at wpastra.com._report._dmarc.bsf.io. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of bsf.io to publish a TXT record at wpastra.com._report._dmarc.bsf.io containing 'v=DMARC1'.
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.wpastra.com
External DMARC report destination not authorized: bsf.io
The rua= URI points to bsf.io but no authorization record exists at wpastra.com._report._dmarc.bsf.io.
💡 Ask the owner of bsf.io to publish a TXT record at wpastra.com._report._dmarc.bsf.io with 'v=DMARC1'.
ManageSieve port 4190 open on linda.mx.cloudflare.net
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
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.
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 (42 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.
Subdomains protected (sp=quarantine)
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).
MX records are valid
All MX records are properly configured.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
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.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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.
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.
DANE/TLSA configured for linda.mx.cloudflare.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for amir.mx.cloudflare.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for isaac.mx.cloudflare.net
TLSA records found and TLS certificate is available for verification.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on linda.mx.cloudflare.net
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995, 4190
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: 2403712813, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org, comodoca.com, pki.goog; cansignhttpexchanges=yes, ssl.com, digicert.com; cansignhttpexchanges=yes
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 subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
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.
2 subdomain(s) discovered for wpastra.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 wpastra.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
162.159.205.24 (linda.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.25 (linda.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.12 (amir.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.13 (amir.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.11 (amir.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.18 (isaac.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
162.159.205.18 (isaac.mx.cloudflare.net) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.19 (isaac.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.17 (isaac.mx.cloudflare.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
162.159.205.17 (isaac.mx.cloudflare.net) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing domain locks: clientDeleteProhibited
Domain wpastra.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled but missing preload directive on wpastra.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://wpastra.com/.well-known/security.txt.
TLS certificate valid for 39 days
Certificate for wpastra.com expires on 2026-07-06.
Certificate issued by WE1
The certificate for wpastra.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for wpastra.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for wpastra.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for wpastra.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on wpastra.com.
Domain valid for 1304 days
Domain wpastra.com expires on 2029-12-22.
No disposable email provider MX records
MX records for wpastra.com do not match known disposable email provider patterns.
Domain is 3443 days old
Domain wpastra.com was registered 2016-12-22.
No wildcard MX records
No wildcard MX records detected for wpastra.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 (linda.mx.cloudflare.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.wpastra.com
HTTPS request to https://webmail.wpastra.com failed or timed out.
WHOIS registration data
Registrar: Cloudflare, Inc. | Created: 2016-12-22 | Expires: 2029-12-22 | Updated: 2020-04-02
WHOIS privacy protection enabled
Domain wpastra.com has WHOIS privacy/redaction enabled.
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: wastra.com (has MX!), wpasta.com (has MX!), wapstra.com (has MX!), pastra.com, spastra.com
6 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 6. 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: quarantine
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: quarantine
⚠️ 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: linda.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: linda.mx.cloudflare.net
Mail server at 162.159.205.23
→
PTR Record
Reverse DNS: route3.mx.cloudflare.net
Mail Server Identity: amir.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: amir.mx.cloudflare.net
Mail server at 162.159.205.11
→
PTR Record
Reverse DNS: route1.mx.cloudflare.net
Mail Server Identity: isaac.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: isaac.mx.cloudflare.net
Mail server at 162.159.205.17
→
PTR Record
Reverse DNS: route2.mx.cloudflare.net
Mail Server Reputation: linda.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: linda.mx.cloudflare.net
Mail server at 162.159.205.23
→
RBL Status
Not blacklisted
Mail Server Reputation: amir.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: amir.mx.cloudflare.net
Mail server at 162.159.205.11
→
RBL Status
Not blacklisted
Mail Server Reputation: isaac.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: isaac.mx.cloudflare.net
Mail server at 162.159.205.17
→
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
Mode: none
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
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/wpastra.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan wpastra.com Again