Skip to main content

Engineer's DNS Intelligence Report

switch.com
10 Feb 2026, 15:48 UTC · 22.4s · SHA-3-512: 8e89✱✱✱✱ Verify
Recon ModeRecon Mode Snapshot Re-analyze New Domain
Footprint Microsoft 365
DNS Security & Trust Posture
Risk Level: Low Risk
3 protocols configured, 4 not configured Why we go beyond letter grades
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 37.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
Protected
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Open
Recommended
No CAA records
Configured
SPF, DMARC (quarantine), DKIM
Not Configured
MTA-STS, TLS-RPT, CAA, DNSSEC
Priority Actions 6 total Achievable posture: Low Risk
Medium Add CAA records

Publish CAA DNS records to restrict which Certificate Authorities can issue TLS certificates for your domain. Specify your preferred CA (e.g., letsencrypt.org, digicert.com).

yourdomain.com CAA 0 issue "letsencrypt.org"
Medium Deploy MTA-STS policy

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

_mta-sts.yourdomain.com TXT "v=STSv1; id=20240101"
Low Upgrade DMARC to reject policy

Your DMARC policy is quarantine — spoofed messages are flagged. Upgrading to p=reject blocks them entirely. Review aggregate reports to confirm legitimate senders are aligned.

_dmarc.yourdomain.com TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com"
Low Configure TLS-RPT reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain. Helps diagnose MTA-STS and STARTTLS issues.

_smtp._tls.yourdomain.com TXT "v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com"
Low Enable DNSSEC

DNSSEC (DNS Security Extensions) cryptographically signs DNS responses, preventing attackers from forging DNS answers. Contact your DNS hosting provider to enable DNSSEC signing.

Low Configure BIMI brand logo

Publish a BIMI DNS record pointing to your brand logo (SVG Tiny PS format). For full support in Gmail, you will also need a Verified Mark Certificate (VMC).

default._bimi.yourdomain.com TXT "v=BIMI1; l=https://yourdomain.com/logo.svg"
Registrar (RDAP) LIVE
Network Solutions, LLC
Where domain was purchased
Email Service Provider
Microsoft 365
Email: Enforced
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? Mostly No
Verdict: DMARC policy is quarantine — spoofed messages will be flagged as spam by receiving servers. DKIM keys verified with strong cryptography.

SPF Record RFC 7208 §4 Verified

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

SPF valid with strict enforcement (-all), 5/10 lookups

v=spf1 mx a ip4:66.209.64.12/30 ip4:216.115.64.12/30 ip4:66.209.64.33 ip4:216.115.77.9 ip4:159.183.64.196 include:aspmx.pardot.com include:spf-westus.emailsignatures365.com include:spf.protection.outlook.com include:amazonses.com -all
RFC 7489 §10.1: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
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)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC enforcement is partial (quarantine). -all may preempt DKIM/DMARC evaluation at some receivers. Consider p=reject for full enforcement; ~all is more DMARC-compatible.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Quarantined, not rejected
Success p=quarantine

DMARC policy quarantine (100%) - good protection

v=DMARC1; p=quarantine; rua=mailto:infosec-alerts@switch.com; aspf=s;ruf=mailto:infosec-alerts@switch.com;fo=0
Alignment: SPF strict DKIM relaxed
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
Forensic reports (ruf) configured - many providers ignore these
Upgrade DMARC to reject policy:
_dmarc.yourdomain.com TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com"
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
Monitoring Posture Note: Quarantine sequesters authentication failures while preserving full DMARC forensic telemetry (RFC 7489 §7). Some organizations maintain quarantine rather than reject as a deliberate monitoring strategy — failed messages are processed and reported but sequestered from the inbox. See NIST SP 800-177 Rev. 1 for enforcement tradeoffs.
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 3 selector(s)

