DNS Tool

Engineer's DNS Intelligence Report

Generated 21 Feb 2026, 05:38 UTC
Duration 13.5s
Version v26.21.55
Integrity 5eefed5cebee08b1c0cb77bb983fdfc102ff29c812287377c9a3bfb58ab5eca73048bdcfc56a39cc333c6200b0e68ada1475ab6dd2bb1c5a629c58aaae3e27a3

TLP:AMBER

Limited disclosure — recipients may share within their organization only

Subject Domain

cisa.gov

Engineer's DNS Intelligence Report

cisa.gov

21 Feb 2026, 05:38 UTC · 13.5s ·v26.21.55 · SHA-3-512: 5eef✱✱✱✱ Verify

Executive Methodology

Recon Mode Snapshot Re-analyze New Domain

Footprint Proofpoint 3 SaaS Services

DNS Security & Trust Posture

Risk Level: Low Risk

4 protocols configured, 4 not configured, 1 unavailable on provider Why we go beyond letter grades

Email Spoofing

Protected

Brand Impersonation

Not Setup

DNS Tampering

Protected

Certificate Control

Open

Configured

SPF (hard fail), DMARC (reject), DKIM, DNSSEC

Not Configured

MTA-STS, TLS-RPT, BIMI, CAA

Unavailable on Provider

DANE

Priority Actions 4 total Achievable posture: Secure

Low Add BIMI Record

Your domain has DMARC reject — you qualify for BIMI, which displays your brand logo in receiving email clients that support it (Gmail, Apple Mail, Yahoo).

BIMI displays your verified brand logo next to your emails in supporting mail clients.

Field	Value
Type	`TXT`
Host	`default._bimi.cisa.gov` (BIMI default record)
Value	`v=BIMI1; l=https://cisa.gov/brand/logo.svg`

RFC 9495

Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.

Field	Value
Type	`CAA`
Host	`cisa.gov` (root of domain — adjust CA to match your provider)
Value	`0 issue "letsencrypt.org"`

RFC 8659

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.

TLS-RPT sends you reports about TLS connection failures to your mail servers.

Field	Value
Type	`TXT`
Host	`_smtp._tls.cisa.gov` (SMTP TLS reporting record)
Value	`v=TLSRPTv1; rua=mailto:tls-reports@cisa.gov`

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.

Field	Value
Type	`TXT`
Host	`_mta-sts.cisa.gov` (MTA-STS policy record)
Value	`v=STSv1; id=cisa.gov`

RFC 8461

Registrar (RDAP) OBSERVED LIVE

get.gov (Registrant: REDACTED FOR PRIVACY)

Where domain was purchased

Email Service Provider INFERRED

Microsoft 365

Strongly 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? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes

Success -all 3/10 lookups

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

v=spf1 include:spf.dhs.gov include:spf.protection.outlook.com include:spf-00376703.gpphosted.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 is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Yes — reject policy

Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; pct=100; rua=mailto:DMARC@hq.dhs.gov, mailto:reports@dmarc.cyber.dhs.gov

Alignment: SPF relaxed DKIM relaxed

No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing

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 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.

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)

Mail routed through Proofpoint (security gateway) — DKIM signed by Microsoft 365 (sending platform). This is a standard enterprise architecture.

selector1._domainkey Microsoft 365

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv32BRAJaAOsxAp31ZqQwd7RYfbYowvb3F7lq8WQEyasI6w7Gm0bxPW57TFM04fM5flf1PYyCDSa3ckQzSQLYmMx9HiXYJYF1Dpk9PnjTarbdR9mm9fc7iBXT2pTFNJw+SRMH3NRrbkefv8GqqLdJotgCl2vWoyRlfKCANCFq5Bbq4qaztXqU/cHRurG8ZVSF7ZrhY4EBKvpzAyIisrf2g2Gky+vO4LTMrgZeNnA/OyHmWmvlUC58e06jBLSysYyh19O4MiU5eUhuT7MYTLWz6fIOl4PaT9HkmM0rH/fgcGSYc8ajCsrvxYA8LgoWR9IzYq5vYzDWLxSo/J0c+6pVWQIDAQAB;

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

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Yes — all authorized

