Executive's DNS Intelligence Brief
DNS Security & Trust Posture
Risk Level:
Medium Risk
4 protocols configured, 4 not configured, 1 unavailable on provider
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
Open
What Requires Attention
Recommended
Enable DMARC aggregate reporting (rua) for authentication visibility
The BIG Questions
Can this domain be impersonated by email?
Partially
DMARC quarantine at limited percentage
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) — no BIMI or CAA (RFC 8659) reinforcement leaves brand impersonation largely unaddressed
Is mail transport encryption enforced?
No
No MTA-STS or DANE — mail transport encryption is opportunistic only
Is certificate issuance controlled?
No
No CAA records — any certificate authority may issue certificates for this domain
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
Realtime Register B.V.
Email Provider
Microsoft 365
Web Hosting
Unknown
DNS Hosting
Unknown
Technical Findings
Email Authentication
Can this domain be impersonated by email?
Partially
— DMARC quarantine at limited percentage
SPF (Sender Policy)
Configured
DMARC (Policy)
Partial
Policy: quarantine
DKIM (Signatures)
Configured
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
DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure
TLS-RPT (Reporting)
Not Configured
Mail Transport
Verified
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
Delegation Consistency
1 Issue
NS Fleet Health
Healthy
Diversity: Fair
DNSSEC Operations
2 Issues
2 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) — no BIMI or CAA (RFC 8659) reinforcement leaves brand impersonation largely unaddressed
Is certificate issuance controlled?
No
— No CAA records — any certificate authority may issue certificates for this domain
BIMI (Brand Logo)
Not Configured
CAA (Certificate)
Open
Any certificate authority may issue certificates
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 Checks 1 Secret Exposed
Immediate action required. Credentials were found in publicly accessible source code. These should be rotated and removed from public-facing code.
high
Generic Bearer Token
api_********b12'
in blauw.com/
Priority Actions 5 total Achievable: Hardened
Medium
Add DMARC Aggregate Reporting
Add a rua= tag to receive aggregate DMARC reports. Without reporting, you cannot monitor authentication failures.
Medium
Increase DMARC Coverage
Your DMARC policy only applies to 40% of mail. Increase pct to 100 for full protection.
Low
Add CAA Records
CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.
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.
f1bdfa441965554a3e6624dce451e600117a19cea52cd81eb51dc5254a039fdab27eb39ccdad3128f58d25b95636966ce2dbdf9699319e70c427119f055de39f
12 RFCs evaluated · DNS state at 30 Apr 2026, 13:46 UTC