s1._domainkey SendGrid
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxKlHzWVU/FGATgYTpaMF5acySXBYdpSb5koyRBOrTvcEHavS+MdxhAFSeV6JjVoN8B4tuTe/FTcCE1vKkXPFv0w+q9ScVwxYhiUn/sDD/8diGGZzbROlJvVCK/r1BjVY0Fe9MbpojHTH7Wn3N+t9lVvbzRRVpnZC8Ip8bYfSYQxj7NTlbwP5S9SarRB4jEHzrOgGzC1sp82h7OOEnK9Mr6vhA/mbzCCWpBnX02DT4kTd1p3sdt3i51Te9T4Fgg3cw0GoHaTT92PdoNE7mOBdHG/INYEzBsGO4iQXWyl/kr/pNqkoe4h+t4OdVOgh4QjBpDmGSraXpyApd+QbZx07PwIDAQAB
s2._domainkey SendGrid
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC78ZmziLUJzGW8Z9kqhNtGIq64ubvd68Sa2X32pHfA3RSAKFNbLa553I58mw2nBK5FQx5QWt3et9ROfk07lfHt9s/JSmsjEgAdJXRznNCqa9v3Ne/CBEcneZCXjyRrZvgEcOQYhrKkRofAHHlQJzCFwvSSVClZpNtsHkTrrFEtnQIDAQAB
selector1._domainkey Microsoft 365
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArioW9i8881OOFyD6HYVOFhr2ALg0c/0rZozDV+1S5BE68oQi0tukTgwTYA2mTUzQagdIzBxBBKe7GYT/5HY79uDP5gY+hzQE6AUDwGrksBRqs/y0hvwpPiu2fE5jom2hr2q+0YdgXDmcjxif5gkotHdTNy3R2ouP23wEj/iKs5/g2WLO5b+tsvem6XzbCTjGxU0PgfH0qAR8zbAUAn+HX0bQvtEKvnVnIDm8yewILTem7JAP9QEBsogW1CoM9hIZyNBFDd3kY+WRi7YU0kF/Ld6SeCwkCR/o5UWL48ywcnxZtwhz7XH5shq+bgqTxiCE/EN7UxcmCojTM1nwKaZVTQIDAQAB;
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? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Microsoft 365

Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.

Recommended alternative: MTA-STS


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 has neither DANE nor MTA-STS. Since Microsoft 365 does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

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?
Verdict: No brand protection configured. Any CA can issue certificates and no brand logo verification in place.

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Warning

Does this domain restrict who can issue TLS certificates? No

No CAA records found - any CA can issue certificates



Domain Security Methodology Can DNS responses be tampered with in transit?

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Domain does not use DNSSEC. Enable in your registrar's DNS settings (look for "DNSSEC" or "DS records" section).

NS Delegation Verified

2 nameserver(s) configured

Nameservers: ns1.switchnap.com ns2.switchnap.com
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [14800437203743243828 7vns1nwz6fdvpfy7zqznbq90dstwdxcx _df5b2c45ye1jzqqyebgz9shdolln3ty autodesk-domain-verification=r--sEKrKf-t-gR3bVGNO cloudflare_dashboard_sso=244be4fe3b59aa8f8643b3f9ba54ecf6 docusign=eccb69ed-77b4-4444-8849-a88b15845064 jamf-site-verification=c5vuJLmTB-CeH6R7jiFiGg openai-domain-verification=dv-TnBvOHAbP1NFm4HgqENsAkKC]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

141.193.213.20
141.193.213.21
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

0 switch-com.mail.protection.outlook.com.
Priority + mail server for email delivery
Microsoft 365

SRVServices