Success

All 1 external reporting domains properly authorized

External Domain	Authorization	Auth Record
`hq.dhs.gov`	Authorized	`v=DMARC1`

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 — Proofpoint does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Proofpoint

Proofpoint is a security gateway with shared MX infrastructure. It does not publish per-customer TLSA records.

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 Proofpoint 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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3), but no BIMI brand verification and no CAA certificate restriction (RFC 8659) — visual impersonation via lookalike domains and unrestricted certificate issuance remain open vectors

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

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

security.txt properly configured

Contact

mailto:IRT@cisa.dhs.gov

mailto:TOC@cisa.dhs.gov

Expires

                                        2026-10-01
                                        
                                            Valid

Encryption

https://www.cisa.gov/contact-us

Hiring

Source: https://cisa.gov/.well-known/security.txt

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)

Type	Detail	Severity	Confidence
`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.

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? No No MTA-STS or DANE — mail transport encryption is opportunistic only

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

Policy Assessment Primary

Proofpoint enforces TLS on managed mail transport

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
`mxa-00376703.gslb.gpphosted.com`		TLSv1.2	ECDHE-RSA-AES256-GCM-SHA384	Valid Expires: 2026-12-10 (292 days) Issuer: Sectigo Limited
`mxb-00376703.gslb.gpphosted.com`		TLSv1.2	ECDHE-RSA-AES256-GCM-SHA384	Valid Expires: 2026-12-10 (292 days) Issuer: Sectigo Limited

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASN	Name	Country
`AS16625`	Akamai Technologies, Inc.	US
`AS20940`	Akamai International B.V.	US

IPv4 Mappings:

23.64.138.233 → AS16625 (23.64.138.0/23)

IPv6 Mappings:

2600:1404:6400:1983::3ff9 → AS20940 (2600:1404:6400::/48)

2600:1404:6400:198c::3ff9 → AS20940 (2600:1404:6400::/48)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 3 services

3 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.

Service	Verification Record
Google Workspace	`google-site-verification=BNRBfY90BM54Mf_pgL4Eg07IkwbGvq5nsdZCOYadDlM`
Microsoft 365	`MS=ms41452370`
Adobe	`adobe-idp-site-verification=edfd88b4c2bdf65395c78b55da3580466eefa9aa874d5bcfb853...`

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 ECDSA P-256/SHA-256 Modern

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: ECDSA P-256/SHA-256 — MUST implement, recommended default (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):

2371 13 2 5F15E517D7A353D755D9D3F8548A3475CE88A738E62B766F5E33CFC4163AB934

NS Delegation Verified

3 nameserver(s) configured

Nameservers: blue.foundationdns.com blue.foundationdns.net blue.foundationdns.org

Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (3 differences found)

Resolver Differences:

TXT: OpenDNS returned different results: [MS=ms36056523 MS=ms41452370 MS=ms53160703 _e01yoinuk3n6xrtnc8q3m9bdjyihdd7 _rr8gice4wv589e4uxop5zqhh6gbqh32 _tufdw17aa2wht723upz8w56htpvpgkw f188eb27-a746-4aa8-b160-eb68b0aab05d google-site-verification=BNRBfY90BM54Mf_pgL4Eg07IkwbGvq5nsdZCOYadDlM google-site-verification=wsLVyeZYgv0NLikdmfm2m3XPP-986Ylo8XxUkrjIOvA]

A: Quad9 returned different results: [184.27.230.106]

A: DNS4EU returned different results: [2.18.140.150]

This may indicate DNS propagation in progress or geo-based DNS routing.

CDS / CDNSKEY (DNSSEC Automation) RFC 7344 Success CDS CDNSKEY

Full RFC 8078 automated DNSSEC key rollover signaling detected (CDS + CDNSKEY)

Key Tag	Algorithm	Digest Type	Digest
`2371`	ECDSAP256SHA256	2

CDNSKEY Records:

Flags	Protocol	Algorithm	Public Key
`257`	3	ECDSAP256SHA256

Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

23.64.138.233

Where the domain points for web traffic

AAAAIPv6 Address

2600:1404:6400:1983::3ff9

2600:1404:6400:198c::3ff9

IPv6 ready

MXMail Servers

10 mxa-00376703.gslb.gpphosted.com.

10 mxb-00376703.gslb.gpphosted.com.

Priority + mail server for email delivery

Microsoft 365

SRVServices

_sipfederationtls._tcp: 100 3600 5061 sipfed.online.lync.com.

SIP, XMPP, or other service endpoints

Web: Reachable (1 IPv4, 2 IPv6) Mail: 2 servers Services: 1 endpoint

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 75 subdomains discovered

How did we find these?

CT logs unavailable 75 current 0 expired 19 CNAMEs Source: Certificate Transparency + DNS Intelligence

Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.

Subdomain	Source	Status	Provider / CNAME	Certificates	First Seen	Issuer(s)
`access-dev.cisa.gov`	CT Log	Current	—	3	2026-01-12T12:25:51	Google Trust Services
`access-uat.cisa.gov`	CT Log	Current	—	3	2026-01-12T12:25:51	Google Trust Services
`access.cisa.gov`	CT Log	Current	—	3	2026-01-12T12:25:51	Google Trust Services
`cge.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`ci.protectivedns.cisa.gov`	CT Log	Current	—	33	2026-01-22T22:27:58	Let's Encrypt, Amazon
`confluence.protectivedns.cisa.gov`	CT Log	Current	—	1	2025-09-14T00:00:00	Amazon
`connect.cisa.gov`	CT Log	Current	—	12	2026-01-02T00:00:00	Sectigo Limited, Google Trust Services
`csccust.development.gateway.cisa.gov`	CT Log	Current	—	3	2025-06-17T00:00:00	DigiCert Inc
`csccust.gateway.cisa.gov`	CT Log	Current	—	21	2025-11-04T00:00:00	DigiCert Inc
`cybermarketplace.cisa.gov`	CT Log	Current	`cybermarketplace.cisa.gov.edgekey.net`	33	2026-01-15T00:00:00	DigiCert Inc
`dashboard.development.gateway.cisa.gov`	CT Log	Current	—	3	2025-06-17T00:00:00	DigiCert Inc
`dashboard.gateway.cisa.gov`	CT Log	Current	`dashboard.gateway.cisa.gov.edgekey.net`	33	2026-01-15T00:00:00	DigiCert Inc
`dev.protectivedns.cisa.gov`	CT Log	Current	—	11	2026-01-22T22:27:58	Let's Encrypt, Amazon
`development.gateway.cisa.gov`	CT Log	Current	—	7	2026-02-04T17:25:13	Google Trust Services, DigiCert Inc
`devlearning.cisa.gov`	CT Log	Current	—	19	2025-11-21T00:00:00	DigiCert Inc
`edit-preview.cisa.gov`	CT Log	Current	—	2	2025-10-30T00:00:00	DigiCert Inc
`edit-staging.cisa.gov`	CT Log	Current	`edit-staging.cisa.gov.edgekey-staging.net`	2	2025-10-30T00:00:00	DigiCert Inc
`edit-testint.cisa.gov`	CT Log	Current	`edit-testint.cisa.gov.edgekey-staging.net`	2	2025-10-30T00:00:00	DigiCert Inc
`edit.cisa.gov`	CT Log	Current	—	2	2025-10-30T00:00:00	DigiCert Inc
`eo13650.development.gateway.cisa.gov`	CT Log	Current	—	3	2025-06-17T00:00:00	DigiCert Inc
`eo13650.gateway.cisa.gov`	CT Log	Current	—	21	2025-11-04T00:00:00	DigiCert Inc
`esubmissions.pciims.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`expo.cisa.gov`	CT Log	Current	—	6	2025-06-18T00:00:00	DigiCert Inc
`gateway.cisa.gov`	CT Log	Current	—	37	2026-02-04T17:25:13	Google Trust Services, DigiCert Inc
`gitlab-launchpad.cisa.gov`	CT Log	Current	—	6	2025-06-18T00:00:00	DigiCert Inc
`gwids.cisa.gov`	CT Log	Current	—	30	2026-02-15T18:08:59	Google Trust Services, DigiCert Inc
`gwypt1.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`gwypt2.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`gwypt3.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`gwypt4.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`idaas.cisa.gov`	CT Log	Current	`ssp-msp.customdomains.okta-gov.com`	2	2026-01-13T00:00:00	DigiCert Inc
`jira.protectivedns.cisa.gov`	CT Log	Current	—	1	2025-09-08T00:00:00	Amazon
`launchpad.cisa.gov`	CT Log	Current	—	6	2025-06-18T00:00:00	DigiCert Inc
`lb.cisa.gov`	CT Log	Current	—	3	2026-01-12T12:25:51	Google Trust Services
`learning.cisa.gov`	CT Log	Current	—	19	2025-11-21T00:00:00	DigiCert Inc
`login.access.cisa.gov`	CT Log	Current	—	2	2025-04-29T00:00:00	DigiCert Inc
`login.cisa.gov`	DNS	Current	`cisa-partner.customdomains.okta-dnssec.com`	2	2026-01-12	Google Trust Services
`malware-anonymous.cisa.gov`	CT Log	Current	`mng-prd-anon-1475162682.us-gov-east-1.elb.amazonaws.com`	1	2025-07-11T00:00:00	DigiCert Inc
`malware.cisa.gov`	CT Log	Current	`mng-prd-app2-669847399.us-gov-east-1.elb.amazonaws.com`	1	2025-07-11T00:00:00	DigiCert Inc
`management.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`myservices.cisa.gov`	CT Log	Current	—	2	2026-01-02T21:30:41	Let's Encrypt
`niccs.cisa.gov`	CT Log	Current	—	2	2025-10-21T00:00:00	DigiCert Inc
`pciims.cisa.gov`	CT Log	Current	`pciims.cisa.gov.edgekey.net`	34	2026-01-15T00:00:00	DigiCert Inc
`pciims.development.gateway.cisa.gov`	CT Log	Current	—	3	2025-06-17T00:00:00	DigiCert Inc
`pciims.gateway.cisa.gov`	CT Log	Current	—	12	2025-08-06T00:00:00	DigiCert Inc
`pciimspt4.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`piv.access-dev.cisa.gov`	CT Log	Current	—	1	2025-07-18T00:00:00	DigiCert Inc
`piv.access-uat.cisa.gov`	CT Log	Current	—	1	2025-08-19T00:00:00	DigiCert Inc
`piv.access.cisa.gov`	CT Log	Current	—	1	2025-08-19T00:00:00	DigiCert Inc
`piv.softwaresecurity.cisa.gov`	CT Log	Current	—	1	2026-01-23T00:00:00	DigiCert Inc
`presidentscup.cisa.gov`	CT Log	Current	—	12	2025-06-18T00:00:00	DigiCert Inc
`preview.cisa.gov`	CT Log	Current	`preview.cisa.gov.edgekey.net`	34	2026-02-09T00:00:00	DigiCert Inc
`protectivedns.cisa.gov`	CT Log	Current	—	86	2026-01-22T22:27:58	Let's Encrypt, Sectigo Limited, Google Trust Services, Amazon
`registration.gateway.cisa.gov`	CT Log	Current	`registration.gateway.cisa.gov.edgekey.net`	33	2026-01-15T00:00:00	DigiCert Inc
`registration.pciims.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`sftp.gwids.cisa.gov`	CT Log	Current	—	1	2025-08-21T00:00:00	DigiCert Inc
`softwaresecurity.cisa.gov`	CT Log	Current	—	1	2026-01-23T00:00:00	DigiCert Inc
`sram.gateway.cisa.gov`	CT Log	Current	—	9	2025-07-22T00:00:00	DigiCert Inc
`stage.gateway.cisa.gov`	CT Log	Current	—	2	2025-06-25T00:00:00	DigiCert Inc
`stage.tripwire.cisa.gov`	CT Log	Current	—	1	2025-06-03T00:00:00	DigiCert Inc
`staging.cisa.gov`	CT Log	Current	`Staging.cisa.gov.edgekey-staging.net`	34	2026-02-09T00:00:00	DigiCert Inc
`test-ci.protectivedns.cisa.gov`	CT Log	Current	—	25	2026-01-22T22:27:58	Let's Encrypt, Amazon
`test.protectivedns.cisa.gov`	CT Log	Current	—	11	2026-01-22T22:27:58	Let's Encrypt, Amazon
`testint.cisa.gov`	CT Log	Current	`testint.cisa.gov.edgekey-staging.net`	2	2025-10-30T00:00:00	DigiCert Inc
`tripwire.cisa.gov`	CT Log	Current	`tripwire.cisa.gov.edgekey.net`	35	2026-02-09T00:00:00	DigiCert Inc
`uat.cisa.gov`	CT Log	Current	—	4	2026-01-08T13:46:41	Google Trust Services
`uat.gwids.cisa.gov`	CT Log	Current	—	18	2025-08-12T00:00:00	DigiCert Inc
`us-cert.cisa.gov`	CT Log	Current	`us-cert.cisa.gov.edgekey.net`	34	2026-02-09T00:00:00	DigiCert Inc
`www.cisa.gov`	CT Log	Current	`www.cisa.gov.edgekey.net`	35	2026-01-14T00:00:00	DigiCert Inc
`www.gwids.cisa.gov`	CT Log	Current	—	18	2025-08-12T00:00:00	DigiCert Inc
`www.login.access.cisa.gov`	CT Log	Current	—	1	2025-04-24T00:00:00	DigiCert Inc
`www.malware.cisa.gov`	CT Log	Current	—	1	2025-07-11T00:00:00	DigiCert Inc
`www.niccs.cisa.gov`	CT Log	Current	`www.niccs.cisa.gov.edgekey.net`	2	2025-10-21T00:00:00	DigiCert Inc
`www.ssp.cisa.gov`	CT Log	Current	`ssp.customdomains.okta-gov.com`	3	2025-09-12T00:00:00	DigiCert Inc
`www.us-cert.cisa.gov`	CT Log	Current	`www.us-cert.cisa.gov.edgekey.net`	34	2026-02-09T00:00:00	DigiCert Inc

