DNS Tool

Engineer's DNS Intelligence Report

Generated 17 Feb 2026, 14:25 UTC
Duration 10.8s
Version v26.19.21
Integrity 19a3b8049046d25f81259bbee2738f0b86d404246dbabf6096b5df6146d5bf3e599399d3df9cb9a0379ade8e8acdb9161e01ac9cb6e81dee59b5575c3ecd653c

TLP:AMBER

Limited disclosure — recipients may share within their organization only

Subject Domain

evilhacker.com

Engineer's DNS Intelligence Report

evilhacker.com

17 Feb 2026, 14:25 UTC · 10.8s ·v26.19.21 · SHA-3-512: 19a3✱✱✱✱ Verify

Executive Methodology

Recon Mode Snapshot Re-analyze New Domain

Footprint

DNS Security & Trust Posture

Risk Level: Medium Risk

3 protocols configured, 6 not configured Why we go beyond letter grades

1 recommendation 3 monitoring

Email Spoofing

Vulnerable

Brand Impersonation

Not Setup

DNS Tampering

Unsigned

Certificate Control

Open

Recommended

Enable DMARC aggregate reporting (rua) for authentication visibility

Monitoring

SPF configured with soft fail (~all) — consider upgrading to hard fail (-all), DMARC record has configuration warnings — review recommended, DKIM signing inferred from provider — could not directly verify selector

Configured

SPF, DMARC (with warnings), DKIM (inferred via Unknown)

Not Configured

MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC, CAA

Priority Actions 4 total Achievable posture: Secure

high Add DMARC Reject for No-Mail Domain

This domain has no MX records and appears to be a website-only domain. A DMARC reject policy tells receiving mail servers to reject any email claiming to be from your domain.

Instructs receiving servers to reject all email from this domain — no legitimate mail is expected.

Field	Value
Type	`TXT`
Host	`_dmarc.evilhacker.com`
Value	`v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;`

RFC 7489

high Lock Down SPF for No-Mail Domain

This domain has no MX records and appears to be a website-only domain. Publishing a strict SPF record explicitly declares that no servers are authorized to send email, preventing attackers from spoofing your domain.

Explicitly declares no servers are authorized to send email from this domain.

Field	Value
Type	`TXT`
Host	`evilhacker.com`
Value	`v=spf1 -all`

RFC 7208

Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035

Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.

Field	Value
Type	`CAA`
Host	`evilhacker.com` (root of domain — adjust CA to match your provider)
Value	`0 issue "letsencrypt.org"`

RFC 8659

Registrar (RDAP) OBSERVED LIVE

Tucows Domains Inc.

Where domain was purchased

Email Service Provider

Unknown

Moderately Protected

Web Hosting

Unknown

Where website is hosted

DNS Hosting

Hover

Where DNS records are edited

Email Security Methodology Can this domain be impersonated by email? Uncertain incomplete configuration

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? No

Warning

No SPF record found

RFC 7208 Deviation: This SPF record deviates from RFC 7208 requirements.

RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.

Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? No policy published

Warning

No DMARC record found

RFC 7489 Present — DMARC record published per RFC 7489 §6.3.

DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.

Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Not discoverable

Not Discoverable

DKIM not discoverable via common selectors (large providers use rotating selectors)

RFC 6376 (Provider-Managed) — DKIM signing managed by the detected mail provider per RFC 6376.

Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented

Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting

Warning

No TLS-RPT record found

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

RFC 7672 §3 RFC 6698 §2 Not Configured

No MX records available — DANE check skipped

DANE (RFC 7672) binds TLS certificates to DNSSEC-signed DNS records, protecting email transport against man-in-the-middle attacks and rogue CAs. It is the primary transport security standard — MTA-STS (RFC 8461) was created as the alternative for domains that cannot deploy DNSSEC. Over 1 million domains use DANE globally, including Microsoft Exchange Online, Proton Mail, and Fastmail. Best practice: deploy both for defense in depth.

Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).

This domain has neither DANE nor MTA-STS. Mail transport relies on opportunistic TLS without policy enforcement, leaving it vulnerable to downgrade attacks. Deploy DANE (RFC 7672) with DNSSEC for the strongest protection, or MTA-STS (RFC 8461) if DNSSEC is not feasible.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked? Partially DMARC policy is not set to reject — partial protection only

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Warning