_sipfederationtls._tcp: 100 1 5061 ae.supernap.com.
_sip._tls: 100 1 443 ae.supernap.com.
SIP, XMPP, or other service endpoints
Web: Reachable (2 IPv4, 0 IPv6) Mail: 1 server Services: 2 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 167 subdomains discovered
How did we find these?
Certificate Transparency Logs Unavailable The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962).
1064 certificates analyzed current expired Source: Certificate Transparency Logs
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
CT Log Expired 3
CT Log Expired 10
CT Log Expired 22
CT Log Expired 24
CT Log Expired 2
CT Log Expired 2
CT Log Expired 29
CT Log Expired 2
CT Log Expired 10
CT Log Expired 2
CT Log Expired 6
CT Log Expired 2
CT Log Expired 27
CT Log Expired 20
CT Log Expired 5
CT Log Expired 3
CT Log Expired 3
CT Log Expired 20
CT Log Expired 2
CT Log Expired 4
CT Log Expired 2
CT Log Expired 3
CT Log Expired 2
CT Log Expired 4
CT Log Expired 10
CT Log Expired 2
CT Log Expired 16
CT Log Expired 3
CT Log Expired 3
CT Log Expired 16
CT Log Expired 5
CT Log Expired 18
CT Log Expired 3
CT Log Expired 12
CT Log Expired 3
CT Log Expired 4
CT Log Expired 6
CT Log Expired 6
CT Log Expired 10
CT Log Expired 10
CT Log Expired 7
CT Log Expired 7
CT Log Expired 33
CT Log Expired 1
CT Log Expired 5
CT Log Expired 2
CT Log Expired 12
CT Log Expired 13
CT Log Expired 6
CT Log Expired 42
CT Log Expired 2
CT Log Expired 9
CT Log Expired 2
CT Log Expired 3
CT Log Expired 4
CT Log Expired 3
CT Log Expired 7
CT Log Expired 1
CT Log Expired 2
CT Log Expired 12
CT Log Expired 5
CT Log Expired 76
CT Log Expired 6
CT Log Expired 1
CT Log Expired 16
CT Log Expired 6
CT Log Expired 13
CT Log Expired 4
CT Log Expired 5
CT Log Expired 20
CT Log Expired 11
CT Log Expired 4
CT Log Expired 2
CT Log Expired 1
CT Log Expired 6
CT Log Expired 2
CT Log Expired 5
CT Log Expired 1
CT Log Expired 2
CT Log Expired 12
CT Log Expired 9
CT Log Expired 12
CT Log Expired 21
CT Log Expired 16
CT Log Expired 4
CT Log Expired 16
CT Log Expired 13
CT Log Expired 2
CT Log Expired 3
CT Log Expired 21
CT Log Expired 2
CT Log Expired 2
CT Log Expired 74
CT Log Expired 8
CT Log Expired 12
CT Log Expired 9
CT Log Expired 25
CT Log Expired 14
CT Log Expired 8
CT Log Expired 10
CT Log Expired 12
CT Log Expired 1
CT Log Expired 3
CT Log Expired 3
CT Log Expired 3
CT Log Expired 18
CT Log Expired 2
CT Log Expired 3
CT Log Expired 10
CT Log Expired 6
CT Log Expired 2
CT Log Expired 2
CT Log Expired 9
CT Log Expired 2
CT Log Expired 2
CT Log Expired 14
CT Log Expired 5
CT Log Expired 14
CT Log Expired 2
CT Log Expired 4
CT Log Expired 2
CT Log Expired 3
CT Log Expired 2
CT Log Expired 2
CT Log Expired 4
CT Log Expired 5
CT Log Expired 4
CT Log Expired 4
CT Log Expired 10
CT Log Expired 7
CT Log Expired 7
CT Log Expired 1
CT Log Expired 5
CT Log Expired 10
CT Log Expired 6
CT Log Expired 18
CT Log Expired 9
CT Log Expired 2
CT Log Expired 3
CT Log Expired 4
CT Log Expired 3
CT Log Expired 7
CT Log Expired 5
CT Log Expired 1
CT Log Expired 16
CT Log Expired 13
CT Log Expired 4
CT Log Expired 15
CT Log Expired 7
CT Log Expired 4
CT Log Expired 2
CT Log Expired 1
CT Log Expired 6
CT Log Expired 2
CT Log Expired 5
CT Log Expired 1
CT Log Expired 9
CT Log Expired 6
CT Log Expired 9
CT Log Expired 7
CT Log Expired 12
CT Log Expired 60
CT Log Expired 1
CT Log Expired 2
CT Log Expired 2
CT Log Expired 3
CT Log Expired 6
Δ Changes Detected: TXT Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
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 2 / 2 records
141.193.213.20
141.193.213.20
141.193.213.21
141.193.213.21
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.switch.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=quarantine; rua=mailto:infosec-alerts@switch.com; aspf=s;ruf=mailto:infosec-alerts@switch.com;fo=0
v=DMARC1; p=quarantine; rua=mailto:infosec-alerts@switch.com; aspf=s;ruf=mailto:infosec-alerts@switch.com;fo=0
MX RFC 5321 Synchronized 1 / 1 records
0 switch-com.mail.protection.outlook.com.
0 switch-com.mail.protection.outlook.com.
NS RFC 1035 Synchronized 2 / 2 records
ns2.switchnap.com.
ns2.switchnap.com.
ns1.switchnap.com.
ns1.switchnap.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns1.switch.com. hostmaster.switch.com. 2026020903 10800 900 1209600 3600
ns1.switch.com. hostmaster.switch.com. 2026020903 10800 900 1209600 3600
TXT RFC 7208 §4 Propagating 16 / 4 records
anthropic-domain-verification-a6s6hn=FfOjvleGr00iAYD4DdvARaGIm
autodesk-domain-verification=r--sEKrKf-t-gR3bVGNO
openai-domain-verification=dv-TnBvOHAbP1NFm4HgqENsAkKC
v=spf1 mx a ip4:66.209.64.12/30 ip4:216.115.64.12/30 ip4:66.209.64.33 ip4:216.115.77.9 ip4:159.183.64.196 include:aspmx.pardot.com include:spf-westus.emailsignatures365.com include:spf.protection.outlook.com include:amazonses.com -all
wKAkPnfWJLooM5ru28K4of7q6F7V4fPeyK/NaCYGRggRASi/PgyNfHQhVrCPqRmulFeXa3MXb82Vcac8SjHMVA==
zapier-domain-verification-challenge=b2b83747-0d89-4105-bffd-d8003c7347cf
_df5b2c45ye1jzqqyebgz9shdolln3ty
openai-domain-verification=dv-TnBvOHAbP1NFm4HgqENsAkKC
autodesk-domain-verification=r--sEKrKf-t-gR3bVGNO
zapier-domain-verification-challenge=b2b83747-0d89-4105-bffd-d8003c7347cf
v=spf1 mx a ip4:66.209.64.12/30 ip4:216.115.64.12/30 ip4:66.209.64.33 ip4:216.115.77.9 ip4:159.183.64.196 include:aspmx.pardot.com include:spf-westus.emailsignatures365.com include:spf.protection.outlook.com include:amazonses.com -all
docusign=eccb69ed-77b4-4444-8849-a88b15845064
jamf-site-verification=c5vuJLmTB-CeH6R7jiFiGg
cloudflare_dashboard_sso=244be4fe3b59aa8f8643b3f9ba54ecf6
14800437203743243828
atlassian-domain-verification=cT0xOEbvfbUfGM6sn1jO4ExnxMFLUj4Rs9+No8N2S3asroS8cB/Iqtf/9zQIGsJA
7vns1nwz6fdvpfy7zqznbq90dstwdxcx
miro-verification=bd9393badd1c3084f4cc0b917dd5c846a1117aa1
smartsheet-site-validation=jfECYHaRo13bacunUvXsXbrM2QyFR0Up
google-site-verification=yPMBxwRV6J4ZiXFc_khNFrX57ZoqrqtAmelb2JI2Q4w
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.

