Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 22 Feb 2026, 14:33 UTC
Duration 56.6s
Version v26.24.05
Integrity 4f6a9e2f121eb3a5fb93bb70e2d13e7eb0533522b41a20e5bf3de2fc69b76fe2677658fe2cd38adae0e9f8d7d550b556795b925cd2bf85302e0712380114730f
Subject Domain
kali.org

Engineer's DNS Intelligence Report

kali.org
22 Feb 2026, 14:33 UTC · 56.6s ·v26.24.05 · SHA-3-512: 4f6a✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Google Workspace 2 SaaS Services
DNS Security & Trust Posture
Risk Level: Medium Risk
4 protocols configured, 4 not configured, 1 unavailable on provider Domain appears to be in deliberate DMARC monitoring phase with aggregate reporting enabled Why we go beyond letter grades
1 recommendation 1 monitoring
Intelligence Currency
Data Currency: Good 82/100
ICuAE Details
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Adequate
DNS data is mostly current with minor gaps — good intelligence currency
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 46.9s, 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
Unsigned
Certificate Control
Configured
Recommended
Move DMARC policy from 'none' to 'quarantine' or 'reject'
Monitoring
DMARC record has configuration warnings — review recommended
Configured
SPF, DMARC (with warnings), DKIM, CAA
Not Configured
MTA-STS, TLS-RPT, BIMI, DNSSEC
Unavailable on Provider
DANE
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.kali.org (DMARC policy record)
Valuev=DMARC1; p=quarantine; rua=mailto:dmarc-reports@kali.org
RFC 7489 §6.3
Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035
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.
TypeTXT
Host_smtp._tls.kali.org (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@kali.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.kali.org (MTA-STS policy record)
Valuev=STSv1; id=kali.org
RFC 8461
Registrar (RDAP) OBSERVED LIVE
Gandi SAS
Where domain was purchased
Email Service Provider INFERRED
Google Workspace
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 2/10 lookups

SPF valid with industry-standard soft fail (~all), 2/10 lookups

v=spf1 a ip4:208.88.127.98 ip4:52.44.83.41 include:_spf.google.com include:sendgrid.net ~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; rua=mailto:dc94040db6314366b5d8c16fb40a986b@dmarc-reports.cloudflare.net,mailto:cu3rgqiu@ag.dmarcian.com; ruf=mailto:cu3rgqiu@fr.dmarcian.com; fo=1;
Policy p=none provides no protection - spoofed emails reach inboxes
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. 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. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
Advanced cryptographic posture detected. Domain appears to be in deliberate DMARC monitoring phase with aggregate reporting enabled
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)

google._domainkey Google Workspace
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApYGplMfn/stW5ijXPQQKWIXn9qvYm0B3NrWq8v3oOMEYH3DWwm16CKYu6+xr6JRNYfomvwKZB5Ro/F6ej1I0BOApgcSLkdFOJZzAtH1TZBi9blWCknG2ficM6/rt+5jEqz1HaZKicppXneviuyGascrvaqWagCEytRMQjXZsClo68v1tdAAJfX5qWnOAUmz4qLH4aClV94o6LTnmo052WEWV25375RrtU2608Nt5Gh0JkaupE2evCiYwtILDaa5o3/1cieaSaQRz9ZXzEoaUTuGSLn0trGGINx8VNQNk3OLg3YOUd8WUYfm0LNJuaUaMJSBFZk5IdTx4U4/+zDvAKwIDAQAB
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 3 external reporting domains properly authorized

External Domain Authorization Auth Record
ag.dmarcian.com Authorized v=DMARC1;
fr.dmarcian.com Authorized v=DMARC1;
dmarc-reports.cloudflare.net 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 — Google Workspace does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Google Workspace

Google Workspace supports DANE for outbound mail verification but does not publish TLSA records for its MX hosts.

Recommended alternative: MTA-STS

Note: Google Workspace does validate DANE/TLSA when sending mail to DANE-enabled recipients (outbound DANE).

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 Google Workspace 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? 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 IODEF

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only ssl.com, DigiCert, Sectigo, godaddy.com, Let's Encrypt, cansignhttpexchanges=yes can issue certificates (wildcard issuance: cansignhttpexchanges=yes, ssl.com, DigiCert, Sectigo, Let's Encrypt per RFC 8659 §4.3)

Authorized CAs: ssl.com DigiCert Sectigo godaddy.com Let's Encrypt cansignhttpexchanges=yes
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issue "comodoca.com"
0 iodef "mailto:webmaster@offsec.com"
0 issue "godaddy.com"
0 issuewild "ssl.com"
0 issue "letsencrypt.org"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issuewild "comodoca.com"
0 issue "ssl.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issuewild "letsencrypt.org"
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? Partial RFC 9116

