Identity
55
C
a21q.org
Posture Score: 74/100
Scanned May 17, 2026 at 4:03 PM UTC
Score History
Attack Surface
69
Reputation
99
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.a21q.org (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@a21q.org").
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.a21q.org
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.
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.a21q.org/.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.
SOA MNAME is not authoritative
The primary nameserver (MNAME) 'get.desec.io' does not return authoritative answers.
💡 Update the MNAME field to point to an authoritative nameserver for this zone.
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@a21q.org").
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 is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (14 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.
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.
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 kmj.a21q.org
Detected open mail-related ports: 25, 587, 993
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: 2026054543, Refresh: 86400s, Retry: 3600s, Expire: 2419200s, Min TTL: 3600s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org
Attack Surface Findings
Non-responsive nameserver:
The nameserver delegated for a21q.org is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for a21q.org is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
0 subdomain(s) discovered for a21q.org
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 a21q.org and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
HSTS enabled but missing preload directive on a21q.org
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
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://a21q.org/.well-known/security.txt.
TLS certificate valid for 47 days
Certificate for a21q.org expires on 2026-07-04.
Certificate issued by E7
The certificate for a21q.org is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for a21q.org uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for a21q.org uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for a21q.org contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on a21q.org.
Domain valid for 338 days
Domain a21q.org expires on 2027-04-21.
Domain transfer and delete locks enabled
Domain a21q.org has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for a21q.org do not match known disposable email provider patterns.
Domain is 1487 days old
Domain a21q.org was registered 2022-04-21.
No wildcard MX records
No wildcard MX records detected for a21q.org.
TLD has good reputation
The .org 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 (kmj.a21q.org) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (kmj.a21q.org) aligns with the MX hostname (kmj.a21q.org).
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.a21q.org
HTTPS request to https://webmail.a21q.org failed or timed out.
WHOIS registration data
Registrar: Porkbun LLC | Created: 2022-04-21 | Expires: 2027-04-21 | Updated: 2026-04-17
WHOIS privacy protection enabled
Domain a21q.org 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: a21.org (has MX!), a21a.org (has MX!), 21q.org
3 registered lookalike domain(s) that could be used for phishing against your brand. 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 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.
Mail Server Identity: kmj.a21q.org
PTR record proves mail server legitimacy
MX: kmj.a21q.org
Mail server at 65.108.120.86
→
PTR Record
Reverse DNS: kmj.a21q.org
Mail Server Reputation: kmj.a21q.org
RBL check ensures server is not blacklisted
MX: kmj.a21q.org
Mail server at 65.108.120.86
→
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/a21q.org.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan a21q.org Again