Executive's DNS Intelligence Brief
TLP:AMBER
Limited disclosure — recipients may share within their organization only
DNS Security & Trust Posture
Risk Level:
Low Risk
8 protocols configured, 1 not configured
2 recommendations
Analysis Confidence
MODERATE
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Email Spoofing
Protected
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Configured
What Requires Attention
Recommended
Upgrade DMARC policy from quarantine to reject (p=reject) for maximum spoofing protection
Recommended
Add DMARC aggregate reporting (rua) for visibility into email authentication
The BIG Questions
Can this domain be impersonated by email?
Unlikely
SPF and DMARC quarantine policy enforced
Can DNS itself be tampered with?
No
DNSSEC signed and validated, cryptographic chain of trust verified
Can this brand be convincingly faked?
Likely
DMARC quarantine flags but does not reject spoofed mail (RFC 7489 §6.3), and no BIMI brand verification — lookalike domains display identically in inboxes; CAA restricts certificate issuance (RFC 8659 §4) but visual brand faking remains open
Is mail transport encryption enforced?
Yes
Both MTA-STS and DANE enforce encrypted mail delivery
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
robots.txt present but does not block AI crawlers — content may be freely scraped
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
Email Provider
Unknown
Web Hosting
Unknown
DNS Hosting
Amazon Route 53
Technical Findings
Email Authentication
Can this domain be impersonated by email?
Unlikely
— SPF and DMARC quarantine policy enforced
SPF (Sender Policy)
Configured
DMARC (Policy)
Configured
Policy: quarantine
DKIM (Signatures)
Configured
Mail Posture
Moderately Protected
Mail Transport Security
Is mail transport encryption enforced?
Yes
— Both MTA-STS and DANE enforce encrypted mail delivery
MTA-STS
Active
Mode: enforce
DANE / TLSA
Active
TLS-RPT (Reporting)
Configured
Mail Transport
Enforced
Policy-assessed
2 probes
DNS Security
Can DNS itself be tampered with?
No
— DNSSEC signed and validated, cryptographic chain of trust verified
DNSSEC
Signed & Validated
DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 8.8.8.8 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)
NS Delegation
Healthy
Managed DNS
Delegation Consistency
1 Issue
NS Fleet Health
Healthy
Diversity: Fair
DNSSEC Operations
1 Issue
3 keys, 0 sigs
Brand & Certificate Controls
Can this brand be convincingly faked?
Likely
— DMARC quarantine flags but does not reject spoofed mail (RFC 7489 §6.3), and no BIMI brand verification — lookalike domains display identically in inboxes; CAA restricts certificate issuance (RFC 8659 §4) but visual brand faking remains open
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
— robots.txt present but does not block AI crawlers — content may be freely scraped
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
Not Blocking
No AI crawler restrictions found in 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: Secure
Medium
Add DMARC Aggregate Reporting
Add a rua= tag to receive aggregate DMARC reports. Without reporting, you cannot monitor authentication failures.
Medium
Upgrade DMARC to Reject
Your DMARC policy is set to quarantine. Upgrade to p=reject for maximum protection — reject instructs receivers to discard spoofed mail entirely rather than quarantining it.
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.
106e8692760701549ccc29009c2c2cd6bb0bfdf5a6472f96d92fcc3163c1e33be1545258f1491332724b72d4a1c8936235e46bc640864b98a8bf1b540d5c2855
12 RFCs evaluated · DNS state at 22 Mar 2026, 20:40 UTC
Internet Archive — Permanent Record Wayback Machine
This analysis is permanently archived by the Internet Archive, providing independent third-party verification of DNS security posture at analysis time.
View Archived Snapshot