Skip to main content

Executive's DNS Intelligence Brief

Board-level domain security assessment — resolutionscope.com

30 Aug 2026, 20:38 UTC · 61.5s · SHA-3-512: 804d✱✱✱✱ Verify ·Archived
DNS Security & Trust Posture
Risk Level: Low Risk
5 protocols configured, 4 not configured
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
No urgent actions detected. Domain security posture is well-maintained.
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? Yes llms.txt published — AI models receive structured context about 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, Inc.
Email Provider No Mail Domain
Web Hosting AWS CloudFront
DNS Hosting Amazon Route 53

Technical Findings

Email Authentication
Can this domain be impersonated by email? No — null MX indicates no-mail domain
SPF (Sender Policy) Configured
DMARC (Policy) Configured Policy: reject
DKIM (Signatures) Configured
Mail Posture No-Mail Domain — Fully Hardened
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 fully configured and validated — AD (Authenticated Data) flag set by validating resolvers 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? 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 Governance Active
Does this domain publish AI agent instructions? Yes — llms.txt published — AI models receive structured context about 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 llms.txt Found Domain provides structured context for AI models
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
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.

View Engineer's DNS Intelligence Report

Appendix — What AIs Are Being Told About This Organization What do AI systems see when they query this domain?

The following content is served to AI systems (ChatGPT, Gemini, Claude, Perplexity, and others) when they visit this domain. This is the organization's machine-readable narrative — it shapes how AI models describe, recommend, and represent this brand in conversations worldwide.

llms.txt (https://resolutionscope.com/llms.txt)
# Resolution Scope

> A sovereign instrument for measuring DNS resolution — what a domain actually
> publishes, verified against the protocol and sealed so anyone can re-check it.
> "Resolution" is literal: DNS resolution.

Resolution Scope measures eight DNS controls (DNSSEC, SPF, DKIM, DMARC, DANE,
MTA-STS, CAA, CDS/CDNSKEY) through one truth-chain: every verdict keeps the RFC
requirement, the measured state, and the real-world consequence. Verdicts carry
four states — present / absent / indeterminate / not-applicable — and unmeasured
is reported as unmeasured, never guessed. Each report carries a SHA3-512 seal:
tamper-evidence that the verdict you hold is the one that was sealed. The seal
does not prove a measurement occurred — a fabricated verdict can be sealed too.

It is the verified-substrate build of the DNS Tool family: a Rust engine
differential-tested against the production Go parent, scoring semantics
machine-checked in Lean, and a roadmap onto the seL4 verified microkernel via
LionsOS. The analyzer core is AGPL-3.0; the measurement is free and cannot be
shelved; the queried domain's data is public DNS, never a person's.

## Links

- [Source repository](https://github.com/IT-Help-San-Diego/resolution-scope): engine, truth-chain, store, proofs (AGPL-3.0)
- [DNS Tool](https://dnstool.it-help.tech): the production parent instrument
- [The Verification Principle](https://dnstool.it-help.tech/publications): the standard both instruments hold to
- [IT Help San Diego Inc.](https://it-help.tech): the operator
- [Calibration Scope](https://calibrationscope.com): sibling instrument (measures reasoning, a different product)

## Policy for automated readers

Academic and research crawlers are welcome. The site is static, no-JS, and
self-contained; everything worth indexing is on this one page.
Why this matters: This content directly influences how AI models describe your organization, products, and services. Review it for accuracy, brand alignment, and competitive positioning. If no llms.txt exists, AI models rely on whatever they can scrape — with no editorial control.
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.

804d5dc6cedc47473696a26db3bd0e610112be6ddecb334c2c249aad5e9c315382a711c7f7c038aeaef0b1a6e918d84069576f9d670ee31008e7261d2607ae9d
12 RFCs evaluated · DNS state at 30 Aug 2026, 20:38 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