Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 24 Feb 2026, 04:36 UTC
Duration 45.3s
Version v26.25.39
Integrity 27ebd7426f5b9bc59ff17e3547308636003f0e010a2609696108fe922e745ab7d34e919f3be3c13749e3b332517341ec9dc790b04ddeb1d7226fcf8e884e0d08
Subject Domain
google.com

Engineer's DNS Intelligence Report

google.com
24 Feb 2026, 04:36 UTC · 45.3s ·v26.25.39 · SHA-3-512: 27eb✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Google Workspace 6 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
6 protocols configured, 2 not configured, 1 unavailable on provider Why we go beyond letter grades
1 monitoring
Intelligence Currency
Data Currency: Adequate 74/100
ICuAE Details
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Degraded
DNS data shows some aging or gaps — consider re-scanning for critical decisions
Suggested Scanner Configuration High Confidence
Based on 20 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 30.3s, 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
Configured
Monitoring
DKIM signing inferred from provider — could not directly verify selector
Configured
SPF, DMARC (reject), DKIM (inferred via Google Workspace), MTA-STS, TLS-RPT, CAA
Not Configured
BIMI, DNSSEC
Unavailable on Provider
DANE
Priority Actions Achievable posture: Secure
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 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.
TypeTXT
Hostdefault._bimi.google.com (BIMI default record)
Valuev=BIMI1; l=https://google.com/brand/logo.svg
RFC 9495
Registrar (RDAP) OBSERVED LIVE
MarkMonitor Inc.
Where domain was purchased
Email Service Provider INFERRED
Google Workspace
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 1/10 lookups

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

v=spf1 include:_spf.google.com ~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 uses ~all + DMARC reject: the strongest compatible security stance, aligned with CISA and RFC guidance.

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; rua=mailto:mailauth-reports@google.com
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? Provider-managed
Provider Verified

DKIM not discoverable via common selectors (large providers use rotating selectors)

Google Workspace detected as primary mail platform — DKIM signing is managed by the provider. The primary provider may use custom selectors not discoverable through standard checks.
Know your DKIM selector? Re-scan with a custom selector to verify.
RFC 6376 (Provider-Managed) — DKIM signing managed by the detected mail provider per RFC 6376.
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? No — TLS enforced
Success ENFORCE Policy Verified

MTA-STS enforced - TLS required for 3 mail server(s)

v=STSv1; id=20210803T010101;
Policy Details:
  • Mode: enforce
  • Max Age: 1 days (86400 seconds)
  • MX Patterns: smtp.google.com, aspmx.l.google.com, *.aspmx.l.google.com

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

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? Yes — reports configured
Success

TLS-RPT configured - receiving TLS delivery reports

v=TLSRPTv1;rua=mailto:sts-reports@google.com
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)
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 (already configured)

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 uses MTA-STS — the best available option for Google Workspace. Since Google Workspace does not support inbound DANE, MTA-STS is the strongest transport security this domain can deploy. MTA-STS enforces TLS via HTTPS-based policy, protecting against downgrade attacks (RFC 8461).

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) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only pki.goog can issue certificates

Authorized CAs: pki.goog
0 issue "pki.goog"
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? Yes RFC 9116

security.txt properly configured

Contact

https://g.co/vulnz
mailto:security@google.com

Expires

unparseable Valid

Encryption

https://services.google.com/corporate/publickey.txt

Policy

https://g.co/vrp
Hiring Acknowledgments
Source: https://google.com/.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)
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 ns1.google.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: ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com

Mail Transport Security Beta Is mail transport encrypted and verified? Yes MTA-STS enforces TLS for all inbound mail delivery

Transport encryption enforced via DNS policy (3 signal(s))

Policy Assessment Primary
  • MTA-STS policy in enforce mode requires encrypted transport (RFC 8461)
  • TLS-RPT configured — domain monitors TLS delivery failures (RFC 8460)
  • Google Workspace enforces TLS 1.2+ with valid certificates on all inbound/outbound mail
Telemetry
TLS-RPT configured — domain receives reports about TLS delivery failures from sending mail servers (RFC 8460)
Reporting to: mailto:sts-reports@google.com
Live Probe Supplementary
Skipped — Remote probe failed (connection failed — probe may be offline) and local port 25 is blocked. Transport security is assessed via DNS policy records 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 10 IP address(es)