Export Recon (CSV)

Δ Changes Detected: A AAAA 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 Propagating 1 / 1 records

23.64.138.233

23.210.150.135

AAAA Propagating 2 / 2 records

2600:1404:6400:1983::3ff9

2600:1407:7400:b95::3ff9

2600:1404:6400:198c::3ff9

2600:1407:7400:b80::3ff9

CAA RFC 8659 §4 0 / 0 records

No records

DMARC _dmarc.cisa.gov RFC 7489 §6.3 Synchronized 1 / 1 records

v=DMARC1; p=reject; pct=100; rua=mailto:DMARC@hq.dhs.gov, mailto:reports@dmarc.cyber.dhs.gov

MX RFC 5321 Synchronized 2 / 2 records

10 mxa-00376703.gslb.gpphosted.com.

10 mxb-00376703.gslb.gpphosted.com.

NS RFC 1035 Synchronized 3 / 3 records

blue.foundationdns.net.

blue.foundationdns.com.

blue.foundationdns.org.

blue.foundationdns.net.

blue.foundationdns.com.

blue.foundationdns.org.

SOA RFC 1035 Synchronized 1 / 1 records

blue.foundationdns.com. dns.cloudflare.com. 2396949020 10000 2400 604800 1800

TXT RFC 7208 §4 11 / 0 records