8e89471a1c75025e563183421a6d909fca563cbe6651d9f9cdc7675fbfeeec8507db70ece1e2d1db9f77340270ea434bc7aea301a5770eeafe31ca95ab0bd612
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 10 Feb 2026, 15:48 UTC.

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-switch.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-switch.com.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-switch.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-switch.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/530/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 switch.com. 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 switch.com A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer switch.com AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer switch.com MX
Query NS records (nameservers) RFC 1035
dig +noall +answer switch.com NS
Query TXT records RFC 1035
dig +noall +answer switch.com TXT

Email Authentication

Check SPF record RFC 7208
dig +short switch.com TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.switch.com TXT
Check DKIM key for selector 's1' RFC 6376
dig +short s1._domainkey.switch.com TXT
Check DKIM key for selector 's2' RFC 6376
dig +short s2._domainkey.switch.com TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.switch.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records RFC 9460
dig +noall +answer switch.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer switch.com CDS

Infrastructure Intelligence

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

Transport Security

Test STARTTLS on primary MX (switch-com.mail.protection.outlook.com) RFC 3207
openssl s_client -starttls smtp -connect switch-com.mail.protection.outlook.com:25 -servername switch-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.switch.com&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://switch.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 141.193.213.20 (Team Cymru)
dig +short 20.213.193.141.origin.asn.cymru.com TXT
ASN lookup for 141.193.213.21 (Team Cymru)
dig +short 21.213.193.141.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 4898 runs
DKIM
Verified 4716 runs
DMARC
Verified 4881 runs
DANE/TLSA
Verified 4700 runs
DNSSEC
Verified 4879 runs
BIMI
Verified 4715 runs
MTA-STS
Verified 4718 runs
TLS-RPT
Verified 4720 runs
CAA
Verified 4712 runs
Maturity: Development Verified Consistent Gold Gold Master
Running Multi-Source Intelligence Audit

switch.com

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.