Executive's DNS Intelligence Brief
DNS Security & Trust Posture
Risk Level:
Medium Risk
5 protocols configured, 4 not configured
1 recommendation
Email Spoofing
Vulnerable
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Configured
What Requires Attention
Recommended
Enable DMARC aggregate reporting (rua) for authentication visibility
The BIG Questions
Can this domain be impersonated by email?
Uncertain
incomplete configuration
Can DNS itself be tampered with?
No
DNSSEC signed and validated, cryptographic chain of trust verified
Can this brand be convincingly faked?
Partially
DMARC policy is not set to reject — partial protection only
Is mail transport encryption enforced?
No
No MTA-STS or DANE — mail transport encryption is opportunistic only
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
MarkMonitor Inc.
Email Provider
Unknown
Web Hosting
AWS CloudFront
DNS Hosting
Amazon Route 53
Technical Findings
Email Authentication
Can this domain be impersonated by email?
Uncertain
— incomplete configuration
SPF (Sender Policy)
Partial
DMARC (Policy)
Partial
DKIM (Signatures)
Not Detected
Mail Posture
Moderately Protected
Mail Transport Security
Is mail transport encryption enforced?
No
— No MTA-STS or DANE — mail transport encryption is opportunistic only
MTA-STS
Partial
DANE / TLSA
Hosted Provider
No DANE/TLSA records found (checked 1 MX host)
TLS-RPT (Reporting)
Not Configured
Mail Transport
Not Enforced
Policy-assessed
DNS Security
Can DNS itself be tampered with?
No
— DNSSEC signed and validated, cryptographic chain of trust verified
DNSSEC
Signed & Validated
DNSSEC configured (DNSKEY + DS records present) but AD flag not set — resolver did not confirm chain of trust validation (RFC 4035 §3.2.3). This may indicate a broken chain or a non-validating resolver path.
NS Delegation
Issues Detected
Brand & Certificate Controls
Can this brand be convincingly faked?
Partially
— DMARC policy is not set to reject — 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 3 total Achievable: Hardened
Medium
Add DMARC Aggregate Reporting
Add a rua= tag to receive aggregate DMARC reports. Without reporting, you cannot monitor authentication failures.
Low
Add TLS-RPT Reporting
TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.
Low
Deploy MTA-STS
MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.
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.
43c5b9435905ac0d1a94c07cd8fe9c0e0a909495053662fdb452ccf81d3fee0f92357c2e7b275cfbefd8064ff475c48e431cffbdc89cedc1a4248d1352db120a
12 RFCs evaluated · DNS state at 17 Feb 2026, 10:30 UTC