Skip to main content
DNS Tool
Executive's DNS Intelligence Brief
Generated 12 Feb 2026, 10:06 UTC
Duration 29.8s
Version v26.12.28
Integrity 8331c6a531c12ee6e457bac268f9c5f0dd7f6000a76c2f833627de20fb6509e8166092a638c0046d6e26954dce9b59861b87ac1e38e5af6092644baf50dfdd51
Subject Domain
freebsd.org

Executive's DNS Intelligence Brief

Board-level domain security assessment — freebsd.org

12 Feb 2026, 10:06 UTC · 29.8s · SHA-3-512: 8331✱✱✱✱ Verify
Engineer
DNS Security & Trust Posture
Risk Level: Medium Risk Monitoring
5 protocols configured, 2 not configured
1 recommendation
Email Spoofing
Partial
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Configured
What Requires Attention
Recommended No DMARC aggregate reporting (rua) configured — unable to monitor authentication results
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 Gandi SAS
Email Provider Unknown
Web Hosting Unknown
DNS Hosting Unknown

Technical Findings

Email Authentication
SPF (Sender Policy) Configured
DMARC (Policy) Partial Policy: none Monitor Only
DKIM (Signatures) Configured
Mail Posture Email: Monitoring
Mail Transport Security
MTA-STS Partial
DANE / TLSA Not Configured
TLS-RPT (Reporting) Not Configured
Mail Transport Not Enforced Policy-assessed
DNS Security
DNSSEC Signed & Validated
DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 1.1.1.1 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)
NS Delegation Healthy
Brand & Certificate Controls
BIMI (Brand Logo) Not Configured
CAA (Certificate) Configured
Priority Actions 3 total Achievable: Low Risk
High Escalate DMARC from monitoring to enforcement

Change your DMARC policy from p=none to p=quarantine (then p=reject). Review your DMARC aggregate reports first to ensure legitimate senders pass authentication.

_dmarc.freebsd.org TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@freebsd.org"
Medium Deploy MTA-STS policy

Publish an MTA-STS DNS record and host a policy file at https://mta-sts.freebsd.org/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.

_mta-sts.freebsd.org TXT "v=STSv1; id=20240101"
Low Configure TLS-RPT reporting

Your domain has DNSSEC + DANE — the strongest email transport security available. TLS-RPT adds operational visibility by reporting when sending servers fail DANE validation or encounter STARTTLS issues delivering to your MX hosts. It does not add security — it monitors the security you already have.

_smtp._tls.freebsd.org TXT "v=TLSRPTv1; rua=mailto:tls-reports@freebsd.org"
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.

8331c6a531c12ee6e457bac268f9c5f0dd7f6000a76c2f833627de20fb6509e8166092a638c0046d6e26954dce9b59861b87ac1e38e5af6092644baf50dfdd51
12 RFCs evaluated · DNS state at 12 Feb 2026, 10:06 UTC