Does this domain restrict who can issue TLS certificates? No

No CAA records found - any CA can issue certificates

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

Could not fetch security.txt

Fetch error: Connection failed

A security.txt file at /.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities. See securitytxt.org for a generator.

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org

Is this domain publishing AI-readable brand context? No

No llms.txt found

No llms-full.txt found

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Are AI crawlers explicitly allowed or blocked? Not blocked

No AI crawler blocking observed — no blocking directives found in robots.txt

Content-Usage Directive IETF Draft

Does the site express AI content-usage preferences? Not Configured

No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.

Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.

AI Recommendation Poisoning

Is this site trying to manipulate AI recommendations? No

No AI recommendation poisoning indicators found

Hidden Prompt Artifacts

Is hidden prompt-injection text present in the source? No

No hidden prompt-like artifacts detected

Evidence Log (1 item)

Type	Detail	Severity	Confidence
`robots_txt_no_ai_blocks`	robots.txt found but no AI-specific blocking directives	low	Observed

Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.

Sources scanned (1)

http://evilhacker.com/

What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

No MX records found

Policy Assessment Primary

No transport enforcement policies detected. Mail delivery relies on opportunistic STARTTLS, which is vulnerable to downgrade attacks (RFC 3207). Consider deploying MTA-STS (RFC 8461) or DANE (RFC 7672).

Telemetry

TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders

Live Probe Supplementary

Skipped — No MX records found for this domain

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 1 IP address(es)

ASN	Name	Country
`AS55293`		US

IPv4 Mappings:

216.137.187.21 → AS55293 (216.137.186.0/23)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success

No SaaS verification records detected

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Domain does not use DNSSEC. Enable in your registrar's DNS settings (look for "DNSSEC" or "DS records" section).

NS Delegation Verified

2 nameserver(s) configured

Nameservers: ns1.hover.com ns2.hover.com

Multi-Resolver Verification Recon: Consensus reached - 4 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records

Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

216.137.187.21

Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records

IPv6 not configured

MXMail Servers

No MX records

Domain cannot receive email

SRVServices

No SRV records

No service-specific routing configured

Web: Reachable (1 IPv4, 0 IPv6) Mail: Not configured Services: None

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 203 subdomains discovered

How did we find these?

Certificate Transparency Logs Unavailable The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962).

Re-Analyze to Retry CT Lookup

CT logs unavailable 203 current 0 expired 1 CNAME Source: Certificate Transparency + DNS Intelligence

Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.

