Skip to main content

Executive's DNS Intelligence Brief

Board-level domain security assessment — 2911.us

9 Feb 2026, 00:04 UTC · 14.7s · SHA-3-512: d51a✱✱✱✱ Verify
DNS Security & Trust Posture
Risk Level: SECURE (Monitoring)
4 protocols configured, 2 not configured
Email Spoofing
Protected
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Open
What Requires Attention
No urgent actions detected. Domain security posture is well-maintained.
The BIG Questions
Can this domain be impersonated by email? Not Assessed
Can DNS itself be tampered with? Not Assessed
Can this brand be convincingly faked? Not Assessed
Is mail transport encryption enforced? Not Assessed
Is certificate issuance controlled? Not Assessed
Domain Overview
Registrar GoDaddy.com, LLC
Email Provider Microsoft 365
Web Hosting GoDaddy
DNS Hosting GoDaddy

Technical Findings

Email Authentication
SPF (Sender Policy) Configured
DMARC (Policy) Configured Policy: reject
DKIM (Signatures) Not Detected
Mail Posture Email: Enabled
Mail Transport Security
MTA-STS Active Mode: enforce
DANE / TLSA Hosted Provider DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure
TLS-RPT (Reporting) Configured
Mail Transport Not assessed
DNS Security
DNSSEC Signed & Validated
DNSSEC fully configured and validated - AD flag confirmed by resolver
NS Delegation Healthy
Brand & Certificate Controls
BIMI (Brand Logo) Not Configured
CAA (Certificate) Open Any certificate authority may issue certificates
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

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.

d51ae13f29cd0ee9888ad05b397cf76f536c416cbb38048e2d22162d6149584e29fc2e0bbce691dc86fe9fb7f5ca8f7f21ae009043273228e5dfc05c02013117
12 RFCs evaluated · DNS state at 9 Feb 2026, 00:04 UTC