Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 21 Feb 2026, 18:39 UTC
Duration 46.0s
Version v26.23.47
Integrity d7770283b0a0c8a256f69178b5f760e7fd802e5992257db04a9edae92464bd999a120aa6f506e4c1df89b92fa7460b8a7e886334f04738f4fe506dcda038cc49
Subject Domain
freebsd.org

Engineer's DNS Intelligence Report

freebsd.org
21 Feb 2026, 18:39 UTC · 46.0s ·v26.23.47 · SHA-3-512: d777✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint 2 SaaS Services
DNS Security & Trust Posture
Risk Level: High Risk
6 protocols configured, 3 not configured Why we go beyond letter grades
2 recommendations 1 monitoring
Suggested Scanner Configuration High Confidence
Based on 20 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 30.5s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Email Spoofing
Partial
Brand Impersonation
Not Setup
DNS Tampering
Protected
Certificate Control
Configured
Recommended
Move DMARC policy from 'none' to 'quarantine' or 'reject', Enable DMARC aggregate reporting (rua) for authentication visibility
Monitoring
DMARC record has configuration warnings — review recommended
Configured
SPF, DMARC (with warnings), DKIM, DANE, DNSSEC, CAA
Not Configured
MTA-STS, TLS-RPT, BIMI
Priority Actions 4 total Achievable posture: Low Risk
High Upgrade DMARC from p=none

Your DMARC policy is monitor-only (p=none). Upgrade to p=quarantine or p=reject after reviewing reports to actively prevent spoofing.

A quarantine or reject policy instructs receivers to take action on failing mail.
TypeTXT
Host_dmarc.freebsd.org (DMARC policy record)
Valuev=DMARC1; p=quarantine; rua=mailto:dmarc-reports@freebsd.org
RFC 7489 §6.3
Medium Add DMARC Aggregate Reporting

Add a rua= tag to receive aggregate DMARC reports. Without reporting, you cannot monitor authentication failures.

Aggregate reports show who is sending mail as your domain and whether it passes authentication.
TypeTXT
Host_dmarc.freebsd.org (add to existing DMARC record)
Valuerua=mailto:dmarc-reports@freebsd.org
RFC 7489 §7.1
Low Add TLS-RPT Reporting

Your domain has DNSSEC + DANE — the strongest email transport security available. TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