google-site-verification=BNRBfY90BM54Mf_pgL4Eg07IkwbGvq5nsdZCOYadDlM

—

google-site-verification=wsLVyeZYgv0NLikdmfm2m3XPP-986Ylo8XxUkrjIOvA

—

MS=ms41452370

—

f188eb27-a746-4aa8-b160-eb68b0aab05d

—

_rr8gice4wv589e4uxop5zqhh6gbqh32

—

_e01yoinuk3n6xrtnc8q3m9bdjyihdd7

—

_tufdw17aa2wht723upz8w56htpvpgkw

—

v=spf1 include:spf.dhs.gov include:spf.protection.outlook.com include:spf-00376703.gpphosted.com -all

—

MS=ms53160703

—

adobe-idp-site-verification=edfd88b4c2bdf65395c78b55da3580466eefa9aa874d5bcfb853692813e80515

—

MS=ms36056523

—

DNS History Timeline BETA

Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key

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.

5eefed5cebee08b1c0cb77bb983fdfc102ff29c812287377c9a3bfb58ab5eca73048bdcfc56a39cc333c6200b0e68ada1475ab6dd2bb1c5a629c58aaae3e27a3

Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 21 Feb 2026, 05:38 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-cisa.gov.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-cisa.gov.json

Python 3 (cross-platform)