ASNNameCountry
AS15169 Google LLC US
IPv4 Mappings:
142.250.125.101 → AS15169 (142.250.125.0/24)
142.250.125.139 → AS15169 (142.250.125.0/24)
142.250.125.113 → AS15169 (142.250.125.0/24)
142.250.125.138 → AS15169 (142.250.125.0/24)
142.250.125.100 → AS15169 (142.250.125.0/24)
142.250.125.102 → AS15169 (142.250.125.0/24)
IPv6 Mappings:
2607:f8b0:4001:c2f::71 → AS15169 (2607:f8b0:4001::/48)
2607:f8b0:4001:c2f::65 → AS15169 (2607:f8b0:4001::/48)
2607:f8b0:4001:c2f::66 → AS15169 (2607:f8b0:4001::/48)
2607:f8b0:4001:c2f::64 → AS15169 (2607:f8b0:4001::/48)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 6 services

6 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
DocuSign docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e
Microsoft 365 MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB
Google Workspace google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0
Apple apple-domain-verification=30afIBcvSuDV2PLX
Cisco Umbrella cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd3...
Facebook / Meta facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
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 not configured - DNS responses are unsigned

Enterprise DNS Context: DNSSEC is the only standardized, DNS-verifiable mechanism that cryptographically authenticates responses between authoritative servers and resolvers (RFC 4033 §2, RFC 4035). Without it, DNS responses are technically vulnerable to in-transit tampering. Enterprise operators may employ compensating controls (anycast, DDoS mitigation, private peering, TSIG) — however, these do not provide DNS-layer data authentication to third-party resolvers and are not verifiable via DNS alone.
Visibility: DNS-only — network-layer compensating controls cannot be observed or verified through DNS queries. This assessment reflects what is provable from the DNS evidence available.

NS Delegation Verified

4 nameserver(s) configured

Nameservers: ns1.google.com ns2.google.com ns3.google.com ns4.google.com
Managed DNS
All 4 nameservers hosted by Google Cloud DNS. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s): Google Cloud DNS
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (4 differences found)
Resolver Differences:
A: Quad9 returned different results: [142.250.72.206]
A: Cloudflare returned different results: [142.250.189.142]
A: DNS4EU returned different results: [142.251.39.206]
TXT: OpenDNS returned different results: [MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB apple-domain-verification=30afIBcvSuDV2PLX docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e docusign=1b0a6754-49b1-4db5-8540-d2c12664b289 facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95 onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0 v=spf1 include:_spf.google.com ~all]
This may indicate DNS propagation in progress or geo-based DNS routing.

HTTPS / SVCB Records RFC 9460 Success HTTPS HTTP/3

HTTPS records found, HTTP/3 supported

PriorityTargetALPNECHRaw
1 . h2, h3 No google.com. 18397 IN HTTPS 1 . alpn="h2,h3"
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

142.250.125.101
142.250.125.139
142.250.125.113
142.250.125.138
142.250.125.100
142.250.125.102
Where the domain points for web traffic

AAAAIPv6 Address

2607:f8b0:4001:c2f::71
2607:f8b0:4001:c2f::65
2607:f8b0:4001:c2f::66
2607:f8b0:4001:c2f::64
IPv6 ready

MXMail Servers

10 smtp.google.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