TLS-RPT sends you reports about TLS connection failures to your mail servers.
TypeTXT
Host_smtp._tls.freebsd.org (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@freebsd.org
RFC 8460
Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.freebsd.org (MTA-STS policy record)
Valuev=STSv1; id=freebsd.org
RFC 8461
Registrar (RDAP) OBSERVED LIVE
Gandi SAS
Where domain was purchased
Email Service Provider
Unknown
Moderately Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? Yes DMARC is monitor-only (p=none)

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes
Success ~all 1/10 lookups

SPF valid with industry-standard soft fail (~all), 1/10 lookups (via redirect: _spf.freebsd.org)

v=spf1 redirect=_spf.freebsd.org
SPF Redirect Chain RFC 7208 §6.1
This SPF record delegates policy via redirect= — the effective policy comes from the target domain.
_spf.freebsd.org
v=spf1 ip4:96.47.72.81 ip6:2610:1c1:1:606c::19:2 ~all
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
~all is the industry standard. Google, Apple, and most providers default to soft fail. CISA (BOD 18-01) and RFC 7489 confirm that DMARC policy — not SPF alone — is the primary enforcement control. Using ~all allows DKIM to be evaluated before a DMARC decision is made. This domain has DMARC p=none (monitoring only). Enforcing quarantine or reject is recommended to gain real protection.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Monitoring only
Warning p=none

DMARC in monitoring mode (p=none) - spoofed mail still delivered, no enforcement

v=DMARC1; p=none
Policy p=none provides no protection - spoofed emails reach inboxes
No aggregate reporting (rua) configured — you won't receive reports about authentication results and potential abuse
No forensic reporting (ruf) tag — this is correct. Many tools flag the absence of ruf= as a gap. It is not. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests regardless. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification, confirming its deprecation. Omitting ruf= is the recommended modern practice. RFC 7489 §7.3 — Forensic Reports
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Yes — verified
Found

Found DKIM records for 1 selector(s)

dkim._domainkey
v=DKIM1; k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAy46C+GD7Y5L4nk7hCMeOJfHf4EA8P/j9UoQRAQx9TQ2+xCCGNhZIoqfn8aQl+q0rSntr1X1dKKNjzJxxa9UX8cubpX4vAIPSvM8xXZ03wbVXoTSJ/YpRwMABLHAKR5OE2X4jLK/O6AXKrMMKj8EcPQofgWwnsub6I/PjXpPrXGbrMLpCh0umE2ViF3RV5qX9bz5el3tt/rQfV+rtahzo5V6xeXwLjJxNY5tKRb3fHheijrprzBFkczFwOCAjORh6zwPKfvpJtbe2Fch9MOMaPS4Hr/jJ1jyweFJWUtQOLxesWl6H+y71sK+Fs91op9pG1ThHaDLEV6K1i1W9YISkmwIDAQAB
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? Yes
RFC 7672 §3 RFC 6698 §2 1/2 MX

DANE partially configured — TLSA records on 1/2 MX hosts

MX Host Usage Selector Match Certificate Data
mx1.freebsd.org 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 0a7e2f469913ea64ca98af1f31bbbcaf51920d8df90d2972a9dc02bf7c37f404
Missing DANE for: mx66.freebsd.org
Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain uses DNSSEC + DANE — the strongest cryptographic transport security. DANE binds TLS certificates to DNSSEC-signed DNS records, creating a verifiable chain of trust from root to mail server (RFC 7672 §1.3). MTA-STS could complement this for senders that don't validate DNSSEC, but DANE alone provides the highest level of protection available.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked? Likely DMARC is monitor-only p=none (RFC 7489 §6.3) — spoofed mail is not blocked, brand faking is trivial

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only Let's Encrypt, Sectigo can issue certificates

Authorized CAs: Let's Encrypt Sectigo
0 issue "letsencrypt.org"
0 issue "comodoca.com"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

No security.txt found

A security.txt file at /.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities. See securitytxt.org for a generator.
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked? Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences? Not Configured
No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations? No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source? No
No hidden prompt-like artifacts detected
Evidence Log (1 item)
TypeDetailSeverityConfidence
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
Sources scanned (1)
  • https://freebsd.org/
What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

Mail Transport Security Beta Is mail transport encrypted and verified? Yes DANE/TLSA provides cryptographic transport verification

All 2 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary
  • DANE/TLSA records published — mail servers pin TLS certificates via DNSSEC (RFC 7672)
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Certificate
mx66.freebsd.org TLSv1.3 TLS_AES_256_GCM_SHA384 Invalid
Certificate invalid: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not va
mx1.freebsd.org TLSv1.3 TLS_AES_256_GCM_SHA384 Invalid
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 2 IP address(es)

ASNNameCountry
AS11403 US
IPv4 Mappings:
96.47.72.84 → AS11403 (96.47.64.0/20)
IPv6 Mappings:
2610:1c1:1:606c::50:15 → AS11403 (2610:1c1::/32)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 2 services

2 SaaS services detected via DNS TXT verification records

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

ServiceVerification Record
Google Workspace google-site-verification=REWF41fx56YWyINtE9RTibL63H3ZBtek1Dl6oX0TJww
Microsoft 365 MS=ms11588187
Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed and validated, cryptographic chain of trust verified

DNSSEC RFC 4033 §2 Verified Signed RSA/SHA-256 Adequate

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)

Algorithm Observation: RSA/SHA-256 — MUST implement, widely deployed (RFC 8624 §3.1)
All current DNSSEC algorithms use classical cryptography. Post-quantum DNSSEC standards are in active IETF development (draft-sheth-pqc-dnssec-strategy) but no PQC algorithms have been standardized for DNSSEC yet.
Chain of trust: Root → TLD → Domain. DNS responses are authenticated and tamper-proof.
AD Flag: Validated - Resolver (8.8.8.8) confirmed cryptographic signatures
DS Record (at registrar):
33175 8 2 BCFE5919C2E253EFD990C2E3BC88A45BEA9F4474821D193B2D7272A6951B01AF

NS Delegation Verified

5 nameserver(s) configured

Nameservers: ns1.freebsd.org ns2.freebsd.org ns3.he.net ns4.he.net ns5.he.net
Enterprise DNS (Mixed Configuration)
2 of 5 nameservers are dedicated (freebsd.org-branded), 3 use external provider(s). This pattern is common in large organizations using split-horizon DNS or maintaining redundancy across internal and external infrastructure.
Dedicated (organization-branded): ns1.freebsd.org ns2.freebsd.org External provider: ns3.he.net ns4.he.net ns5.he.net
Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

96.47.72.84
Where the domain points for web traffic

AAAAIPv6 Address