Subdomain	Source	Status	Provider / CNAME	Certificates	First Seen	Issuer(s)
`academy.evilhacker.com`	DNS	Current	—	—	—	—
`account.evilhacker.com`	DNS	Current	—	—	—	—
`accounts.evilhacker.com`	DNS	Current	—	—	—	—
`admin.evilhacker.com`	DNS	Current	—	—	—	—
`alerts.evilhacker.com`	DNS	Current	—	—	—	—
`analytics.evilhacker.com`	DNS	Current	—	—	—	—
`api.evilhacker.com`	DNS	Current	—	—	—	—
`app.evilhacker.com`	DNS	Current	—	—	—	—
`appointments.evilhacker.com`	DNS	Current	—	—	—	—
`apps.evilhacker.com`	DNS	Current	—	—	—	—
`archive.evilhacker.com`	DNS	Current	—	—	—	—
`assets.evilhacker.com`	DNS	Current	—	—	—	—
`auth.evilhacker.com`	DNS	Current	—	—	—	—
`autoconfig.evilhacker.com`	DNS	Current	—	—	—	—
`autodiscover.evilhacker.com`	DNS	Current	—	—	—	—
`backup.evilhacker.com`	DNS	Current	—	—	—	—
`backup1.evilhacker.com`	DNS	Current	—	—	—	—
`backup2.evilhacker.com`	DNS	Current	—	—	—	—
`beta.evilhacker.com`	DNS	Current	—	—	—	—
`billing.evilhacker.com`	DNS	Current	—	—	—	—
`bitbucket.evilhacker.com`	DNS	Current	—	—	—	—
`blog.evilhacker.com`	DNS	Current	—	—	—	—
`booking.evilhacker.com`	DNS	Current	—	—	—	—
`bucket.evilhacker.com`	DNS	Current	—	—	—	—
`build.evilhacker.com`	DNS	Current	—	—	—	—
`cache.evilhacker.com`	DNS	Current	—	—	—	—
`cal.evilhacker.com`	DNS	Current	—	—	—	—
`calendar.evilhacker.com`	DNS	Current	—	—	—	—
`catalog.evilhacker.com`	DNS	Current	—	—	—	—
`cdn.evilhacker.com`	DNS	Current	—	—	—	—
`chat.evilhacker.com`	DNS	Current	—	—	—	—
`checkout.evilhacker.com`	DNS	Current	—	—	—	—
`ci.evilhacker.com`	DNS	Current	—	—	—	—
`client.evilhacker.com`	DNS	Current	—	—	—	—
`clients.evilhacker.com`	DNS	Current	—	—	—	—
`cloud.evilhacker.com`	DNS	Current	—	—	—	—
`community.evilhacker.com`	DNS	Current	—	—	—	—
`conference.evilhacker.com`	DNS	Current	—	—	—	—
`confluence.evilhacker.com`	DNS	Current	—	—	—	—
`connect.evilhacker.com`	DNS	Current	—	—	—	—
`corp.evilhacker.com`	DNS	Current	—	—	—	—
`cpanel.evilhacker.com`	DNS	Current	—	—	—	—
`crm.evilhacker.com`	DNS	Current	—	—	—	—
`dashboard.evilhacker.com`	DNS	Current	—	—	—	—
`database.evilhacker.com`	DNS	Current	—	—	—	—
`db.evilhacker.com`	DNS	Current	—	—	—	—
`demo.evilhacker.com`	DNS	Current	—	—	—	—
`deploy.evilhacker.com`	DNS	Current	—	—	—	—
`dev.evilhacker.com`	DNS	Current	—	—	—	—
`devices.evilhacker.com`	DNS	Current	—	—	—	—
`dns.evilhacker.com`	DNS	Current	—	—	—	—
`dns1.evilhacker.com`	DNS	Current	—	—	—	—
`dns2.evilhacker.com`	DNS	Current	—	—	—	—
`dnstool.evilhacker.com`	DNS	Current	—	—	—	—
`doc.evilhacker.com`	DNS	Current	—	—	—	—
`docs.evilhacker.com`	DNS	Current	—	—	—	—
`download.evilhacker.com`	DNS	Current	—	—	—	—
`edge.evilhacker.com`	DNS	Current	—	—	—	—
`elastic.evilhacker.com`	DNS	Current	—	—	—	—
`email.evilhacker.com`	DNS	Current	—	—	—	—
`erp.evilhacker.com`	DNS	Current	—	—	—	—
`es.evilhacker.com`	DNS	Current	—	—	—	—
`exchange.evilhacker.com`	DNS	Current	—	—	—	—
`faq.evilhacker.com`	DNS	Current	—	—	—	—
`files.evilhacker.com`	DNS	Current	—	—	—	—
`firewall.evilhacker.com`	DNS	Current	—	—	—	—
`forum.evilhacker.com`	DNS	Current	—	—	—	—
`ftp.evilhacker.com`	DNS	Current	—	—	—	—
`gateway.evilhacker.com`	DNS	Current	—	—	—	—
`geo.evilhacker.com`	DNS	Current	—	—	—	—
`git.evilhacker.com`	DNS	Current	—	—	—	—
`github.evilhacker.com`	DNS	Current	—	—	—	—
`gitlab.evilhacker.com`	DNS	Current	—	—	—	—
`grafana.evilhacker.com`	DNS	Current	—	—	—	—
`gw.evilhacker.com`	DNS	Current	—	—	—	—
`help.evilhacker.com`	DNS	Current	—	—	—	—
`host.evilhacker.com`	DNS	Current	—	—	—	—
`hr.evilhacker.com`	DNS	Current	—	—	—	—
`id.evilhacker.com`	DNS	Current	—	—	—	—
`images.evilhacker.com`	DNS	Current	—	—	—	—
`imap.evilhacker.com`	DNS	Current	—	—	—	—
`img.evilhacker.com`	DNS	Current	—	—	—	—
`internal.evilhacker.com`	DNS	Current	—	—	—	—
`intranet.evilhacker.com`	DNS	Current	—	—	—	—
`inventory.evilhacker.com`	DNS	Current	—	—	—	—
`invoice.evilhacker.com`	DNS	Current	—	—	—	—
`jenkins.evilhacker.com`	DNS	Current	—	—	—	—
`jira.evilhacker.com`	DNS	Current	—	—	—	—
`kb.evilhacker.com`	DNS	Current	—	—	—	—
`lb.evilhacker.com`	DNS	Current	—	—	—	—
`learn.evilhacker.com`	DNS	Current	—	—	—	—
`lms.evilhacker.com`	DNS	Current	—	—	—	—
`loadbalancer.evilhacker.com`	DNS	Current	—	—	—	—
`login.evilhacker.com`	DNS	Current	—	—	—	—
`logs.evilhacker.com`	DNS	Current	—	—	—	—
`m.evilhacker.com`	DNS	Current	—	—	—	—
`mail.evilhacker.com`	DNS	Current	—	—	—	—
`manage.evilhacker.com`	DNS	Current	—	—	—	—
`management.evilhacker.com`	DNS	Current	—	—	—	—
`map.evilhacker.com`	DNS	Current	—	—	—	—
`maps.evilhacker.com`	DNS	Current	—	—	—	—
`mdm.evilhacker.com`	DNS	Current	—	—	—	—
`media.evilhacker.com`	DNS	Current	—	—	—	—
`meet.evilhacker.com`	DNS	Current	—	—	—	—
`memcached.evilhacker.com`	DNS	Current	—	—	—	—
`metrics.evilhacker.com`	DNS	Current	—	—	—	—
`mobile.evilhacker.com`	DNS	Current	—	—	—	—
`monitor.evilhacker.com`	DNS	Current	—	—	—	—
`mq.evilhacker.com`	DNS	Current	—	—	—	—
`mta.evilhacker.com`	DNS	Current	—	—	—	—
`mx.evilhacker.com`	DNS	Current	—	—	—	—
`mx1.evilhacker.com`	DNS	Current	—	—	—	—
`mx2.evilhacker.com`	DNS	Current	—	—	—	—
`mysql.evilhacker.com`	DNS	Current	—	—	—	—
`nagios.evilhacker.com`	DNS	Current	—	—	—	—
`news.evilhacker.com`	DNS	Current	—	—	—	—
`notifications.evilhacker.com`	DNS	Current	—	—	—	—
`notify.evilhacker.com`	DNS	Current	—	—	—	—
`ns1.evilhacker.com`	DNS	Current	—	—	—	—
`ns2.evilhacker.com`	DNS	Current	—	—	—	—
`ns3.evilhacker.com`	DNS	Current	—	—	—	—
`ns4.evilhacker.com`	DNS	Current	—	—	—	—
`office.evilhacker.com`	DNS	Current	—	—	—	—
`orders.evilhacker.com`	DNS	Current	—	—	—	—
`owa.evilhacker.com`	DNS	Current	—	—	—	—
`panel.evilhacker.com`	DNS	Current	—	—	—	—
`partner.evilhacker.com`	DNS	Current	—	—	—	—
`partners.evilhacker.com`	DNS	Current	—	—	—	—
`pay.evilhacker.com`	DNS	Current	—	—	—	—
`payment.evilhacker.com`	DNS	Current	—	—	—	—
`pbx.evilhacker.com`	DNS	Current	—	—	—	—
`phone.evilhacker.com`	DNS	Current	—	—	—	—
`pop.evilhacker.com`	DNS	Current	—	—	—	—
`portal.evilhacker.com`	DNS	Current	—	—	—	—
`postgres.evilhacker.com`	DNS	Current	—	—	—	—
`preview.evilhacker.com`	DNS	Current	—	—	—	—
`print.evilhacker.com`	DNS	Current	—	—	—	—
`printer.evilhacker.com`	DNS	Current	—	—	—	—
`prometheus.evilhacker.com`	DNS	Current	—	—	—	—
`proxy.evilhacker.com`	DNS	Current	—	—	—	—
`proxy1.evilhacker.com`	DNS	Current	—	—	—	—
`proxy2.evilhacker.com`	DNS	Current	—	—	—	—
`queue.evilhacker.com`	DNS	Current	—	—	—	—
`rabbitmq.evilhacker.com`	DNS	Current	—	—	—	—
`redis.evilhacker.com`	DNS	Current	—	—	—	—
`register.evilhacker.com`	DNS	Current	—	—	—	—
`relay.evilhacker.com`	DNS	Current	—	—	—	—
`remote.evilhacker.com`	DNS	Current	—	—	—	—
`repo.evilhacker.com`	DNS	Current	—	—	—	—
`report.evilhacker.com`	DNS	Current	—	—	—	—
`reports.evilhacker.com`	DNS	Current	—	—	—	—
`s3.evilhacker.com`	DNS	Current	—	—	—	—
`sandbox.evilhacker.com`	DNS	Current	—	—	—	—
`scan.evilhacker.com`	DNS	Current	—	—	—	—
`schedule.evilhacker.com`	DNS	Current	—	—	—	—
`screen.evilhacker.com`	DNS	Current	—	—	—	—
`search.evilhacker.com`	DNS	Current	—	—	—	—
`secure.evilhacker.com`	DNS	Current	—	—	—	—
`server.evilhacker.com`	DNS	Current	—	—	—	—
`server1.evilhacker.com`	DNS	Current	—	—	—	—
`server2.evilhacker.com`	DNS	Current	—	—	—	—
`sftp.evilhacker.com`	DNS	Current	—	—	—	—
`share.evilhacker.com`	DNS	Current	—	—	—	—
`shop.evilhacker.com`	DNS	Current	—	—	—	—
`signup.evilhacker.com`	DNS	Current	—	—	—	—
`sip.evilhacker.com`	DNS	Current	—	—	—	—
`slack.evilhacker.com`	DNS	Current	—	—	—	—
`smtp.evilhacker.com`	DNS	Current	—	—	—	—
`sql.evilhacker.com`	DNS	Current	—	—	—	—
`ssh.evilhacker.com`	DNS	Current	—	—	—	—
`ssl.evilhacker.com`	DNS	Current	—	—	—	—
`sso.evilhacker.com`	DNS	Current	—	—	—	—
`stage.evilhacker.com`	DNS	Current	—	—	—	—
`staging.evilhacker.com`	DNS	Current	—	—	—	—
`static.evilhacker.com`	DNS	Current	—	—	—	—
`status.evilhacker.com`	DNS	Current	—	—	—	—
`storage.evilhacker.com`	DNS	Current	—	—	—	—
`store.evilhacker.com`	DNS	Current	—	—	—	—
`support.evilhacker.com`	DNS	Current	—	—	—	—
`teams.evilhacker.com`	DNS	Current	—	—	—	—
`tel.evilhacker.com`	DNS	Current	—	—	—	—
`test.evilhacker.com`	DNS	Current	—	—	—	—
`ticket.evilhacker.com`	DNS	Current	—	—	—	—
`tickets.evilhacker.com`	DNS	Current	—	—	—	—
`tls.evilhacker.com`	DNS	Current	—	—	—	—
`tool.evilhacker.com`	DNS	Current	—	—	—	—
`tools.evilhacker.com`	DNS	Current	—	—	—	—
`tracking.evilhacker.com`	DNS	Current	—	—	—	—
`training.evilhacker.com`	DNS	Current	—	—	—	—
`uat.evilhacker.com`	DNS	Current	—	—	—	—
`video.evilhacker.com`	DNS	Current	—	—	—	—
`voip.evilhacker.com`	DNS	Current	—	—	—	—
`vpn.evilhacker.com`	DNS	Current	—	—	—	—
`waf.evilhacker.com`	DNS	Current	—	—	—	—
`web.evilhacker.com`	DNS	Current	—	—	—	—
`webmail.evilhacker.com`	DNS	Current	—	—	—	—
`wiki.evilhacker.com`	DNS	Current	—	—	—	—
`work.evilhacker.com`	DNS	Current	—	—	—	—
`www.evilhacker.com`	DNS	Current	`evilhacker.com`	—	—	—
`www2.evilhacker.com`	DNS	Current	—	—	—	—
`www3.evilhacker.com`	DNS	Current	—	—	—	—
`zabbix.evilhacker.com`	DNS	Current	—	—	—	—
`zoom.evilhacker.com`	DNS	Current	—	—	—	—