python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-cisa.gov.json','rb').read()).hexdigest())"

sha3sum (coreutils 9+)

sha3sum -a 512 dns-intelligence-cisa.gov.json

Compare the output against the .sha3 file or the checksum API at /api/analysis/2876/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 cisa.gov. 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 cisa.gov A

Query AAAA records (IPv6) RFC 1035

dig +noall +answer cisa.gov AAAA

Query MX records (mail servers) RFC 1035

dig +noall +answer cisa.gov MX

Query NS records (nameservers) RFC 1035

dig +noall +answer cisa.gov NS

Query TXT records RFC 1035

dig +noall +answer cisa.gov TXT

Email Authentication

Check SPF record RFC 7208

dig +short cisa.gov TXT | grep -i spf

Check DMARC policy RFC 7489

dig +short _dmarc.cisa.gov TXT

Check DKIM key for selector 'selector1' RFC 6376

dig +short selector1._domainkey.cisa.gov TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035

dig +dnssec +noall +answer cisa.gov DNSKEY

Check DNSSEC DS records RFC 4035

dig +noall +answer cisa.gov DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035

dig +dnssec +cd cisa.gov A @1.1.1.1

Transport Security

Check TLSA record for mxa-00376703.gslb.gpphosted.com RFC 7672

dig +noall +answer _25._tcp.mxa-00376703.gslb.gpphosted.com TLSA

