Identity
21
D
axon.com
Posture Score: 68/100
Scanned May 17, 2026 at 6:07 PM UTC
Attack Surface
92
Reputation
92
Identity Findings
Open recursion on nameserver: ns-1099.awsdns-09.org
The nameserver ns-1099.awsdns-09.org allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns-1099.awsdns-09.org or restrict it to trusted networks only.
Open recursion on nameserver: ns-144.awsdns-18.com
The nameserver ns-144.awsdns-18.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns-144.awsdns-18.com or restrict it to trusted networks only.
Weak DKIM RSA key (~1296 bits) for selector 'selector1'
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.
Invalid DKIM syntax for selector 'google'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
Weak DKIM RSA key (~1296 bits) for selector 's2'
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.
Weak DKIM RSA key (~1296 bits) for selector 'mandrill'
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.
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.axon.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"
Void lookup: include:%{ir}.%{v}.%{d}.spf.has.pphosted.com
The mechanism include:%{ir}.%{v}.%{d}.spf.has.pphosted.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@axon.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.
Slow DNS response from ns-144.awsdns-18.com: 2089.2ms
The nameserver ns-144.awsdns-18.com responded in 2089.2ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns-144.awsdns-18.com.
Very low TTL on NS records: 268s
4 NS records have a TTL of 268s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record length OK (175 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.
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.
MX records are valid
All MX records are properly configured.
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.
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.
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 BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx0a-00333a01.pphosted.com
Detected open mail-related ports: 25
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: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
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.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
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.
5 subdomain(s) discovered for axon.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 axon.com and its subdomains. Each certificate reveals subdomain names.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
DMARC reports sent to URL shortener domain
DMARC aggregate or forensic reports contain sensitive authentication metadata. Sending them to URL shortener domains indicates misconfiguration or a compromised record.
💡 Change DMARC rua/ruf addresses to a domain you control.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on axon.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://axon.com/.well-known/security.txt.
TLS certificate valid for 58 days
Certificate for axon.com expires on 2026-07-15.
Certificate issued by R13
The certificate for axon.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for axon.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for axon.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for axon.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on axon.com.
Domain valid for 121 days
Domain axon.com expires on 2026-09-16.
Domain transfer and delete locks enabled
Domain axon.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for axon.com do not match known disposable email provider patterns.
Domain is 10104 days old
Domain axon.com was registered 1998-09-17.
No wildcard MX records
No wildcard MX records detected for axon.com.
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 (mx0a-00333a01.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mx0b-00333a01.pphosted.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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.axon.com
HTTPS request to https://webmail.axon.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 1998-09-17 | Expires: 2026-09-16 | Updated: 2026-05-16
WHOIS privacy protection enabled
Domain axon.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: xon.com (has MX!), aon.com (has MX!), axn.com (has MX!), axo.com (has MX!), axno.com (has MX!)
27 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 27. 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: mx0a-00333a01.pphosted.com
PTR record proves mail server legitimacy
MX: mx0a-00333a01.pphosted.com
Mail server at 148.163.145.146
→
PTR Record
Reverse DNS: mx0a-00333a01.pphosted.com
Mail Server Identity: mx0b-00333a01.pphosted.com
PTR record proves mail server legitimacy
MX: mx0b-00333a01.pphosted.com
Mail server at 148.163.141.146
→
PTR Record
Reverse DNS: mx0b-00333a01.pphosted.com
Mail Server Reputation: mx0a-00333a01.pphosted.com
RBL check ensures server is not blacklisted
MX: mx0a-00333a01.pphosted.com
Mail server at 148.163.145.146
→
RBL Status
Not blacklisted
Mail Server Reputation: mx0b-00333a01.pphosted.com
RBL check ensures server is not blacklisted
MX: mx0b-00333a01.pphosted.com
Mail server at 148.163.141.146
→
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-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
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/axon.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan axon.com Again