Identity
59
D
darkero.com
Posture Score: 60/100
Scanned May 28, 2026 at 1:48 AM UTC
Attack Surface
84
Reputation
36
Identity Findings
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Subdomains have no DMARC enforcement
No sp= tag set and p=none. Subdomains inherit the monitoring-only policy, leaving them open to spoofing.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
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.darkero.com
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
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.darkero.com/.well-known/mta-sts.txt
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@darkero.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (42 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.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
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.
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.
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.
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: 2403715781, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive IP for www.darkero.com: 2606:4700:3030::ac43:aea8
The subdomain www.darkero.com resolves to 2606:4700:3030::ac43:aea8 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3030::ac43:aea8 is operational or remove the DNS record for www.darkero.com.
Non-responsive IP for www.darkero.com: 2606:4700:3037::6815:1f15
The subdomain www.darkero.com resolves to 2606:4700:3037::6815:1f15 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::6815:1f15 is operational or remove the DNS record for www.darkero.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 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.
1 subdomain(s) discovered for darkero.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 darkero.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on dnsbl.spfbl.net
162.159.205.23 (route3.mx.cloudflare.net) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
162.159.205.18 (route2.mx.cloudflare.net) 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.
Listed on dnsbl.spfbl.net
162.159.205.18 (route2.mx.cloudflare.net) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
162.159.205.17 (route2.mx.cloudflare.net) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing Strict-Transport-Security on darkero.com
The Strict-Transport-Security header is not set on https://darkero.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://darkero.com/.well-known/security.txt.
TLS certificate valid for 70 days
Certificate for darkero.com expires on 2026-08-06.
Certificate issued by WE1
The certificate for darkero.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for darkero.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for darkero.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for darkero.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on darkero.com.
No disposable email provider MX records
MX records for darkero.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for darkero.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 (route3.mx.cloudflare.net) uses with cipher 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 webmail.darkero.com
HTTPS request to https://webmail.darkero.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for darkero.com.
Could not determine domain age
WHOIS creation date could not be parsed for darkero.com.
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: arkero.com (has MX!), dakero.com (has MX!), darero.com (has MX!), darkeo.com (has MX!), darker.com (has MX!)
13 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 13. 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: none
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: none
⚠️ 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: route3.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: route3.mx.cloudflare.net
Mail server at 162.159.205.25
→
PTR Record
Reverse DNS: route3.mx.cloudflare.net
Mail Server Identity: route1.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: route1.mx.cloudflare.net
Mail server at 162.159.205.12
→
PTR Record
Reverse DNS: route1.mx.cloudflare.net
Mail Server Identity: route2.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: route2.mx.cloudflare.net
Mail server at 162.159.205.17
→
PTR Record
Reverse DNS: route2.mx.cloudflare.net
Mail Server Reputation: route3.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: route3.mx.cloudflare.net
Mail server at 162.159.205.25
→
RBL Status
Not blacklisted
Mail Server Reputation: route1.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: route1.mx.cloudflare.net
Mail server at 162.159.205.12
→
RBL Status
Not blacklisted
Mail Server Reputation: route2.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: route2.mx.cloudflare.net
Mail server at 162.159.205.17
→
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-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/darkero.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan darkero.com Again