Check TLSA record for mxb-00376703.gslb.gpphosted.com RFC 7672

dig +noall +answer _25._tcp.mxb-00376703.gslb.gpphosted.com TLSA

Verify TLS certificate on primary MX (mxa-00376703.gslb.gpphosted.com) RFC 6698

openssl s_client -starttls smtp -connect mxa-00376703.gslb.gpphosted.com:25 -servername mxa-00376703.gslb.gpphosted.com 2>/dev/null | openssl x509 -noout -subject -dates

Check MTA-STS DNS record RFC 8461

dig +short _mta-sts.cisa.gov TXT

Fetch MTA-STS policy file RFC 8461

curl -sL https://mta-sts.cisa.gov/.well-known/mta-sts.txt

Check TLS-RPT record RFC 8460

dig +short _smtp._tls.cisa.gov TXT

Brand & Trust

Check BIMI record BIMI Draft

dig +short default._bimi.cisa.gov TXT

Check CAA records (certificate authority authorization) RFC 8659

dig +noall +answer cisa.gov CAA

DNS Records

Check HTTPS/SVCB records RFC 9460

dig +noall +answer cisa.gov HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344

dig +noall +answer cisa.gov CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083

curl -sL 'https://rdap.org/domain/cisa.gov' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (mxa-00376703.gslb.gpphosted.com) RFC 3207

