Identity
0
D
thexyz.com
Posture Score: 62/100
Scanned May 10, 2026 at 5:53 AM UTC
Score History
Attack Surface
99
Reputation
88
Identity Findings
Open recursion on nameserver: pns3.thexyz.com
The nameserver pns3.thexyz.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on pns3.thexyz.com or restrict it to trusted networks only.
Open recursion on nameserver: pns4.thexyz.com
The nameserver pns4.thexyz.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on pns4.thexyz.com or restrict it to trusted networks only.
Open recursion on nameserver: pns2.thexyz.com
The nameserver pns2.thexyz.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on pns2.thexyz.com or restrict it to trusted networks only.
Open recursion on nameserver: pns1.thexyz.com
The nameserver pns1.thexyz.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on pns1.thexyz.com or restrict it to trusted networks only.
Weak DKIM RSA key (~1296 bits) for selector 'k1'
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.
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.
TLS certificate hostname mismatch on mx.thexyz.com
Certificate subject '*.emailarray.com' does not match hostname 'mx.thexyz.com'. SANs: *.emailarray.com, emailarray.com
💡 Obtain a TLS certificate that matches the mail server hostname.
TLS certificate hostname mismatch on mx2.thexyz.com
Certificate subject '*.emailarray.com' does not match hostname 'mx2.thexyz.com'. SANs: *.emailarray.com, emailarray.com
💡 Obtain a TLS certificate that matches the mail server hostname.
Subdomain policy (sp=none) is weaker than domain policy (p=quarantine)
The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.
💡 Set sp=quarantine or remove sp= to inherit the domain policy.
MTA-STS is in testing mode
The MTA-STS policy is in testing mode and not actively enforcing TLS.
💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.
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.
Shared IP 65.39.216.33 used by multiple MX servers
The IP 65.39.216.33 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 65.39.216.37 used by multiple MX servers
The IP 65.39.216.37 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 65.39.216.41 used by multiple MX servers
The IP 65.39.216.41 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 MX records: 275s
2 MX records have a TTL of 275s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 275s
2 TXT records have a TTL of 275s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 275s
The SPF record has a TTL of 275s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7175s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (108 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.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
MX records are valid
All MX records are properly configured.
2 MX records with 2 unique IPs
Multiple MX records provide mail delivery redundancy.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
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 responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
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 VMC authority URL in BIMI record
The BIMI record does not specify a VMC (a= tag). Gmail and Apple Mail require a VMC to display brand logos.
Open mail ports on mx.thexyz.com
Detected open mail-related ports: 25
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
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: 2026042301, Refresh: 7200s, Retry: 1800s, Expire: 1209600s, Min TTL: 3600s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodoca.com, globalsign.com, letsencrypt.org, sectigo.com
Attack Surface Findings
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.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
15 subdomain(s) discovered for thexyz.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 thexyz.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.thexyz.com, resolving to 66.179.84.186. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '40A46E197260172C'.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.thexyz.com responded with HTTP 404.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain thexyz.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Missing Strict-Transport-Security on webmail.thexyz.com
The Strict-Transport-Security header is not set on https://webmail.thexyz.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
HSTS enabled with preload on thexyz.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://thexyz.com/.well-known/security.txt.
TLS certificate valid for 83 days
Certificate for thexyz.com expires on 2026-08-02.
Certificate issued by R13
The certificate for thexyz.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for thexyz.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for thexyz.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for thexyz.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on thexyz.com.
Domain valid for 619 days
Domain thexyz.com expires on 2028-01-20.
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 (mx.thexyz.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 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 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.
WHOIS registration data
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com | Created: 2003-01-20 | Expires: 2028-01-20 | Updated: 2022-11-08
WHOIS privacy protection not detected
Domain thexyz.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Typosquat detected: texyz.com (has MX!), theyz.com (has MX!), thexz.com (has MX!), thesyz.com (has MX!), thedyz.com (has MX!)
9 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 9. 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: mx.thexyz.com
PTR record proves mail server legitimacy
MX: mx.thexyz.com
Mail server at 65.39.216.33
→
PTR Record
Reverse DNS: mx4.emailarray.com
Mail Server Identity: mx2.thexyz.com
PTR record proves mail server legitimacy
MX: mx2.thexyz.com
Mail server at 65.39.216.37
→
PTR Record
Reverse DNS: mx5.emailarray.com
Mail Server Reputation: mx.thexyz.com
RBL check ensures server is not blacklisted
MX: mx.thexyz.com
Mail server at 65.39.216.33
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.thexyz.com
RBL check ensures server is not blacklisted
MX: mx2.thexyz.com
Mail server at 65.39.216.37
→
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: testing
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
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/thexyz.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan thexyz.com Again