Identity
0
F
ahcdn.com
Posture Score: 50/100
Scanned May 30, 2026 at 1:23 PM UTC
Attack Surface
70
Reputation
80
Identity Findings
Permissive SPF qualifier: ?all
The ?all qualifier provides no guidance on unauthorized senders.
💡 Change to "-all" (hard fail) or "~all" (soft fail).
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.ahcdn.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@ahcdn.com").
Open recursion on nameserver: ns2.ahcdn.com
The nameserver ns2.ahcdn.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns2.ahcdn.com or restrict it to trusted networks only.
Open recursion on nameserver: ns3.ahcdn.com
The nameserver ns3.ahcdn.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns3.ahcdn.com or restrict it to trusted networks only.
Open recursion on nameserver: ns1.ahcdn.com
The nameserver ns1.ahcdn.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns1.ahcdn.com or restrict it to trusted networks only.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
TLS certificate hostname mismatch on mail.ahcdn.com
Certificate subject '*.advancedhosters.com' does not match hostname 'mail.ahcdn.com'. SANs: *.advancedhosters.com, advancedhosters.com
💡 Obtain a TLS certificate that matches the mail server hostname.
TLS certificate hostname mismatch on mail2.ahcdn.com
Certificate subject '*.advancedhosters.com' does not match hostname 'mail2.ahcdn.com'. SANs: *.advancedhosters.com, advancedhosters.com
💡 Obtain a TLS certificate that matches the mail server hostname.
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.ahcdn.com
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.ahcdn.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 CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
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@ahcdn.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.
SPF record length OK (52 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.
MX records are valid
All MX records are properly configured.
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.
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.
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 mail.ahcdn.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
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2020050607, Refresh: 7200s, Retry: 3600s, Expire: 1209600s, Min TTL: 3600s
Attack Surface Findings
Non-responsive IP for www.ahcdn.com: 2a02:b48:8a00::b2e:5ffc
The subdomain www.ahcdn.com resolves to 2a02:b48:8a00::b2e:5ffc which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:b48:8a00::b2e:5ffc is operational or remove the DNS record for www.ahcdn.com.
Non-responsive IP for ns1.ahcdn.com: 45.13.3.22
The subdomain ns1.ahcdn.com resolves to 45.13.3.22 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 45.13.3.22 is operational or remove the DNS record for ns1.ahcdn.com.
Non-responsive IP for ns1.ahcdn.com: 2a02:b48:8400::22
The subdomain ns1.ahcdn.com resolves to 2a02:b48:8400::22 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:b48:8400::22 is operational or remove the DNS record for ns1.ahcdn.com.
Non-responsive IP for ns2.ahcdn.com: 2a02:b48:8a00::1
The subdomain ns2.ahcdn.com resolves to 2a02:b48:8a00::1 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:b48:8a00::1 is operational or remove the DNS record for ns2.ahcdn.com.
Non-responsive IP for test.ahcdn.com: 2a02:b48:8a00::52:9539
The subdomain test.ahcdn.com resolves to 2a02:b48:8a00::52:9539 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:b48:8a00::52:9539 is operational or remove the DNS record for test.ahcdn.com.
Non-responsive IP for api.ahcdn.com: 2a02:b48:8a00::ffff
The subdomain api.ahcdn.com resolves to 2a02:b48:8a00::ffff which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:b48:8a00::ffff is operational or remove the DNS record for api.ahcdn.com.
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 16 record(s)
The DNS server responds to ANY queries with 16 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.
7 subdomain(s) discovered for ahcdn.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 ahcdn.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.ahcdn.com, resolving to 88.208.5.14. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.ahcdn.com responded with HTTP 404.
Reputation Findings
TLS certificate expires in 29 days
Certificate for ahcdn.com expires on 2026-06-28 (29 days).
💡 Renew the TLS certificate soon — it expires within 30 days.
Missing Strict-Transport-Security on ahcdn.com
The Strict-Transport-Security header is not set on https://ahcdn.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Missing Strict-Transport-Security on webmail.ahcdn.com
The Strict-Transport-Security header is not set on https://webmail.ahcdn.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Wildcard MX records detected
Domain ahcdn.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.
security.txt present
Found security.txt at https://ahcdn.com/.well-known/security.txt.
Certificate issued by GoGetSSL RSA DV CA
The certificate for ahcdn.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for ahcdn.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for ahcdn.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for ahcdn.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ahcdn.com.
Domain valid for 270 days
Domain ahcdn.com expires on 2027-02-25.
Domain transfer and delete locks enabled
Domain ahcdn.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for ahcdn.com do not match known disposable email provider patterns.
Domain is 6303 days old
Domain ahcdn.com was registered 2009-02-25.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mail.ahcdn.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx5.advancedhosters.com) aligns with the MX hostname (mail.ahcdn.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: Danesco Trading Ltd. | Created: 2009-02-25 | Expires: 2027-02-25 | Updated: 2026-01-25
WHOIS privacy protection enabled
Domain ahcdn.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: acdn.com (has MX!), ahdn.com (has MX!), ahcd.com (has MX!), aucdn.com (has MX!), ahcrn.com (has MX!)
20 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 20. 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 missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy missing
⚠️ DMARC policy is missing. Even with DKIM configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
Mail Server Identity: mail.ahcdn.com
PTR record proves mail server legitimacy
MX: mail.ahcdn.com
Mail server at 213.174.151.151
→
PTR Record
Reverse DNS: mx5.advancedhosters.com
Mail Server Identity: mail2.ahcdn.com
PTR record proves mail server legitimacy
MX: mail2.ahcdn.com
Mail server at 88.208.36.36
→
PTR Record
Reverse DNS: mx6.advancedhosters.com
Mail Server Reputation: mail.ahcdn.com
RBL check ensures server is not blacklisted
MX: mail.ahcdn.com
Mail server at 213.174.151.151
→
RBL Status
Not blacklisted
Mail Server Reputation: mail2.ahcdn.com
RBL check ensures server is not blacklisted
MX: mail2.ahcdn.com
Mail server at 88.208.36.36
→
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 not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
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/ahcdn.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ahcdn.com Again