openssl s_client -starttls smtp -connect mxa-00376703.gslb.gpphosted.com:25 -servername mxa-00376703.gslb.gpphosted.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962

curl -s 'https://crt.sh/?q=%25.cisa.gov&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://cisa.gov/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://cisa.gov/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://cisa.gov/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 23.64.138.233 (Team Cymru)

dig +short 233.138.64.23.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 4877 runs

DKIM

Verified 4695 runs

DMARC

Verified 4860 runs

DANE/TLSA

Verified 4679 runs

DNSSEC

Verified 4858 runs

BIMI

Verified 4694 runs

MTA-STS

Verified 4697 runs

TLS-RPT

Verified 4699 runs

CAA

Verified 4691 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 cisa.gov A

Query AAAA records (IPv6) (RFC 1035)

dig +noall +answer cisa.gov AAAA

Query MX records (mail servers) (RFC 1035)

dig +noall +answer cisa.gov MX

Query NS records (nameservers) (RFC 1035)

dig +noall +answer cisa.gov NS

Query TXT records (RFC 1035)

dig +noall +answer cisa.gov TXT

Email Authentication

Check SPF record (RFC 7208)

dig +short cisa.gov TXT | grep -i spf

Check DMARC policy (RFC 7489)

dig +short _dmarc.cisa.gov TXT

Check DKIM key for selector 'selector1' (RFC 6376)

dig +short selector1._domainkey.cisa.gov TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035)

dig +dnssec +noall +answer cisa.gov DNSKEY

Check DNSSEC DS records (RFC 4035)

dig +noall +answer cisa.gov DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035)

dig +dnssec +cd cisa.gov A @1.1.1.1

Transport Security

Check TLSA record for mxa-00376703.gslb.gpphosted.com (RFC 7672)

dig +noall +answer _25._tcp.mxa-00376703.gslb.gpphosted.com TLSA

Check TLSA record for mxb-00376703.gslb.gpphosted.com (RFC 7672)

dig +noall +answer _25._tcp.mxb-00376703.gslb.gpphosted.com TLSA

Verify TLS certificate on primary MX (mxa-00376703.gslb.gpphosted.com) (RFC 6698)

openssl s_client -starttls smtp -connect mxa-00376703.gslb.gpphosted.com:25 -servername mxa-00376703.gslb.gpphosted.com 2>/dev/null | openssl x509 -noout -subject -dates

Check MTA-STS DNS record (RFC 8461)

dig +short _mta-sts.cisa.gov TXT

Fetch MTA-STS policy file (RFC 8461)

curl -sL https://mta-sts.cisa.gov/.well-known/mta-sts.txt

Check TLS-RPT record (RFC 8460)

dig +short _smtp._tls.cisa.gov TXT

Brand & Trust

Check BIMI record (BIMI Draft)

dig +short default._bimi.cisa.gov TXT

Check CAA records (certificate authority authorization) (RFC 8659)

dig +noall +answer cisa.gov CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460)

dig +noall +answer cisa.gov HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344)

dig +noall +answer cisa.gov CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083)

curl -sL 'https://rdap.org/domain/cisa.gov' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (mxa-00376703.gslb.gpphosted.com) (RFC 3207)

openssl s_client -starttls smtp -connect mxa-00376703.gslb.gpphosted.com:25 -servername mxa-00376703.gslb.gpphosted.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962)

curl -s 'https://crt.sh/?q=%25.cisa.gov&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://cisa.gov/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://cisa.gov/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://cisa.gov/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 23.64.138.233 (Team Cymru)

dig +short 233.138.64.23.origin.asn.cymru.com TXT

Engineer's DNS Intelligence Report

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed and validated, cryptographic chain of trust verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 75 subdomains discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

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

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

Rules of Engagement

What You May Do

What You May Not Do

Engineer's DNS Intelligence Report

Intelligence Dissemination

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed and validated, cryptographic chain of trust verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 75 subdomains discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

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

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

RFC Reference