2610:1c1:1:606c::50:15
IPv6 ready

MXMail Servers

30 mx66.freebsd.org.
10 mx1.freebsd.org.
Priority + mail server for email delivery

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (1 IPv4, 1 IPv6) Mail: 2 servers Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 174 subdomains discovered
How did we find these?
294 unique certificates 174 current 0 expired 7 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Certificate Authority Diversity (4 CAs observed across CT log history)
Certificate Authority Certs First Issued Last Issued Status
Let's Encrypt 283 2025-11-23 2026-02-21 Active
Certainly 7 2026-01-28 2026-02-17 Active
ZeroSSL 3 2025-12-15 2026-02-15 Active
Amazon 1 2025-11-14 2025-11-14 Active
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
admbugs.freebsd.org CT Log Current wfe0.nyi.freebsd.org 4 2026-01-27T20:15:34 Let's Encrypt
admin-http.freebsd.org CT Log Current — 2 2025-12-24T20:15:34 Let's Encrypt
admin-svn.freebsd.org CT Log Current — 4 2026-01-28T20:15:34 Let's Encrypt
archive.freebsd.org CT Log Current — 8 2026-01-25T20:17:37 Let's Encrypt
artifact.ci.freebsd.org CT Log Current — 6 2026-02-05T20:12:33 Let's Encrypt
artifacts.ci.freebsd.org CT Log Current artifact.ci.freebsd.org 6 2026-02-05T20:12:33 Let's Encrypt
awfe0.chi.freebsd.org CT Log Current — 4 2026-02-16T20:17:34 Let's Encrypt
awfe0.nyi.freebsd.org CT Log Current — 2 2026-01-14T20:15:34 Let's Encrypt
bitergia-dash.your.freebsd.org CT Log Current — 8 2026-01-28T20:20:45 Let's Encrypt
bugs-dev.freebsd.org CT Log Current — 4 2026-02-16T20:20:42 Let's Encrypt
bugs.au.freebsd.org CT Log Current — 4 2026-02-20T16:17:50 Let's Encrypt
bugs.freebsd.org CT Log Current — 8 2026-02-20T20:12:33 Let's Encrypt
bugstest.freebsd.org CT Log Current — 6 2026-01-23T20:12:33 Let's Encrypt
bugstest2.freebsd.org CT Log Current wfe1.nyi.freebsd.org 4 2026-02-11T20:17:35 Let's Encrypt
bugzilla.freebsd.org CT Log Current — 2 2026-01-19T20:21:50 Let's Encrypt
bz-attachments-dev.freebsd.org CT Log Current — 4 2026-02-16T20:20:42 Let's Encrypt
bz-attachments.freebsd.org CT Log Current web3.nyi.freebsd.org 8 2026-02-20T20:12:33 Let's Encrypt
bztest-attachments.freebsd.org CT Log Current wfe1.nyi.freebsd.org 6 2026-01-23T20:12:33 Let's Encrypt
bztest2-attachments.freebsd.org CT Log Current — 4 2026-02-11T20:17:35 Let's Encrypt
cgit-beta.freebsd.org CT Log Current — 2 2026-01-14T20:18:40 Let's Encrypt
cgit-dev.freebsd.org CT Log Current — 4 2026-02-14T20:15:35 Let's Encrypt
cgit.freebsd.org CT Log Current cgit.geo.freebsd.org 8 2026-02-11T20:17:39 Let's Encrypt
ci-dev.freebsd.org CT Log Current — 8 2026-02-16T20:20:45 Let's Encrypt
ci.freebsd.org CT Log Current — 6 2026-02-03T20:12:33 Let's Encrypt
cloudfront.aws.pkgbase.freebsd.org CT Log Current — 1 2025-11-14T00:00:00 Amazon
cvsweb.freebsd.org CT Log Current wfe0.nyi.freebsd.org 6 2026-02-03T20:17:50 Let's Encrypt
daemon3.kr.freebsd.org CT Log Current — 4 2026-02-21T06:00:20 Let's Encrypt
docs-archive.freebsd.org CT Log Current — 8 2026-02-04T20:17:38 Let's Encrypt
docs-dev.freebsd.org CT Log Current — 4 2026-01-14T20:24:53 Let's Encrypt
docs-legacy.freebsd.org CT Log Current wfe0.nyi.freebsd.org 4 2026-01-18T20:23:53 Let's Encrypt
docs.freebsd.org CT Log Current — 4 2026-01-18T20:24:00 Let's Encrypt
download-archive.freebsd.org CT Log Current ftp-archive.freebsd.org 4 2026-01-19T20:26:58 Let's Encrypt
download.fastly.freebsd.org CT Log Current thefreebsdproject.map.fastly.net 2 2026-02-06T16:23:13 Certainly
download.freebsd.org CT Log Current — 8 2026-02-06T20:17:44 Let's Encrypt, Certainly
election.freebsd.org CT Log Current wfe0.nyi.freebsd.org 8 2026-02-16T20:20:49 Let's Encrypt
element-dev.freebsd.org CT Log Current — 8 2026-02-08T20:17:38 Let's Encrypt
element.freebsd.org CT Log Current — 8 2026-02-08T20:22:46 Let's Encrypt
forgejo-dev.freebsd.org CT Log Current — 8 2026-02-11T20:22:51 Let's Encrypt
forums.freebsd.org CT Log Current — 2 2026-01-10T08:26:54 Let's Encrypt
freefall.freebsd.org CT Log Current — 4 2026-01-25T20:20:42 Let's Encrypt
ftp.de.freebsd.org CT Log Current — 4 2026-01-23T15:03:41 Let's Encrypt
ftp.freebsd.org CT Log Current — 6 2026-02-06T20:17:44 Let's Encrypt
ftp.ir.freebsd.org CT Log Current — 4 2025-12-29T09:27:42 Let's Encrypt
ftp.kr.freebsd.org CT Log Current daemon3.kr.freebsd.org 4 2026-02-21T06:00:20 Let's Encrypt
ftp.lv.freebsd.org CT Log Current — 4 2026-02-05T23:51:10 Let's Encrypt
ftp.nl.freebsd.org CT Log Current — 2 2026-01-04T04:48:55 Let's Encrypt
ftp1.freebsd.org DNS Current ftp.geo.freebsd.org — — —
ftp2.freebsd.org DNS Current ftp.geo.freebsd.org — — —
ftp2.kr.freebsd.org CT Log Current — 6 2026-01-15T00:32:24 Let's Encrypt
ftp2.ru.freebsd.org CT Log Current — 2 2026-01-10T00:34:11 Let's Encrypt
ftp2.uk.freebsd.org CT Log Current ftp.mirrorservice.org 4 2026-01-21T05:11:51 Let's Encrypt
ftp3.de.freebsd.org CT Log Current — 4 2026-01-23T15:03:41 Let's Encrypt
ftp4.de.freebsd.org CT Log Current — 4 2026-01-23T15:03:41 Let's Encrypt
ftp5.freebsd.org CT Log Current — 4 2026-02-18T05:15:41 Let's Encrypt
ftp5.us.freebsd.org CT Log Current — 2 2026-01-14T05:15:41 Let's Encrypt
ftp7.freebsd.org CT Log Current — 4 2026-01-21T05:11:51 Let's Encrypt
git-dev.freebsd.org CT Log Current — 4 2026-02-11T20:25:56 Let's Encrypt
git.freebsd.org CT Log Current — 8 2026-02-16T20:24:01 Let's Encrypt
gitea-dev.freebsd.org CT Log Current gitea-dev.nyi.freebsd.org 8 2026-02-16T20:29:09 Let's Encrypt
gitlab-dev.freebsd.org CT Log Current — 8 2026-02-17T20:12:33 Let's Encrypt
grimoire-dev.freebsd.org CT Log Current — 8 2026-02-11T20:31:06 Let's Encrypt
grimoire-elk.freebsd.org CT Log Current — 4 2026-02-12T20:17:35 Let's Encrypt
grimoire.freebsd.org CT Log Current — 8 2026-01-28T20:20:45 Let's Encrypt
groups.freebsd.org CT Log Current — 4 2026-01-27T20:26:58 Let's Encrypt
gsoc.freebsd.org CT Log Current wfe0.nyi.freebsd.org 8 2026-02-16T21:06:18 Let's Encrypt
jenkins.freebsd.org DNS Current ci.freebsd.org — — —
kr.freebsd.org CT Log Current — 4 2026-02-21T06:00:20 Let's Encrypt
ldap-dev.freebsd.org CT Log Current — 4 2026-01-19T20:35:16 Let's Encrypt
ldap-master.freebsd.org CT Log Current — 4 2026-02-16T20:42:23 Let's Encrypt
ldap.nyi.freebsd.org CT Log Current — 2 2026-01-19T20:38:21 Let's Encrypt
lists.freebsd.org CT Log Current — 4 2026-01-18T20:24:00 Let's Encrypt
live.freebsd.org CT Log Current wfe1.nyi.freebsd.org 8 2026-02-12T20:17:38 Let's Encrypt
mail-archive.freebsd.org CT Log Current wfe0.nyi.freebsd.org 8 2026-02-04T20:22:48 Let's Encrypt
mail.freebsd.org DNS Current mx1.freebsd.org — — —
man-dev.freebsd.org CT Log Current — 4 2026-01-14T20:30:01 Let's Encrypt
man.freebsd.org CT Log Current wfe0.nyi.freebsd.org 8 2026-02-16T21:06:18 Let's Encrypt
matrix-dev.freebsd.org CT Log Current — 8 2026-02-08T20:22:50 Let's Encrypt
matrix.freebsd.org CT Log Current — 4 2026-02-08T20:27:56 Let's Encrypt
meet.freebsd.org CT Log Current — 4 2026-01-25T20:36:03 Let's Encrypt
meet.nyi.freebsd.org CT Log Current — 4 2026-01-25T20:36:03 Let's Encrypt
mfc.freebsd.org CT Log Current wfe1.nyi.freebsd.org 8 2026-02-12T20:22:48 Let's Encrypt
monitor.bbt.freebsd.org CT Log Current — 4 2026-01-26T20:17:36 Let's Encrypt
monitor.bme.freebsd.org CT Log Current — 2 2025-12-24T20:18:47 Let's Encrypt
monitor.bra.freebsd.org CT Log Current — 4 2026-02-01T20:25:47 Let's Encrypt
monitor.chi.freebsd.org CT Log Current — 4 2026-02-14T20:20:41 Let's Encrypt
monitor.fmt.freebsd.org CT Log Current — 4 2026-02-12T20:27:54 Let's Encrypt
monitor.fra.freebsd.org CT Log Current — 2 2025-12-24T20:23:52 Let's Encrypt
monitor.isc.freebsd.org CT Log Current — 4 2026-02-19T20:15:36 Let's Encrypt
monitor.jinx.freebsd.org CT Log Current — 4 2026-01-25T20:44:12 Let's Encrypt
monitor.kul.freebsd.org CT Log Current — 4 2026-02-10T20:20:43 Let's Encrypt
monitor.kwc.freebsd.org CT Log Current — 2 2026-01-01T20:15:36 Let's Encrypt
monitor.nyi.freebsd.org CT Log Current — 4 2026-02-18T20:15:37 Let's Encrypt
monitor.pao.freebsd.org CT Log Current — 2 2026-01-10T20:17:36 Let's Encrypt
monitor.sentex.freebsd.org CT Log Current — 2 2026-01-14T20:33:06 Let's Encrypt
monitor.sjb.freebsd.org CT Log Current — 4 2026-01-25T20:49:20 Let's Encrypt
monitor.son.freebsd.org CT Log Current — 4 2026-02-10T20:25:50 Let's Encrypt
monitor.syd.freebsd.org CT Log Current — 4 2026-02-08T20:33:01 Let's Encrypt
monitor.tuk.freebsd.org CT Log Current — 4 2026-01-31T20:20:41 Let's Encrypt
monitor.twn.freebsd.org CT Log Current — 4 2026-02-16T20:45:33 Let's Encrypt
monitor.your.freebsd.org CT Log Current — 4 2026-01-23T20:17:39 Let's Encrypt
mx1.freebsd.org CT Log Current — 4 2026-02-17T20:15:39 Let's Encrypt
mx2.freebsd.org CT Log Current — 4 2026-02-16T20:51:43 Let's Encrypt
mxrelay.bbt.freebsd.org CT Log Current — 4 2026-01-25T20:54:25 Let's Encrypt
mxrelay.bme.freebsd.org CT Log Current — 2 2025-12-24T20:26:59 Let's Encrypt
mxrelay.bra.freebsd.org CT Log Current — 4 2026-02-01T20:28:52 Let's Encrypt
mxrelay.chi.freebsd.org CT Log Current — 4 2026-02-12T20:32:59 Let's Encrypt
mxrelay.fmt.freebsd.org CT Log Current — 4 2026-02-12T20:38:07 Let's Encrypt
mxrelay.fra.freebsd.org CT Log Current — 2 2025-12-24T20:32:04 Let's Encrypt
mxrelay.isc.freebsd.org CT Log Current — 4 2026-02-16T20:54:50 Let's Encrypt
mxrelay.jinx.freebsd.org CT Log Current — 2 2025-12-24T20:35:09 Let's Encrypt
mxrelay.kul.freebsd.org CT Log Current — 2 2026-01-13T20:20:40 Let's Encrypt
mxrelay.kwc.freebsd.org CT Log Current — 2 2025-12-27T20:15:36 Let's Encrypt
mxrelay.nyi.freebsd.org CT Log Current — 4 2026-02-16T20:57:55 Let's Encrypt
mxrelay.pao.freebsd.org CT Log Current — 2 2026-01-10T20:22:41 Let's Encrypt
mxrelay.sjb.freebsd.org CT Log Current — 4 2026-01-25T20:59:31 Let's Encrypt
mxrelay.son.freebsd.org CT Log Current — 4 2026-02-10T20:30:55 Let's Encrypt
mxrelay.syd.freebsd.org CT Log Current — 4 2026-02-08T20:38:06 Let's Encrypt
mxrelay.tuk.freebsd.org CT Log Current — 4 2026-01-27T20:30:04 Let's Encrypt
mxrelay.twn.freebsd.org CT Log Current — 4 2026-02-18T20:18:43 Let's Encrypt
netbox.freebsd.org CT Log Current — 4 2026-02-16T21:06:08 Let's Encrypt
ns1.freebsd.org DNS Current — — — —
ns2.freebsd.org DNS Current — — — —
papers.freebsd.org CT Log Current — 6 2026-01-22T20:12:35 Let's Encrypt
people.freebsd.org CT Log Current — 4 2026-01-18T20:24:00 Let's Encrypt
pkg-status.freebsd.org CT Log Current — 6 2026-01-22T20:12:38 Let's Encrypt
pkg.fastly.freebsd.org CT Log Current w.sni.global.fastly.net 6 2026-02-17T19:42:59 Certainly
pkg.freebsd.org CT Log Current — 12 2026-02-17T14:23:50 Certainly, Let's Encrypt
pkgmir.geo.freebsd.org CT Log Current — 12 2026-02-17T14:23:50 Certainly, Let's Encrypt
portaudit.freebsd.org CT Log Current wfe0.nyi.freebsd.org 8 2026-02-16T21:06:18 Let's Encrypt
ports.freebsd.org CT Log Current — 8 2026-02-16T21:06:18 Let's Encrypt
portscout-dev.freebsd.org CT Log Current — 2 2025-12-28T20:17:37 Let's Encrypt
portscout.freebsd.org CT Log Current wfe0.nyi.freebsd.org 8 2026-02-16T21:06:13 Let's Encrypt
proxy.freebsd.org DNS Current squid.nyi.freebsd.org — — —
rackmonkey.freebsd.org CT Log Current — 2 2026-01-13T20:29:58 Let's Encrypt
repo.freebsd.org DNS Current gitrepo.freebsd.org — — —
reviews-dev.freebsd.org CT Log Current wfe2-chi.geo.freebsd.org 8 2026-02-03T20:17:46 Let's Encrypt
reviews.freebsd.org CT Log Current — 8 2026-02-03T20:17:46 Let's Encrypt
ron-dev.freebsd.org CT Log Current — 4 2026-01-31T06:26:25 Let's Encrypt
ron.freebsd.org CT Log Current — 4 2026-01-31T06:26:40 Let's Encrypt
security.freebsd.org CT Log Current — 8 2026-02-16T21:06:18 Let's Encrypt
smtp.freebsd.org CT Log Current — 4 2026-02-16T21:09:23 Let's Encrypt
socsvn.freebsd.org CT Log Current — 4 2026-01-25T21:07:51 Let's Encrypt
sso-dev.freebsd.org CT Log Current sso-dev.nyi.freebsd.org 8 2026-01-31T20:30:56 Let's Encrypt
svn-master.freebsd.org CT Log Current — 4 2026-02-04T20:27:56 Let's Encrypt
svn.freebsd.org CT Log Current — 4 2026-01-19T20:38:26 Let's Encrypt
svnmir.freebsd.org CT Log Current svnmir.nyi.freebsd.org 4 2026-01-19T20:38:26 Let's Encrypt
svnweb.freebsd.org CT Log Current — 6 2026-02-03T20:17:50 Let's Encrypt
tinderbox.freebsd.org CT Log Current ci.freebsd.org 4 2026-01-27T20:33:11 Let's Encrypt
translate-dev.freebsd.org CT Log Current — 6 2026-02-15T00:00:00 ZeroSSL
vuxml.freebsd.org CT Log Current web.geo.freebsd.org 4 2025-12-24T20:43:44 Let's Encrypt
web1.nyi.freebsd.org CT Log Current — 2 2026-01-19T20:41:32 Let's Encrypt
web3.nyi.freebsd.org CT Log Current — 2 2026-01-19T20:46:39 Let's Encrypt
wfe0.nyi.freebsd.org CT Log Current — 2 2026-01-19T20:49:44 Let's Encrypt
wfe1.chi.freebsd.org CT Log Current — 2 2026-01-19T20:54:50 Let's Encrypt
wfe1.nyi.freebsd.org CT Log Current — 4 2026-02-17T20:21:49 Let's Encrypt
wfe2.chi.freebsd.org CT Log Current — 2 2026-01-19T20:59:55 Let's Encrypt
wfe2.nyi.freebsd.org CT Log Current — 2 2025-12-23T20:30:53 Let's Encrypt
wfe3.chi.freebsd.org CT Log Current — 2 2026-01-19T21:05:02 Let's Encrypt
wiki-dev.freebsd.org CT Log Current Web3.NyI.freebsd.org 4 2026-01-19T21:08:09 Let's Encrypt
wiki.freebsd.org CT Log Current web3.nyi.freebsd.org 4 2026-01-19T21:11:17 Let's Encrypt
wiki.kr.freebsd.org CT Log Current daemon3.kr.freebsd.org 4 2026-02-21T06:00:20 Let's Encrypt
www-dev.freebsd.org CT Log Current web3.nyi.freebsd.org 4 2026-01-19T21:11:20 Let's Encrypt
www-legacy.freebsd.org CT Log Current wfe0.nyi.freebsd.org 4 2026-01-18T20:23:53 Let's Encrypt
www.bugs.au.freebsd.org CT Log Current — 4 2026-02-20T16:17:50 Let's Encrypt
www.freebsd.org CT Log Current web.geo.freebsd.org 4 2026-01-18T20:24:00 Let's Encrypt
www.kr.freebsd.org CT Log Current — 4 2026-02-21T06:00:20 Let's Encrypt
www.sk.freebsd.org CT Log Current — 2 2026-01-10T02:37:23 Let's Encrypt
www1.fr.freebsd.org CT Log Current — 4 2026-01-31T02:17:35 Let's Encrypt
www2.freebsd.org CT Log Current wfe0.nyi.freebsd.org 4 2026-01-27T20:26:58 Let's Encrypt
www3.freebsd.org DNS Current www.se.freebsd.org — — —
www5.freebsd.org CT Log Current — 4 2026-01-27T20:26:58 Let's Encrypt
www7.freebsd.org CT Log Current — 4 2026-01-27T20:26:58 Let's Encrypt
zmonitor-dev.nyi.freebsd.org CT Log Current — 2 2025-12-24T20:48:50 Let's Encrypt
zmonitor.freebsd.org CT Log Current — 4 2026-01-14T20:41:34 Let's Encrypt
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 1 / 1 records
96.47.72.84
96.47.72.84
AAAA Synchronized 1 / 1 records
2610:1c1:1:606c::50:15
2610:1c1:1:606c::50:15
CAA RFC 8659 §4 Synchronized 2 / 2 records
0 issue "comodoca.com"
0 issue "comodoca.com"
0 issue "letsencrypt.org"
0 issue "letsencrypt.org"
DMARC _dmarc.freebsd.org RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=none
v=DMARC1; p=none
MX RFC 5321 Synchronized 2 / 2 records
30 mx66.freebsd.org.
30 mx66.freebsd.org.
10 mx1.freebsd.org.
10 mx1.freebsd.org.
NS RFC 1035 Synchronized 5 / 5 records
ns4.he.net.
ns5.he.net.
ns1.freebsd.org.
ns4.he.net.
ns2.freebsd.org.
ns3.he.net.
ns3.he.net.
ns1.freebsd.org.
ns5.he.net.
ns2.freebsd.org.
SOA RFC 1035 Synchronized 1 / 1 records
ns0.freebsd.org. hostmaster.freebsd.org. 2026022118 3600 900 1209600 3600
ns0.freebsd.org. hostmaster.freebsd.org. 2026022118 3600 900 1209600 3600
TXT RFC 7208 §4 Synchronized 4 / 4 records
v=spf1 redirect=_spf.freebsd.org
google-site-verification=REWF41fx56YWyINtE9RTibL63H3ZBtek1Dl6oX0TJww
google-site-verification=REWF41fx56YWyINtE9RTibL63H3ZBtek1Dl6oX0TJww
hns-claim:aakkrbzh6oyntnuoh5inq26wzg5iceg43ti726v4aaaaaaaapkk3hln5b5mvy7fny4mh6iaapmwg3wrcc5tw6bbk2dzaeaaaacnun75s
hns-claim:aakkrbzh6oyntnuoh5inq26wzg5iceg43ti726v4aaaaaaaapkk3hln5b5mvy7fny4mh6iaapmwg3wrcc5tw6bbk2dzaeaaaacnun75s
MS=ms11588187
MS=ms11588187
v=spf1 redirect=_spf.freebsd.org
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

