Identity
22
F
dnsowl.com
Posture Score: 48/100
Scanned May 27, 2026 at 2:35 PM UTC
Attack Surface
68
Reputation
55
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.dnsowl.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@dnsowl.com").
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.
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.
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.dnsowl.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.dnsowl.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@dnsowl.com").
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.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
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 m1.emailowl.com
Detected open mail-related ports: 25
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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: 1779892307, Refresh: 7200s, Retry: 1800s, Expire: 1209600s, Min TTL: 600s
Attack Surface Findings
Non-routable IPv4 in public DNS: test.dnsowl.com → 127.0.0.1
The subdomain test.dnsowl.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-responsive IP for ns1.dnsowl.com: 2400:cb00:2049:1::a29f:1a88
The subdomain ns1.dnsowl.com resolves to 2400:cb00:2049:1::a29f:1a88 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::a29f:1a88 is operational or remove the DNS record for ns1.dnsowl.com.
Non-responsive IP for ns1.dnsowl.com: 2400:cb00:2049:1::a29f:1bad
The subdomain ns1.dnsowl.com resolves to 2400:cb00:2049:1::a29f:1bad which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::a29f:1bad is operational or remove the DNS record for ns1.dnsowl.com.
Non-responsive IP for ns2.dnsowl.com: 2400:cb00:2049:1::a29f:1a31
The subdomain ns2.dnsowl.com resolves to 2400:cb00:2049:1::a29f:1a31 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::a29f:1a31 is operational or remove the DNS record for ns2.dnsowl.com.
Non-responsive IP for ns2.dnsowl.com: 2400:cb00:2049:1::a29f:1b82
The subdomain ns2.dnsowl.com resolves to 2400:cb00:2049:1::a29f:1b82 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::a29f:1b82 is operational or remove the DNS record for ns2.dnsowl.com.
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.
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.
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 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.
4 subdomain(s) discovered for dnsowl.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 dnsowl.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on dnsbl-2.uceprotect.net
162.243.40.215 (m1.emailowl.com) is listed on blacklist dnsbl-2.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-2.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.243.40.215 (m1.emailowl.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Could not retrieve TLS certificate
Failed to connect to dnsowl.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
Domain valid for 2786 days
Domain dnsowl.com expires on 2034-01-11.
Domain transfer and delete locks enabled
Domain dnsowl.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for dnsowl.com do not match known disposable email provider patterns.
Domain is 5979 days old
Domain dnsowl.com was registered 2010-01-11.
No wildcard MX records
No wildcard MX records detected for dnsowl.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 (m2.emailowl.com) uses TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 including Forward Secrecy.
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 dnsowl.com
HTTPS request to https://dnsowl.com failed or timed out.
Could not connect to webmail.dnsowl.com
HTTPS request to https://webmail.dnsowl.com failed or timed out.
WHOIS registration data
Registrar: NameSilo, LLC | Created: 2010-01-11 | Expires: 2034-01-11 | Updated: 2025-09-25
WHOIS privacy protection enabled
Domain dnsowl.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: dnowl.com (has MX!), dnaowl.com (has MX!), dnswl.com
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 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.
Mail Server Identity: m1.emailowl.com
PTR record proves mail server legitimacy
MX: m1.emailowl.com
Mail server at 162.243.40.215
→
PTR Record
Reverse DNS: m1.emailowl.com
Mail Server Identity: m2.emailowl.com
PTR record proves mail server legitimacy
MX: m2.emailowl.com
Mail server at 198.199.111.6
→
PTR Record
Reverse DNS: m2.emailowl.com
Mail Server Reputation: m1.emailowl.com
RBL check ensures server is not blacklisted
MX: m1.emailowl.com
Mail server at 162.243.40.215
→
RBL Status
Not blacklisted
Mail Server Reputation: m2.emailowl.com
RBL check ensures server is not blacklisted
MX: m2.emailowl.com
Mail server at 198.199.111.6
→
RBL Status
Not blacklisted
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/dnsowl.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan dnsowl.com Again