Identity
51
B
directadmin.com
Posture Score: 81/100
Scanned May 30, 2026 at 1:33 PM UTC
Attack Surface
92
Reputation
100
Identity Findings
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
MX hostname resolves via CNAME: mail.directadmin.com
MX records should not point to a CNAME (RFC 2181). This can cause delivery failures.
💡 Point the MX record directly to an A/AAAA record, not a CNAME.
TLS certificate hostname mismatch on mail.jbmc-software.com
Certificate subject '*.directadmin.com' does not match hostname 'mail.jbmc-software.com'. SANs: *.directadmin.com, directadmin.com
💡 Obtain a TLS certificate that matches the mail server hostname.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.directadmin.com
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"
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 167.172.23.237 used by multiple MX servers
The IP 167.172.23.237 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (98 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
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.
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.
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, ri
The DMARC record contains tags deprecated in DMARCbis: pct, ri. 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 mail.directadmin.com
Detected open mail-related ports: 25, 465, 587
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: 2405592379, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
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.
6 subdomain(s) discovered for directadmin.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 directadmin.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
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on directadmin.com
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
security.txt present
Found security.txt at https://directadmin.com/.well-known/security.txt.
TLS certificate valid for 72 days
Certificate for directadmin.com expires on 2026-08-11.
Certificate issued by WE1
The certificate for directadmin.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for directadmin.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for directadmin.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for directadmin.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on directadmin.com.
Domain valid for 129 days
Domain directadmin.com expires on 2026-10-06.
Domain transfer and delete locks enabled
Domain directadmin.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for directadmin.com do not match known disposable email provider patterns.
Domain is 8636 days old
Domain directadmin.com was registered 2002-10-06.
No wildcard MX records
No wildcard MX records detected for directadmin.com.
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 (mail.directadmin.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (do.directadmin.com) aligns with the MX hostname (mail.directadmin.com).
No registered typosquat domains detected
None of the common typosquat mutations of this domain appear to be registered by third parties.
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.directadmin.com
HTTPS request to https://webmail.directadmin.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2002-10-06 | Expires: 2026-10-06 | Updated: 2022-09-04
WHOIS privacy protection enabled
Domain directadmin.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).
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: mail.directadmin.com
PTR record proves mail server legitimacy
MX: mail.directadmin.com
Mail server at mail.jbmc-software.com
→
PTR Record
No PTR record
⚠️ Mail server mail.directadmin.com (mail.jbmc-software.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mail.jbmc-software.com
PTR record proves mail server legitimacy
MX: mail.jbmc-software.com
Mail server at 167.172.23.237
→
PTR Record
Reverse DNS: do.directadmin.com
Mail Server Reputation: mail.directadmin.com
RBL check ensures server is not blacklisted
MX: mail.directadmin.com
Mail server at mail.jbmc-software.com
→
RBL Status
Not blacklisted
Mail Server Reputation: mail.jbmc-software.com
RBL check ensures server is not blacklisted
MX: mail.jbmc-software.com
Mail server at 167.172.23.237
→
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: enforce
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 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/directadmin.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan directadmin.com Again