security.txt found with issues

Contact

security at offsec dot com

Expires

Missing (required by RFC 9116 §2.5.5)

Policy

https://www.offsec.com/blog/bug-bounty-program-insights/
https://www.offsec.com/bug-bounty-program/
en Canonical URL Hiring Acknowledgments
Source: https://kali.org/.well-known/security.txt
Missing required Expires field (RFC 9116 §2.5.5)
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.
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.

DNS Server Security Hardened

No DNS server misconfigurations found on nina.ns.cloudflare.com — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Zone transfer denied (correct configuration)
Open Recursion Disabled Recursion disabled (correct configuration)
Nameserver Identity Hidden No nameserver identity information disclosed
Cache Snooping Protected Cache snooping not possible (correct configuration)

Tested nameservers: nina.ns.cloudflare.com, nash.ns.cloudflare.com

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

Transport security inferred from 1 signal(s) — no enforcement policy active

Policy Assessment Primary
  • Google Workspace enforces TLS 1.2+ with valid certificates on all inbound/outbound mail
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — SMTP port 25 not reachable from this host — outbound port 25 is likely blocked by the hosting provider. Transport security is assessed via DNS policy records, which is the standards-aligned primary method per NIST SP 800-177 Rev. 1.
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASNNameCountry
AS13335 Cloudflare, Inc. US
IPv4 Mappings:
104.18.4.159 → AS13335 (104.18.0.0/20)
104.18.5.159 → AS13335 (104.18.0.0/20)
IPv6 Mappings:
2606:4700::6812:59f → AS13335 (2606:4700::/44)
2606:4700::6812:49f → AS13335 (2606:4700::/44)

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
Microsoft 365 MS=2F24AAB1EA3933DA8A05BF4B28C70033E0001820
Google Workspace google-site-verification=QO0m_WIzc81XaujadDfsFymI53IwsX4sCt-Tin9ugoI
Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC partially configured - DNSKEY exists but DS record missing at registrar

DNSKEY exists but DS record not published at registrar. Add DS record to complete chain of trust.

NS Delegation Verified

2 nameserver(s) configured

Nameservers: nash.ns.cloudflare.com nina.ns.cloudflare.com
Managed DNS
All 2 nameservers hosted by Cloudflare. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s): Cloudflare
Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records

HTTPS / SVCB Records RFC 9460 Success HTTPS ECH

HTTPS records found, ECH (Encrypted Client Hello) enabled

PriorityTargetALPNECHRaw
1 . h2 Yes kali.org. 300 IN HTTPS 1 . alpn="h2" ipv4hint="104.18.4.159,104.18.5.159" ech="AEX+DQBBlQAgACD/tJtq5TsNIaXETR7Kybv00SPlxAgyvtLAE2sPI3HBWgAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA=" ipv6hint="2606:4700::6812:49f,2606:4700::6812:59f"

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

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

Key TagAlgorithmDigest TypeDigest
2371 ECDSAP256SHA256 2
CDNSKEY Records:
FlagsProtocolAlgorithmPublic Key
257 3 ECDSAP256SHA256
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

104.18.4.159
104.18.5.159
Where the domain points for web traffic

AAAAIPv6 Address

2606:4700::6812:59f
2606:4700::6812:49f
IPv6 ready

MXMail Servers

