Executive's DNS Intelligence Brief
DNS Security & Trust Posture
Risk Level:
Critical Risk
3 protocols configured, 2 not configured
1 action required
1 recommendation
Email Spoofing
Inconclusive
Brand Impersonation
Not Set Up
DNS Tampering
Broken
Certificate Control
Configured
What Requires Attention
Critical
DNSSEC validation is failing
Recommended
Fix DNSSEC configuration or remove broken DS records
The BIG Questions
Can this domain be impersonated by email?
No
null MX indicates no-mail domain
Can DNS itself be tampered with?
Yes
DNSSEC validation is failing, DNS responses cannot be trusted
Can this brand be convincingly faked?
Likely
DMARC policy is not set to reject (RFC 7489 §6.3) — partial protection only
Is mail transport encryption enforced?
Unknown
Mail transport security could not be verified — the MTA-STS DNS lookup did not complete; a TLS-RPT record alone does not enforce TLS, so this is not evidence enforcement is absent. Re-run before concluding transport encryption is unenforced
Is certificate issuance controlled?
Yes
CAA records restrict which certificate authorities may issue certificates
Does this domain publish AI agent instructions?
No
No llms.txt file detected — AI models have no structured instructions for this domain
Is AI crawling of our content controlled?
No
No robots.txt found — AI crawlers have unrestricted access
Has someone manipulated AI recommendations about us?
No
No indicators of AI recommendation manipulation found
Are there hidden AI prompts on our site?
No
No hidden prompt artifacts found in page source
Domain Overview
Registrar
Amazon Registrar, Inc.
Email Provider
No Mail Domain
Web Hosting
Unknown
DNS Hosting
Unknown
Technical Findings
Email Authentication
Can this domain be impersonated by email?
No
— null MX indicates no-mail domain
SPF (Sender Policy)
Configured
DMARC (Policy)
Could Not Verify
DKIM (Signatures)
Not Detected
Mail Posture
Could Not Verify
Mail Transport Security
Is mail transport encryption enforced?
Unknown
— Mail transport security could not be verified — the MTA-STS DNS lookup did not complete; a TLS-RPT record alone does not enforce TLS, so this is not evidence enforcement is absent. Re-run before concluding transport encryption is unenforced
MTA-STS
Not Configured
DANE / TLSA
Hosted Provider
No valid MX hosts — DANE check skipped
TLS-RPT (Reporting)
Not Configured
Mail Transport
Not Enforced
Policy-assessed
DNS Security
Can DNS itself be tampered with?
Yes
— DNSSEC validation is failing, DNS responses cannot be trusted
DNSSEC
Partial
DNSSEC configured (DNSKEY + DS records present) but validation failed — the chain of trust is broken (RFC 4033 §5: bogus is signaled via SERVFAIL / RCODE=2).
NS Delegation
Healthy
Delegation Consistency
2 Issues
NS Fleet Health
Healthy
Diversity: Fair
Brand & Certificate Controls
Can this brand be convincingly faked?
Likely
— DMARC policy is not set to reject (RFC 7489 §6.3) — partial protection only
Is certificate issuance controlled?
Yes
— CAA records restrict which certificate authorities may issue certificates
BIMI (Brand Logo)
Not Configured
CAA (Certificate)
Configured
AI Surface Scanner Scanned
Does this domain publish AI agent instructions?
No
— No llms.txt file detected — AI models have no structured instructions for this domain
Is AI crawling of our content controlled?
No
— No robots.txt found — AI crawlers have unrestricted access
Has someone manipulated AI recommendations about us?
No
— No indicators of AI recommendation manipulation found
Are there hidden AI prompts on our site?
No
— No hidden prompt artifacts found in page source
LLM Context File
Not Found
No llms.txt file detected
AI Crawler Governance
No robots.txt
Poisoning Indicators
None Found
No AI recommendation poisoning indicators detected
Hidden Prompt Artifacts
None Found
No hidden prompt artifacts detected
Public Exposure
Clear
No secrets detected in publicly accessible source
Priority Actions 2 total Achievable: Low Risk
Critical
Fix Broken DNSSEC
DNSSEC validation is failing for this domain. This can cause resolvers to reject all DNS responses, making your domain unreachable.
High
Add DMARC Reject for Null MX Domain
This domain publishes a Null MX record (RFC 7505) but lacks a DMARC reject policy. Without it, attackers can still spoof email from this domain. Complete the no-mail hardening with a strict DMARC reject policy.
Appendix — Additional Resources
Full technical details including raw DNS records, DKIM public keys, IP/ASN mappings, resolver consensus evidence, and verification commands are available in the Engineer's DNS Intelligence Report.
Verify Report Integrity SHA-3-512 Has this report been tampered with? Verify below
Tamper-evident fingerprint binding this analysis to its data, domain, timestamp, and tool version.
2326f53112744fa36e7af3717896c985d81a18dce3a6a3d4f7efab2e4047bccbf34e3ace84e6ef4c11dd7c0a4af573689bd8eb98654b4758d76eb2f0617f45af
12 RFCs evaluated · DNS state at 30 Sep 2026, 16:05 UTC