Export Recon (CSV)

Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.

DNS Intelligence What does DNS look like right now — and what changed over time?

DNS Evidence Diff Side-by-side comparison

Resolver Records (Public DNS cache)

Authoritative Records (Source of truth)

A Synchronized 1 / 1 records

216.137.187.21

AAAA 0 / 0 records

No records

CAA RFC 8659 §4 0 / 0 records

No records

MX RFC 5321 0 / 0 records

No records

NS RFC 1035 Synchronized 2 / 2 records

ns2.hover.com.

ns1.hover.com.

SOA RFC 1035 Synchronized 1 / 1 records

ns1.hover.com. dnsmaster.hover.com. 1724454820 1800 900 604800 300

TXT RFC 7208 §4 0 / 0 records

No records

DNS History Timeline BETA

Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

19a3b8049046d25f81259bbee2738f0b86d404246dbabf6096b5df6146d5bf3e599399d3df9cb9a0379ade8e8acdb9161e01ac9cb6e81dee59b5575c3ecd653c

Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 17 Feb 2026, 14:25 UTC.

Download Raw Intelligence Download Checksum (.sha3)

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL)

cat dns-intelligence-evilhacker.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-evilhacker.com.json

Python 3 (cross-platform)

python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-evilhacker.com.json','rb').read()).hexdigest())"