5 aspmx.l.google.com.
25 alt4.aspmx.l.google.com.
10 alt1.aspmx.l.google.com.
15 alt2.aspmx.l.google.com.
20 alt3.aspmx.l.google.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (2 IPv4, 2 IPv6) Mail: 5 servers Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 53 subdomains discovered
How did we find these?
CT logs unavailable 53 current 0 expired 13 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)
aphrodite.kali.org CT Log Current — 4 2026-02-04T07:44:43 Let's Encrypt
archive-4.kali.org CT Log Current hecate.kali.org 4 2026-01-30T09:57:30 Let's Encrypt
archive.kali.org CT Log Current rhea.kali.org 2 2026-01-03T22:16:50 Let's Encrypt
arm.kali.org CT Log Current kalilinux.gitlab.io 4 2026-01-30T13:14:04 Let's Encrypt
artemis.kali.org CT Log Current — 2 2026-01-19T04:17:04 Let's Encrypt
artifacts.kali.org CT Log Current — 4 2026-02-18T06:59:08 Let's Encrypt
autopkgtest.kali.org CT Log Current — 2 2025-12-28T08:40:21 Let's Encrypt
bittorrent.kali.org CT Log Current artemis.kali.org 2 2026-01-19T11:23:14 Let's Encrypt
bugs.kali.org CT Log Current — 4 2026-02-03T08:34:19 Let's Encrypt
buildd-amd64.kali.org CT Log Current dionysus.kali.org 2 2026-01-16T16:17:11 Let's Encrypt
buildd-arm64.kali.org CT Log Current gaia.kali.org 4 2026-02-12T09:32:10 Let's Encrypt
buildd-armhf.kali.org CT Log Current crius.kali.org 2 2026-01-16T01:14:50 Let's Encrypt
buildd-i386.kali.org CT Log Current dionysus.kali.org 4 2026-02-10T15:52:40 Let's Encrypt
coeus.kali.org CT Log Current — 2 2026-01-11T16:59:11 Let's Encrypt
crius.kali.org CT Log Current — 2 2026-01-16T01:15:00 Let's Encrypt
demeter.kali.org CT Log Current — 2 2026-01-18T06:02:16 Let's Encrypt
dionysus.kali.org CT Log Current — 2 2026-01-16T16:17:21 Let's Encrypt
docs.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
downloads.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
dzaa.kali.org CT Log Current — 4 2026-02-01T08:42:06 Let's Encrypt
epimetheus.kali.org CT Log Current — 8 2026-02-09T18:08:53 Let's Encrypt
erato.kali.org CT Log Current — 4 2026-02-12T10:14:04 Let's Encrypt
forums.kali.org CT Log Current — 2 2026-01-18T02:51:48 Let's Encrypt
gaia.kali.org CT Log Current — 4 2026-02-12T09:32:16 Let's Encrypt
git.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
hecate.kali.org CT Log Current — 4 2026-01-30T09:57:42 Let's Encrypt
image-amd64.kali.org CT Log Current demeter.kali.org 2 2026-01-18T06:02:24 Let's Encrypt
image-arm64.kali.org CT Log Current coeus.kali.org 2 2026-01-11T16:59:23 Let's Encrypt
image.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
images.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
jenkins.kali.org CT Log Current — 4 2026-01-29T06:03:04 Let's Encrypt
melpomene.kali.org CT Log Current — 2 2025-12-28T08:40:31 Let's Encrypt
minos.kali.org CT Log Current — 4 2026-02-18T06:59:36 Let's Encrypt
mirror-traces.kali.org CT Log Current — 4 2026-01-27T17:42:18 Let's Encrypt
mnemosyne.kali.org CT Log Current — 4 2026-01-29T06:03:13 Let's Encrypt
nethunter.kali.org CT Log Current kalilinux.gitlab.io 2 2025-12-24T10:52:37 Let's Encrypt
nike.kali.org CT Log Current — 4 2026-01-27T17:42:27 Let's Encrypt
oceanus.kali.org CT Log Current — 2 2026-01-10T13:58:50 Let's Encrypt
old.kali.org CT Log Current terpsichore.kali.org 2 2026-01-04T06:50:32 Let's Encrypt
phobos.kali.org CT Log Current — 2 2026-01-10T17:19:31 Let's Encrypt
pkg.kali.org CT Log Current — 2 2026-01-10T13:59:01 Let's Encrypt
poseidon.kali.org CT Log Current — 4 2026-02-01T16:58:40 Let's Encrypt
prometheus.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
qa.kali.org CT Log Current — 2 2026-01-10T17:19:45 Let's Encrypt
repo.kali.org CT Log Current urania.kali.org 4 2026-02-13T03:26:57 Let's Encrypt
rhea.kali.org CT Log Current — 2 2026-01-03T22:16:58 Let's Encrypt
status.kali.org CT Log Current — 4 2026-01-27T17:42:35 Let's Encrypt
terpsichore.kali.org CT Log Current — 2 2026-01-04T06:50:47 Let's Encrypt
tethys.kali.org CT Log Current — 8 2026-02-04T07:12:21 Let's Encrypt
tools.kali.org DNS Current — 8 2025-12-05 Let's Encrypt, Google Trust Services, Sectigo Limited
triton.kali.org CT Log Current — 2 2026-01-15T22:43:59 Let's Encrypt
urania.kali.org CT Log Current — 4 2026-02-13T03:27:06 Let's Encrypt
www.kali.org CT Log Current — 4 2026-01-30T16:42:40 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 2 / 2 records
104.18.4.159
104.18.4.159
104.18.5.159
104.18.5.159
AAAA Synchronized 2 / 2 records
2606:4700::6812:59f
2606:4700::6812:49f
2606:4700::6812:49f
2606:4700::6812:59f
CAA RFC 8659 §4 12 / 0 records
0 issuewild "ssl.com"
—
0 issue "pki.goog; cansignhttpexchanges=yes"
—
0 issuewild "pki.goog; cansignhttpexchanges=yes"
—
0 issue "letsencrypt.org"
—
0 issue "comodoca.com"
—
0 issue "digicert.com; cansignhttpexchanges=yes"
—
0 issue "godaddy.com"
—
0 iodef "mailto:webmaster@offsec.com"
—
0 issuewild "comodoca.com"
—
0 issuewild "letsencrypt.org"
—
0 issue "ssl.com"
—
0 issuewild "digicert.com; cansignhttpexchanges=yes"
—
DMARC _dmarc.kali.org RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=none; rua=mailto:dc94040db6314366b5d8c16fb40a986b@dmarc-reports.cloudflare.net,mailto:cu3rgqiu@ag.dmarcian.com; ruf=mailto:cu3rgqiu@fr.dmarcian.com; fo=1;
v=DMARC1; p=none; rua=mailto:dc94040db6314366b5d8c16fb40a986b@dmarc-reports.cloudflare.net,mailto:cu3rgqiu@ag.dmarcian.com; ruf=mailto:cu3rgqiu@fr.dmarcian.com; fo=1;
MX RFC 5321 Synchronized 5 / 5 records
5 aspmx.l.google.com.
10 alt1.aspmx.l.google.com.
25 alt4.aspmx.l.google.com.
15 alt2.aspmx.l.google.com.
10 alt1.aspmx.l.google.com.
20 alt3.aspmx.l.google.com.
15 alt2.aspmx.l.google.com.
25 alt4.aspmx.l.google.com.
20 alt3.aspmx.l.google.com.
5 aspmx.l.google.com.
NS RFC 1035 Synchronized 2 / 2 records
nash.ns.cloudflare.com.
nash.ns.cloudflare.com.
nina.ns.cloudflare.com.
nina.ns.cloudflare.com.
SOA RFC 1035 Synchronized 1 / 1 records
nash.ns.cloudflare.com. dns.cloudflare.com. 2396996609 10000 2400 604800 1800
nash.ns.cloudflare.com. dns.cloudflare.com. 2396996609 10000 2400 604800 1800
TXT RFC 7208 §4 Synchronized 4 / 4 records
MS=2F24AAB1EA3933DA8A05BF4B28C70033E0001820
MS=2F24AAB1EA3933DA8A05BF4B28C70033E0001820
v=spf1 a ip4:208.88.127.98 ip4:52.44.83.41 include:_spf.google.com include:sendgrid.net ~all
google-site-verification=QO0m_WIzc81XaujadDfsFymI53IwsX4sCt-Tin9ugoI
google-site-verification=QO0m_WIzc81XaujadDfsFymI53IwsX4sCt-Tin9ugoI
mjb3j7d41a5qd3i4qo8j8d9q7g
mjb3j7d41a5qd3i4qo8j8d9q7g
v=spf1 a ip4:208.88.127.98 ip4:52.44.83.41 include:_spf.google.com include:sendgrid.net ~all
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.