d7770283b0a0c8a256f69178b5f760e7fd802e5992257db04a9edae92464bd999a120aa6f506e4c1df89b92fa7460b8a7e886334f04738f4fe506dcda038cc49
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 21 Feb 2026, 18:39 UTC.
Download Raw Intelligence Download Checksum (.sha3)

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL) 
cat dns-intelligence-freebsd.org.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-freebsd.org.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-freebsd.org.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-freebsd.org.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/3134/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for freebsd.org. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035 
dig +noall +answer freebsd.org A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer freebsd.org AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer freebsd.org MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer freebsd.org NS
Query TXT records RFC 1035 
dig +noall +answer freebsd.org TXT

Email Authentication

Check SPF record RFC 7208 
dig +short freebsd.org TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.freebsd.org TXT
Check DKIM key for selector 'dkim' RFC 6376 
dig +short dkim._domainkey.freebsd.org TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer freebsd.org DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer freebsd.org DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd freebsd.org A @1.1.1.1

Transport Security

Check TLSA record for mx66.freebsd.org RFC 7672 
dig +noall +answer _25._tcp.mx66.freebsd.org TLSA
Check TLSA record for mx1.freebsd.org RFC 7672 
dig +noall +answer _25._tcp.mx1.freebsd.org TLSA
Verify TLS certificate on primary MX (mx66.freebsd.org) RFC 6698 
openssl s_client -starttls smtp -connect mx66.freebsd.org:25 -servername mx66.freebsd.org 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.freebsd.org TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.freebsd.org/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.freebsd.org TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.freebsd.org TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer freebsd.org CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer freebsd.org HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer freebsd.org CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/freebsd.org' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (mx66.freebsd.org) RFC 3207 
openssl s_client -starttls smtp -connect mx66.freebsd.org:25 -servername mx66.freebsd.org </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.freebsd.org&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116 
curl -sL https://freebsd.org/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://freebsd.org/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://freebsd.org/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 96.47.72.84 (Team Cymru) 
dig +short 84.72.47.96.origin.asn.cymru.com TXT
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine Verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified 4858 runs
DKIM
Verified 4677 runs
DMARC
Verified 4842 runs
DANE/TLSA
Verified 4661 runs
DNSSEC
Verified 4839 runs
BIMI
Verified 4676 runs
MTA-STS
Verified 4679 runs
TLS-RPT
Verified 4681 runs
CAA
Verified 4673 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035) 
dig +noall +answer freebsd.org A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer freebsd.org AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer freebsd.org MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer freebsd.org NS
Query TXT records (RFC 1035) 
dig +noall +answer freebsd.org TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short freebsd.org TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.freebsd.org TXT
Check DKIM key for selector 'dkim' (RFC 6376) 
dig +short dkim._domainkey.freebsd.org TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer freebsd.org DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer freebsd.org DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd freebsd.org A @1.1.1.1

Transport Security

Check TLSA record for mx66.freebsd.org (RFC 7672) 
dig +noall +answer _25._tcp.mx66.freebsd.org TLSA
Check TLSA record for mx1.freebsd.org (RFC 7672) 
dig +noall +answer _25._tcp.mx1.freebsd.org TLSA
Verify TLS certificate on primary MX (mx66.freebsd.org) (RFC 6698) 
openssl s_client -starttls smtp -connect mx66.freebsd.org:25 -servername mx66.freebsd.org 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.freebsd.org TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.freebsd.org/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.freebsd.org TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.freebsd.org TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer freebsd.org CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer freebsd.org HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer freebsd.org CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/freebsd.org' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (mx66.freebsd.org) (RFC 3207) 
openssl s_client -starttls smtp -connect mx66.freebsd.org:25 -servername mx66.freebsd.org </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.freebsd.org&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt (RFC 9116) 
curl -sL https://freebsd.org/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://freebsd.org/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://freebsd.org/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 96.47.72.84 (Team Cymru) 
dig +short 84.72.47.96.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

freebsd.org

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.