sha3sum (coreutils 9+)

sha3sum -a 512 dns-intelligence-evilhacker.com.json

Compare the output against the .sha3 file or the checksum API at /api/analysis/1255/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for evilhacker.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035

dig +noall +answer evilhacker.com A

Query AAAA records (IPv6) RFC 1035

dig +noall +answer evilhacker.com AAAA

Query MX records (mail servers) RFC 1035

dig +noall +answer evilhacker.com MX

Query NS records (nameservers) RFC 1035

dig +noall +answer evilhacker.com NS

Query TXT records RFC 1035

dig +noall +answer evilhacker.com TXT

Email Authentication

Check SPF record RFC 7208

dig +short evilhacker.com TXT | grep -i spf

Check DMARC policy RFC 7489

dig +short _dmarc.evilhacker.com TXT

Check DKIM key for selector 'default' RFC 6376

dig +short default._domainkey.evilhacker.com TXT

Check DKIM key for selector 'google' RFC 6376

dig +short google._domainkey.evilhacker.com TXT

Check DKIM key for selector 'selector1' RFC 6376

dig +short selector1._domainkey.evilhacker.com TXT

Check DKIM key for selector 'selector2' RFC 6376

dig +short selector2._domainkey.evilhacker.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035

dig +dnssec +noall +answer evilhacker.com DNSKEY