4f6a9e2f121eb3a5fb93bb70e2d13e7eb0533522b41a20e5bf3de2fc69b76fe2677658fe2cd38adae0e9f8d7d550b556795b925cd2bf85302e0712380114730f
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 22 Feb 2026, 14:33 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-kali.org.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-kali.org.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-kali.org.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-kali.org.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/3674/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 kali.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 kali.org A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer kali.org AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer kali.org MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer kali.org NS
Query TXT records RFC 1035 
dig +noall +answer kali.org TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 104.18.4.159 (Team Cymru) 
dig +short 159.4.18.104.origin.asn.cymru.com TXT
ASN lookup for 104.18.5.159 (Team Cymru) 
dig +short 159.5.18.104.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 4851 runs
DKIM
Verified 4670 runs
DMARC
Verified 4835 runs
DANE/TLSA
Verified 4654 runs
DNSSEC
Verified 4832 runs
BIMI
Verified 4669 runs
MTA-STS
Verified 4672 runs
TLS-RPT
Verified 4674 runs
CAA
Verified 4666 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 kali.org A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer kali.org AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer kali.org MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer kali.org NS
Query TXT records (RFC 1035) 
dig +noall +answer kali.org TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 104.18.4.159 (Team Cymru) 
dig +short 159.4.18.104.origin.asn.cymru.com TXT
ASN lookup for 104.18.5.159 (Team Cymru) 
dig +short 159.5.18.104.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

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