Executive's DNS Intelligence Brief
DNS Security & Trust Posture
Risk Level:
High Risk
4 protocols configured, 5 not configured
1 recommendation
Analysis Confidence
MODERATE
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Email Spoofing
Partial
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Configured
What Requires Attention
Recommended
Publish an SPF record to authorize legitimate mail senders
The BIG Questions
Can this domain be impersonated by email?
No
null MX indicates no-mail domain
Can DNS itself be tampered with?
No
DNSSEC signed; a validating resolver confirmed the cryptographic chain of trust via the AD flag (RFC 4035 §3.2.3)
Can this brand be convincingly faked?
Possible
DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity
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
Amazon Registrar, Inc.
Email Provider
No Mail Domain
Web Hosting
AWS
DNS Hosting
Unknown
Technical Findings
Email Authentication
Can this domain be impersonated by email?
No
— null MX indicates no-mail domain
SPF (Sender Policy)
Missing
DMARC (Policy)
Configured
Policy: reject
DKIM (Signatures)
Configured
Mail Posture
No-Mail Domain — Incomplete Hardening
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 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?
No
— DNSSEC signed; a validating resolver confirmed the cryptographic chain of trust via the AD flag (RFC 4035 §3.2.3)
DNSSEC
Signed & Validated
DNSSEC inherited from parent zone (resolutionscope.com) - DNS responses are authenticated
NS Delegation
Healthy
Delegation Consistency
2 Issues
Brand & Certificate Controls
Can this brand be convincingly faked?
Possible
— DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity
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 1 total Achievable: Low Risk
High
Harden SPF for Null MX Domain
This domain publishes a Null MX record (RFC 7505) declaring it does not accept email. Complete the no-mail hardening by adding a strict SPF record that explicitly denies all senders.
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.
0b8b1029cd5a8f895c2c2b29bc447e206825ebdafc171a5ec4da438ee801fd400101c931d9094a99fff2dbbaa3957ccf178f3b4d829a55d82c41b7e4b1041b56
12 RFCs evaluated · DNS state at 31 Aug 2026, 02:44 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