Check DNSSEC DS records RFC 4035

dig +noall +answer evilhacker.com DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035

dig +dnssec +cd evilhacker.com A @1.1.1.1

Transport Security

Check TLSA record (replace MX_HOST with actual MX) RFC 7672

dig +noall +answer _25._tcp.MX_HOST TLSA

Check MTA-STS DNS record RFC 8461

dig +short _mta-sts.evilhacker.com TXT

Fetch MTA-STS policy file RFC 8461

curl -sL https://mta-sts.evilhacker.com/.well-known/mta-sts.txt

Check TLS-RPT record RFC 8460

dig +short _smtp._tls.evilhacker.com TXT

Brand & Trust

Check BIMI record BIMI Draft

dig +short default._bimi.evilhacker.com TXT

Check CAA records (certificate authority authorization) RFC 8659

dig +noall +answer evilhacker.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460

dig +noall +answer evilhacker.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344

dig +noall +answer evilhacker.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083

curl -sL 'https://rdap.org/domain/evilhacker.com' | python3 -m json.tool | head -50

Search Certificate Transparency logs RFC 6962

curl -s 'https://crt.sh/?q=%25.evilhacker.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20

Check security.txt RFC 9116

curl -sL https://evilhacker.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://evilhacker.com/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://evilhacker.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 216.137.187.21 (Team Cymru)

