Identity
13
F
adnxs.com
Posture Score: 54/100
Scanned May 27, 2026 at 3:55 PM UTC
Attack Surface
56
Reputation
92
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.adnxs.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@adnxs.com").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
Nameserver unresponsive: ns1.gslb.com
The nameserver ns1.gslb.com is not responding on port 53.
💡 Verify that ns1.gslb.com is properly configured and accessible.
Nameserver unresponsive: ns2.gslb.com
The nameserver ns2.gslb.com is not responding on port 53.
💡 Verify that ns2.gslb.com is properly configured and accessible.
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.adnxs.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.adnxs.com/.well-known/mta-sts.txt
SOA expire value too short
The SOA expire value is 86400s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.
💡 Increase the SOA expire value to at least 604800 seconds (7 days).
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@adnxs.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 1, Refresh: 86400s, Retry: 30s, Expire: 86400s, Min TTL: 30s
Attack Surface Findings
Non-responsive nameserver: ns1.gslb.com
The nameserver ns1.gslb.com delegated for adnxs.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to ns1.gslb.com or ensure the nameserver is operational.
Non-responsive nameserver: ns2.gslb.com
The nameserver ns2.gslb.com delegated for adnxs.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to ns2.gslb.com or ensure the nameserver is operational.
Non-responsive IP for www.adnxs.com: 68.67.163.91
The subdomain www.adnxs.com resolves to 68.67.163.91 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 68.67.163.91 is operational or remove the DNS record for www.adnxs.com.
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
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 MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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.
13 subdomain(s) discovered for adnxs.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 adnxs.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.adnxs.com, resolving to 185.89.211.132. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.adnxs.com responded with HTTP 404.
Reputation Findings
Missing Strict-Transport-Security on adnxs.com
The Strict-Transport-Security header is not set on https://adnxs.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.adnxs.com
The Strict-Transport-Security header is not set on https://webmail.adnxs.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
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://adnxs.com/.well-known/security.txt.
TLS certificate valid for 152 days
Certificate for adnxs.com expires on 2026-10-26.
Certificate issued by GeoTrust TLS ECC CA G1
The certificate for adnxs.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for adnxs.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for adnxs.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for adnxs.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on adnxs.com.
Domain valid for 365 days
Domain adnxs.com expires on 2027-05-27.
Domain transfer and delete locks enabled
Domain adnxs.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for adnxs.com do not match known disposable email provider patterns.
Domain is 6573 days old
Domain adnxs.com was registered 2008-05-27.
No wildcard MX records
No wildcard MX records detected for adnxs.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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: 2008-05-27 | Expires: 2027-05-27 | Updated: 2026-04-25
WHOIS privacy protection not detected
Domain adnxs.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: anxs.com (has MX!), adxs.com (has MX!), adnx.com (has MX!), danxs.com (has MX!), adnsx.com (has MX!)
15 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 15. 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 missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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 missing
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/adnxs.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan adnxs.com Again