_caldavs._tcp: 5 0 443 calendar.google.com.
_carddavs._tcp: 5 0 443 google.com.
SIP, XMPP, or other service endpoints
Web: Reachable (6 IPv4, 4 IPv6) Mail: 1 server Services: 2 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? Showing 200 of 378 discovered
How did we find these?
300 unique certificates 110 current 268 expired 42 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Wildcard certificate detected: *.google.com Expired 4 certs 1 CA:
Explicit SANs found on wildcard certificates: These hostnames were specifically listed alongside the wildcard — revealing infrastructure the operator intentionally secured.
*.aistudio.google.com *.appengine.google.com *.cloud.google.com *.crowdsource.google.com *.datacompute.google.com *.gemini.cloud.google.com *.url.google.com android.clients.google.com
DNS probing and CNAME chain traversal were used to discover additional subdomains below.
Certificate Authority Diversity (1 CA observed across CT log history)
Certificate Authority Certs First Issued Last Issued Status
300 2025-12-01 2025-12-02 Active
Showing 200 of 378 discovered subdomains, prioritized by security relevance. All 110 current subdomains are included, plus the most relevant historical entries. Export Full Recon (CSV)
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
account.google.com DNS Current www3.l.google.com 4 2025-12-02 —
accounts.google.com CT Log Current — 3 2025-12-02T12:34:11Z
admin.google.com DNS Current — 4 2025-12-02 —
alerts.google.com DNS Current www3.l.google.com 4 2025-12-02 —
alt1.gmail-smtp-in.l.google.com CT Log Current — 4 2025-12-02T12:26:02Z
alt3.aspmx.l.google.com CT Log Current — 4 2025-12-02T12:26:02Z
analytics.google.com DNS Current — 4 2025-12-02 —
ap.google.com DNS Current www2.l.google.com 4 2025-12-02 —
api.google.com DNS Current api.l.google.com 4 2025-12-02 —
appengine.google.com CT Log Current www3.l.google.com 4 2025-12-02T12:20:39Z
apps.google.com DNS Current www3.l.google.com 4 2025-12-02 —
archive.google.com DNS Current — 4 2025-12-02 —
area120.google.com CT Log Current — 4 2025-12-02T12:21:52Z
arvr.google.com CT Log Current www3.l.google.com 4 2025-12-02T12:21:30Z
asia-east1.mtls.cloud-run-qual.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
asia.google.com DNS Current — 4 2025-12-02 —
billing.google.com DNS Current — 4 2025-12-02 —
blog.google.com DNS Current www.blogger.com 4 2025-12-02 —
calendar.google.com CT Log Current — 4 2025-12-02T12:33:43Z
campaigns.google.com DNS Current — 4 2025-12-02 —
careers.google.com DNS Current — 4 2025-12-02 —
catalog.google.com DNS Current books.google.com 4 2025-12-02 —
chat.google.com DNS Current — 4 2025-12-02 —
cloud.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
console.eu.cloud.google.com CT Log Current — 8 2025-12-02T12:20:42Z
corp.google.com DNS Current — 4 2025-12-02 —
d.google.com DNS Current www3.l.google.com 4 2025-12-02 —
datafusion-dev.cloud.google.com CT Log Current www3.l.google.com 4 2025-12-02T12:21:30Z
datafusion-staging.cloud.google.com CT Log Current www3.l.google.com 4 2025-12-02T12:21:30Z
digiyaar.pay.google.com CT Log Current google-pci.l.google.com 3 2025-12-02T12:34:23Z
directory.google.com DNS Current www3.l.google.com 4 2025-12-02 —
doc.google.com DNS Current writely.l.google.com 4 2025-12-02 —
download.google.com DNS Current www2.l.google.com 4 2025-12-02 —
downloads.google.com DNS Current www2.l.google.com 4 2025-12-02 —
earthengine.google.com CT Log Current www3.l.google.com 4 2025-12-02T12:21:30Z
education.google.com DNS Current — 4 2025-12-02 —
email.google.com DNS Current gmail.google.com 4 2025-12-02 —
events.google.com DNS Current — 4 2025-12-02 —
feeds.google.com DNS Current uploads.google.com 4 2025-12-02 —
files.google.com DNS Current www3.l.google.com 4 2025-12-02 —
finance.google.com DNS Current www3.l.google.com 4 2025-12-02 —
forms.google.com DNS Current — 4 2025-12-02 —
gmail-smtp-in.l.google.com CT Log Current — 4 2025-12-02T12:26:02Z
gw1.google.com DNS Current gw.l.google.com 4 2025-12-02 —
gw2.google.com DNS Current gw.l.google.com 4 2025-12-02 —
health.google.com DNS Current — 4 2025-12-02 —
help.google.com DNS Current www3.l.google.com 4 2025-12-02 —
id.google.com DNS Current — 4 2025-12-02 —
image.google.com DNS Current images.google.com 4 2025-12-02 —
images.google.com DNS Current images.l.google.com 4 2025-12-02 —
investor.google.com DNS Current www3.l.google.com 4 2025-12-02 —
investors.google.com DNS Current www3.l.google.com 4 2025-12-02 —
jobs.google.com DNS Current www3.l.google.com 4 2025-12-02 —
labs.google.com DNS Current www3.l.google.com 4 2025-12-02 —
landing.pay.google.com CT Log Current google-pci.l.google.com 3 2025-12-02T12:34:23Z
ldap.google.com CT Log Current — 4 2025-12-02T12:34:11Z
learning.google.com DNS Current — 4 2025-12-02 —
lh3-de.photos4.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
lookerstudio.eu.cloud.google.com CT Log Current — 4 2025-12-02T12:20:42Z
lz.r.prom-qa.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
mail.google.com CT Log Current — 8 2025-12-02T12:25:55Z
manifest.lh3-dc.photos2.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
map.google.com DNS Current maps.google.com 4 2025-12-02 —
mapmaker.google.com CT Log Current www3.l.google.com 4 2025-12-02T12:21:30Z
maps.google.com DNS Current — 4 2025-12-02 —
mobile.google.com DNS Current mobile.l.google.com 4 2025-12-02 —
myaccount.google.com DNS Current — 4 2025-12-02 —
notifications.google.com DNS Current plus.l.google.com 4 2025-12-02 —
npgm14.mtv.corp.google.com CT Log Current — 1 2025-12-01T17:14:38Z
ns.google.com DNS Current — 4 2025-12-02 —
ns1.google.com DNS Current — 4 2025-12-02 —
ns2.google.com DNS Current — 4 2025-12-02 —
ns3.google.com DNS Current — 4 2025-12-02 —
ns4.google.com DNS Current — 4 2025-12-02 —
onetoday-dev.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
partners.google.com DNS Current www3.l.google.com 4 2025-12-02 —
ping.feedburner.google.com CT Log Current www4.l.google.com 4 2025-12-02T12:21:30Z
pki.google.com DNS Current www3.l.google.com 4 2025-12-02 —
policies.google.com DNS Current — 4 2025-12-02 —
print.google.com DNS Current www2.l.google.com 4 2025-12-02 —
privacy.google.com DNS Current — 4 2025-12-02 —
products.google.com DNS Current www3.l.google.com 4 2025-12-02 —
profile.google.com DNS Current — 4 2025-12-02 —
prom-nightly-gp.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
r.ext.google.com CT Log Current — 2 2025-12-01T10:40:49Z
rcs-adamantium-staging-us.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
realtime.google.com DNS Current www3.l.google.com 4 2025-12-02 —
registry.google.com DNS Current — 4 2025-12-02 —
rtcsupport.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
search.google.com DNS Current www3.l.google.com 4 2025-12-02 —
services.google.com DNS Current www3.l.google.com 4 2025-12-02 —
shop.google.com DNS Current — 4 2025-12-02 —
store.google.com DNS Current — 4 2025-12-02 —
supl.google.com CT Log Current — 2 2025-12-02T12:34:25Z
survey.google.com DNS Current — 4 2025-12-02 —
surveys.google.com DNS Current — 4 2025-12-02 —
test-bigquery.eu.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
tools.google.com DNS Current tools.l.google.com 4 2025-12-02 —
uc.r.prom-qa.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
upload.video.google.com CT Log Current sslvideo-upload.l.google.com 4 2025-12-02T12:26:59Z
uploads.google.com DNS Current feedsftp.l.google.com 4 2025-12-02 —
us-east1.mtls.cloud-run-qual.sandbox.google.com CT Log Current — 4 2025-12-02T12:26:58Z
vault.google.com DNS Current www4.l.google.com 4 2025-12-02 —
video.google.com DNS Current video.l.google.com 4 2025-12-02 —
videos.google.com DNS Current video.google.com 4 2025-12-02 —
vincuna.bld.corp.google.com CT Log Current — 1 2025-12-01T14:45:50Z
vpn.google.com DNS Current — 4 2025-12-02 —
waymo-capital.corp.google.com CT Log Current — 1 2025-12-01T17:14:38Z
web.google.com DNS Current www3.l.google.com 4 2025-12-02 —
work.google.com DNS Current www3.l.google.com 4 2025-12-02 —
gsuite.google.com CT Log Expired — 1 2025-12-02T12:36:12Z
workspace.google.com CT Log Expired — 1 2025-12-02T12:36:12Z
time.google.com CT Log Expired — 3 2025-12-02T12:34:35Z
webapps.google.com CT Log Expired — 3 2025-12-02T12:34:32Z
dns.google.com CT Log Expired — 8 2025-12-02T12:34:25Z
tokenized.play.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
merchantstories.pay.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
p.sandbox.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
bpui0.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
payments.google.com CT Log Expired — 6 2025-12-02T12:34:23Z
wallet.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
tez.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
pay.google.com CT Log Expired — 3 2025-12-02T12:34:23Z
webapp.google.com CT Log Expired — 4 2025-12-02T12:34:20Z
jibe.google.com CT Log Expired — 4 2025-12-02T12:34:14Z
apis.google.com CT Log Expired — 8 2025-12-02T12:34:13Z
checkout.google.com CT Log Expired — 4 2025-12-02T12:34:11Z
inbox.google.com CT Log Expired — 4 2025-12-02T12:34:10Z
m.google.com CT Log Expired — 3 2025-12-02T12:34:10Z
www.google.com CT Log Expired — 3 2025-12-02T12:34:10Z
programmablesearchengine.google.com CT Log Expired — 4 2025-12-02T12:33:46Z
startup.google.com CT Log Expired — 8 2025-12-02T12:33:45Z
chrome.google.com CT Log Expired — 4 2025-12-02T12:33:43Z
lti.gemini.usercontent.google.com CT Log Expired — 4 2025-12-02T12:33:31Z
recorder.google.com CT Log Expired — 4 2025-12-02T12:33:31Z
fife.google.com CT Log Expired — 8 2025-12-02T12:33:31Z
lti.meet.usercontent.google.com CT Log Expired — 4 2025-12-02T12:33:31Z
usercontent.sandbox.google.com CT Log Expired — 4 2025-12-02T12:33:31Z
usercontent.google.com CT Log Expired — 8 2025-12-02T12:33:31Z
lti.workspace.usercontent.google.com CT Log Expired — 4 2025-12-02T12:33:31Z
lti.drive.usercontent.google.com CT Log Expired — 4 2025-12-02T12:33:31Z
fife.usercontent.google.com CT Log Expired — 8 2025-12-02T12:33:31Z
news.google.com CT Log Expired — 8 2025-12-02T12:33:31Z
classroom.google.com CT Log Expired — 8 2025-12-02T12:33:31Z
ecc-test.sandbox.google.com CT Log Expired — 4 2025-12-02T12:33:28Z
telus-voice-staging.sandbox.google.com CT Log Expired — 4 2025-12-02T12:33:11Z
telus.voice.google.com CT Log Expired — 4 2025-12-02T12:33:11Z
acs.voice.google.com CT Log Expired — 4 2025-12-02T12:33:02Z
acs-staging.voice.google.com CT Log Expired — 4 2025-12-02T12:32:58Z
acs-dev.voice.google.com CT Log Expired — 4 2025-12-02T12:32:58Z
acs-autopush.voice.google.com CT Log Expired — 4 2025-12-02T12:32:49Z
ext.google.com CT Log Expired — 8 2025-12-02T12:32:48Z
wifi.google.com CT Log Expired — 4 2025-12-02T12:32:12Z
pa.clients6.google.com CT Log Expired — 2 2025-12-02T12:29:14Z
clients6.google.com CT Log Expired — 2 2025-12-02T12:29:14Z
photos.google.com CT Log Expired — 4 2025-12-02T12:26:59Z
upload.google.com CT Log Expired — 8 2025-12-02T12:26:59Z
clients.google.com CT Log Expired — 8 2025-12-02T12:26:59Z
us-east4.mtls.cloud-run-qual.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
prom-gfe-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
a.cloud-run-qual.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
lh3-dc.photos2.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
mail-dispatcher.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
rcs-adamantium-autopush.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
a.serverless-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
sandbox.google.com CT Log Expired — 15 2025-12-02T12:26:58Z
prom-test.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
prom-nightly.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
mail.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
prom-gfe-nightly.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
mail-ls3.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
mail-ls0.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
lh3-da.photos0.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
lh3-dg.photos6.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
lh3-dz.photos-autopush.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
pa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
lh3-db.photos1.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
cf.prom-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
us-east1.cloud-run-qual.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
manifest.lh3-dz.photos-autopush.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
ew.r.prom-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
tz.r.prom-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
meet-quality.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
docs.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
mail-qa3.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
googlesource-testing.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
hybrid.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
uk.r.prom-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
app.ddl-autopush.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
manifest.lh3-dg.photos6.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
us-central1.mtls.cloud-run-qual.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
app.ddl-daily0.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
gplex-qa.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
us-east4.cloud-run-qual.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
drive.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
a.serverless-nightly.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
sites.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
script.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
us-central1.cloud-run-qual.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
mail-qa0.sandbox.google.com CT Log Expired — 4 2025-12-02T12:26:58Z
Showing 200 of 378 discovered subdomains, curated by security relevance. Multiple cooperative discovery methods — including CT logs (RFC 6962), DNS probing, and CNAME chain traversal — feed into a unified view. Well-known service names (mail, vpn, api, sso, admin, etc.), DNS-resolving hosts, and subdomains with the most certificate activity are prioritized. 268 expired-certificate-only subdomains included where relevant. Export Full Recon (CSV)
Δ Changes Detected: A AAAA 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 Propagating 6 / 6 records
142.250.125.101
74.125.126.102
142.250.125.139
74.125.126.139
142.250.125.113
74.125.126.100
142.250.125.138
74.125.126.101
142.250.125.100
74.125.126.113
142.250.125.102
74.125.126.138
AAAA Propagating 4 / 4 records
2607:f8b0:4001:c2f::71
2607:f8b0:4001:c1d::66
2607:f8b0:4001:c2f::65
2607:f8b0:4001:c1d::65
2607:f8b0:4001:c2f::66
2607:f8b0:4001:c1d::71
2607:f8b0:4001:c2f::64
2607:f8b0:4001:c1d::8b
CAA RFC 8659 §4 Synchronized 1 / 1 records
0 issue "pki.goog"
0 issue "pki.goog"
DMARC _dmarc.google.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
MTA-STS _mta-sts.google.com RFC 8461 §3 Synchronized 1 / 1 records
v=STSv1; id=20210803T010101;
v=STSv1; id=20210803T010101;
MX RFC 5321 Synchronized 1 / 1 records
10 smtp.google.com.
10 smtp.google.com.
NS RFC 1035 Synchronized 4 / 4 records
ns4.google.com.
ns1.google.com.
ns1.google.com.
ns3.google.com.
ns2.google.com.
ns2.google.com.
ns3.google.com.
ns4.google.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns1.google.com. dns-admin.google.com. 873609184 900 900 1800 60
ns1.google.com. dns-admin.google.com. 873609184 900 900 1800 60
TLS-RPT _smtp._tls.google.com RFC 8460 §3 Synchronized 1 / 1 records
v=TLSRPTv1;rua=mailto:sts-reports@google.com
v=TLSRPTv1;rua=mailto:sts-reports@google.com
TXT RFC 7208 §4 Propagating 12 / 7 records
docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e
google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ
MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB
apple-domain-verification=30afIBcvSuDV2PLX
google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0
MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB
globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=
facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
apple-domain-verification=30afIBcvSuDV2PLX
onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0
cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b
v=spf1 include:_spf.google.com ~all
onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0
google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0
google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o
—
google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ
—
v=spf1 include:_spf.google.com ~all
—
facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
—
docusign=1b0a6754-49b1-4db5-8540-d2c12664b289
—
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.

Subdomain curation: 378 subdomains were discovered — the most security-relevant are displayed, prioritized by: well-known service names (mail, vpn, api, sso, admin, etc.), DNS-resolving hosts, and subdomains with the most certificate activity. CNAME chain resolution and provider identification run on the curated set for accuracy. The complete list is available via CSV export.

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.

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

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 142.250.125.101 (Team Cymru) 
dig +short 101.125.250.142.origin.asn.cymru.com TXT
ASN lookup for 142.250.125.139 (Team Cymru) 
dig +short 139.125.250.142.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 4849 runs
DKIM
Verified 4668 runs
DMARC
Verified 4833 runs
DANE/TLSA
Verified 4652 runs
DNSSEC
Verified 4830 runs
BIMI
Verified 4667 runs
MTA-STS
Verified 4670 runs
TLS-RPT
Verified 4672 runs
CAA
Verified 4664 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 google.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer google.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer google.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer google.com NS
Query TXT records (RFC 1035) 
dig +noall +answer google.com TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer google.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer google.com CDS

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 142.250.125.101 (Team Cymru) 
dig +short 101.125.250.142.origin.asn.cymru.com TXT
ASN lookup for 142.250.125.139 (Team Cymru) 
dig +short 139.125.250.142.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

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