dig +short 21.187.137.216.origin.asn.cymru.com TXT

Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.

Intelligence Confidence Audit Engine Verified · 9/9 Evaluated

How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.

SPF

Verified 4843 runs

DKIM

Verified 4662 runs

DMARC

Verified 4827 runs

DANE/TLSA

Verified 4646 runs

DNSSEC

Verified 4824 runs

BIMI

Verified 4661 runs

MTA-STS

Verified 4664 runs

TLS-RPT

Verified 4666 runs

CAA

Verified 4658 runs

Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035)

dig +noall +answer evilhacker.com A

Query AAAA records (IPv6) (RFC 1035)

dig +noall +answer evilhacker.com AAAA

Query MX records (mail servers) (RFC 1035)

dig +noall +answer evilhacker.com MX

Query NS records (nameservers) (RFC 1035)

dig +noall +answer evilhacker.com NS

Query TXT records (RFC 1035)

dig +noall +answer evilhacker.com TXT

Email Authentication

Check SPF record (RFC 7208)

dig +short evilhacker.com TXT | grep -i spf

Check DMARC policy (RFC 7489)

dig +short _dmarc.evilhacker.com TXT

Check DKIM key for selector 'default' (RFC 6376)

dig +short default._domainkey.evilhacker.com TXT

Check DKIM key for selector 'google' (RFC 6376)

dig +short google._domainkey.evilhacker.com TXT

Check DKIM key for selector 'selector1' (RFC 6376)

dig +short selector1._domainkey.evilhacker.com TXT

Check DKIM key for selector 'selector2' (RFC 6376)

dig +short selector2._domainkey.evilhacker.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035)

dig +dnssec +noall +answer evilhacker.com DNSKEY

Check DNSSEC DS records (RFC 4035)

dig +noall +answer evilhacker.com DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035)

dig +dnssec +cd evilhacker.com A @1.1.1.1

Transport Security

Check TLSA record (replace MX_HOST with actual MX) (RFC 7672)

dig +noall +answer _25._tcp.MX_HOST TLSA

Check MTA-STS DNS record (RFC 8461)

dig +short _mta-sts.evilhacker.com TXT

Fetch MTA-STS policy file (RFC 8461)

curl -sL https://mta-sts.evilhacker.com/.well-known/mta-sts.txt

Check TLS-RPT record (RFC 8460)

dig +short _smtp._tls.evilhacker.com TXT

Brand & Trust

Check BIMI record (BIMI Draft)

dig +short default._bimi.evilhacker.com TXT

Check CAA records (certificate authority authorization) (RFC 8659)

dig +noall +answer evilhacker.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460)

dig +noall +answer evilhacker.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344)

dig +noall +answer evilhacker.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083)

curl -sL 'https://rdap.org/domain/evilhacker.com' | python3 -m json.tool | head -50

Search Certificate Transparency logs (RFC 6962)

curl -s 'https://crt.sh/?q=%25.evilhacker.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20

Check security.txt (RFC 9116)

curl -sL https://evilhacker.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://evilhacker.com/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://evilhacker.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 216.137.187.21 (Team Cymru)

dig +short 21.187.137.216.origin.asn.cymru.com TXT

Engineer's DNS Intelligence Report

Email Security Methodology Can this domain be impersonated by email? Uncertain incomplete configuration

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

Brand Security Can this brand be convincingly faked? Partially DMARC policy is not set to reject — partial protection only

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 203 subdomains discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

Rules of Engagement

What You May Do

What You May Not Do

Engineer's DNS Intelligence Report

Intelligence Dissemination

Email Security Methodology Can this domain be impersonated by email? Uncertain incomplete configuration

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

Brand Security Can this brand be convincingly faked? Partially DMARC policy is not set to reject — partial protection only

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 203 subdomains discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

RFC Reference