DNS Tool

Engineer's DNS Intelligence Report

Generated 8 Mar 2026, 14:06 UTC
Duration 27.7s
Version v26.35.20
Integrity 25e60ff57f87901d02229fb088f9dc11789ad145206f38be26c722e49cc65bcc12ceba20d29ae65375eaa24a72107157451096debb943a51db529edbc6121b65

TLP:AMBER

Limited disclosure — recipients may share within their organization only

Subject Domain

google.com

Engineer's DNS Intelligence Report

google.com

8 Mar 2026, 14:06 UTC · 27.7s ·v26.35.20 · SHA-3-512: 25e6✱✱✱✱ 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

Analysis Confidence (ICD 203)

MODERATE 66/100

Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.

Accuracy 63% Currency 68/100 Maturity verified

Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers

Intelligence Currency

Data Currency: Adequate 68/100

ICuAE Details

Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Good TTL Relevance Stale

DNS data shows some aging or gaps — consider re-scanning for critical decisions

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type	Observed TTL	Typical TTL	Severity	Context
CAA	`18722s`	`1 hour (3600s)`	high	CAA TTL is above typical — observed 18722s, typical value is 1 hour (3600s). Long TTLs reduce DNS query volume but slow propagation when records change. Consider 3600 seconds for a balance of performance and flexibility per NIST SP 800-53 SI-18 relevance guidance.
NS	`6 hours (21600s)`	`1 day (86400s)`	medium	NS TTL is below typical — observed 6 hours (21600s), typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
MX	`200s`	`1 hour (3600s)`	high	MX TTL is below typical — observed 200s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
SOA	`25s`	`1 hour (3600s)`	high	SOA TTL is below typical — observed 25s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT	`270s`	`1 hour (3600s)`	high	TXT TTL is below typical — observed 270s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
AAAA	`5 minutes (300s)`	`1 hour (3600s)`	high	AAAA TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
A	`261s`	`1 hour (3600s)`	high	A TTL is below typical — observed 261s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.

Tune TTL for google.com

Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) DNS provider detected: Google Cloud DNS — provider-specific RFC compliance notes are shown inline above where applicable.

Primary NS ns1.google.com

Serial 879543655

Admin dns-admin.google.com

Provider Google Cloud DNS

Timer	Value	RFC 1912 Range
Refresh	`900s`	1,200–43,200s (20 min – 12 hrs)
Retry	`900s`	Fraction of Refresh
Expire	`1800s`	1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)	`60s`	300–86,400s (5 min – 1 day)

Expire: SOA Expire is 30 minutes (1800s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 30 minutes (1800s).

RFC 1912 §2.2

Refresh: SOA Refresh is 15 minutes (900s), below the RFC 1912 recommended minimum of 1,200 seconds.

RFC 1912 §2.2

Expire vs Refresh+Retry: If Expire is not greater than Refresh + Retry, secondary nameservers may stop serving the zone before they've had a chance to retry the primary.

RFC 1912 §2.2

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.

Field	Value
Type	`TXT`
Host	`default._bimi.google.com` (BIMI default record)
Value	`v=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 OBSERVED

Google Cloud DNS

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. The absence of ruf= is not a gap. 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)

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.

DNS Server Security Hardened

No DNS server misconfigurations found on ns3.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	Test inconclusive
Open Recursion	Disabled	Test inconclusive
Nameserver Identity	Hidden	Test inconclusive
Cache Snooping	Protected	Test inconclusive

Tested nameservers: ns3.google.com, ns1.google.com, ns4.google.com, ns2.google.com

Delegation Consistency 5 Issues

Delegation consistency: 5 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:

In-bailiwick NS ns1.google.com has no glue records at parent — resolution may fail
In-bailiwick NS ns2.google.com has no glue records at parent — resolution may fail
In-bailiwick NS ns3.google.com has no glue records at parent — resolution may fail
In-bailiwick NS ns4.google.com has no glue records at parent — resolution may fail
Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Incomplete

Nameserver	In-Bailiwick	IPv4 Glue	IPv6 Glue	Status
`ns1.google.com`				Missing
`ns2.google.com`				Missing
`ns3.google.com`				Missing
`ns4.google.com`				Missing

NS TTL Comparison Drift

Child TTL: 345600s Drift: 0s

SOA Serial Consistency Consistent

ns1.google.com: 8.79543655e+08

ns2.google.com: 8.79543655e+08

ns3.google.com: 8.79543655e+08

ns4.google.com: 8.79543655e+08

Nameserver Fleet Matrix Healthy

Analyzed 4 nameserver(s) for google.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver	IPv4	IPv6	ASN / Operator	SOA Serial
`ns4.google.com`	216.239.38.10	2001:4860:4802:38::a	AS15169 Google LLC	879543655
`ns3.google.com`	216.239.36.10	2001:4860:4802:36::a	AS15169 Google LLC	879543655
`ns2.google.com`	216.239.34.10	2001:4860:4802:34::a	AS15169 Google LLC	879543655
`ns1.google.com`	216.239.32.10	2001:4860:4802:32::a	AS15169 Google LLC	879543655

Unique ASNs

Unique Operators

Unique /24 Prefixes

Diversity Score

Fair

1 ASN(s), 4 /24 prefix(es) — consider adding diversity

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

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

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

MX Host	STARTTLS	TLS Version	Cipher	Certificate
`smtp.google.com`		TLSv1.3	TLS_AES_128_GCM_SHA256	Valid Expires: 2026-04-27 (49 days) Issuer: Google Trust Services

Multi-Vantage Probe Results

Unanimous: TLS verified 2 probes, 1 responded

US-East (Boston) observed

All servers support TLS

France - EU skipped

9.002043063s

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)

ASN	Name	Country
`AS15169`	Google LLC	US

IPv4 Mappings:

74.125.69.100 → AS15169 (74.125.69.0/24)

74.125.69.138 → AS15169 (74.125.69.0/24)

74.125.69.113 → AS15169 (74.125.69.0/24)

74.125.69.101 → AS15169 (74.125.69.0/24)

74.125.69.139 → AS ()

74.125.69.102 → AS ()

IPv6 Mappings:

2607:f8b0:4001:c06::66 → AS ()

2607:f8b0:4001:c06::8a → AS ()

2607:f8b0:4001:c06::8b → AS ()

2607:f8b0:4001:c06::65 → AS ()

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.

Service	Verification Record
Google Workspace	`google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0`
Cisco Umbrella	`cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd3...`
Facebook / Meta	`facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95`
Apple	`apple-domain-verification=30afIBcvSuDV2PLX`
DocuSign	`docusign=1b0a6754-49b1-4db5-8540-d2c12664b289`
Microsoft 365	`MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB`

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 (3 differences found)

Resolver Differences:

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=0d477fe608074e6f9c12bca7826035cc v=spf1 include:_spf.google.com ~all]

A: Cloudflare returned different results: [142.251.32.14]

A: DNS4EU returned different results: [172.217.23.238]

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

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

AIPv4 Address

74.125.69.100

74.125.69.138

74.125.69.113

74.125.69.101

74.125.69.139

74.125.69.102

Where the domain points for web traffic

AAAAIPv6 Address

2607:f8b0:4001:c06::66

2607:f8b0:4001:c06::8a

2607:f8b0:4001:c06::8b

2607:f8b0:4001:c06::65

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? 515 subdomains discovered

How did we find these?

CT logs unavailable 514 current 1 expired 48 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)
`a.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`a.cloud-run-test.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`a.serverless-nightly.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`a.serverless-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`account.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`accounts.google.com`	CT Log	Current	—	8	2025-12-15T08:39:41Z
`acs-autopush.voice.google.com`	CT Log	Current	—	8	2025-12-15T08:39:21Z
`acs-dev.voice.google.com`	CT Log	Current	—	8	2025-12-15T08:39:15Z
`acs-staging.voice.google.com`	CT Log	Current	—	8	2025-12-15T08:39:15Z
`acs.voice.google.com`	CT Log	Current	—	8	2025-12-15T08:39:15Z
`actions.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`ad-ds-46-anycast.corp.google.com`	CT Log	Current	—	10	2025-12-18T17:46:13Z
`ad-ds-anycast.corp.google.com`	CT Log	Current	—	10	2025-12-18T17:46:13Z
`addc.corp.google.com`	CT Log	Current	—	10	2025-12-18T17:46:13Z
`admin.google.com`	DNS	Current	—	12	2025-12-15	—
`ads.google.com`	CT Log	Current	—	4	2025-12-18T19:20:14Z
`adwords.google.com`	CT Log	Current	—	4	2025-12-18T19:20:14Z
`africa-south1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:08Z
`aiplatform-notebook.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`aiplatform-training.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`aistudio.google.com`	CT Log	Current	—	28	2025-12-15T08:37:29Z
`alerts.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`alt1.aspmx.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt1.gmail-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt1.gmr-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt2.aspmx.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt2.gmail-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt2.gmr-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt3.aspmx.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt3.gmail-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt3.gmr-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt4.aspmx.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt4.gmail-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`alt4.gmr-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`an.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`analytics.google.com`	DNS	Current	—	12	2025-12-15	—
`android.clients.google.com`	CT Log	Current	—	12	2025-12-15T08:37:22Z
`android.google.com`	CT Log	Current	—	8	2025-12-15T08:42:43Z
`ap.google.com`	DNS	Current	`www2.l.google.com`	12	2025-12-15	—
`api.google.com`	DNS	Current	`api.l.google.com`	12	2025-12-15	—
`apigee.google.com`	CT Log	Current	—	17	2025-12-15T08:37:47Z
`apis.google.com`	CT Log	Current	—	16	2025-12-15T08:39:44Z
`app.ddl-autopush.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`app.ddl-daily0.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`appengine.google.com`	CT Log	Current	—	12	2025-12-15T08:37:22Z
`apps.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`archive.google.com`	DNS	Current	—	12	2025-12-15	—
`area120.google.com`	CT Log	Current	—	8	2025-12-15T08:37:58Z
`artsandculture.google.com`	CT Log	Current	—	16	2025-12-15T08:38:03Z
`arvr.google.com`	CT Log	Current	`www3.l.google.com`	15	2025-12-15T08:37:47Z
`asia-east1.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`asia-east1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:17Z
`asia-east1.mtls.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`asia-east2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:18Z
`asia-northeast1.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:18Z
`asia-northeast2.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:19Z
`asia-northeast3.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:11Z
`asia-south1.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:12Z
`asia-south2.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:14Z
`asia-southeast1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:15Z
`asia-southeast2.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:15Z
`asia-southeast3.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:16Z
`asia.apigee.google.com`	CT Log	Current	—	5	2025-12-15T08:41:14Z
`asia.google.com`	DNS	Current	—	12	2025-12-15	—
`aspmx.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`au.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`australia-southeast1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:24Z
`australia-southeast2.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:17Z
`australia.apigee.google.com`	CT Log	Current	—	5	2025-12-15T08:41:14Z
`backupdr-autopush.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`backupdr-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`backupdr-sandbox.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`backupdr-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`backupdr.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`bandwidth.voice.google.com`	CT Log	Current	—	15	2025-12-15T08:37:47Z
`baseline.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`billing.google.com`	DNS	Current	—	12	2025-12-15	—
`blog.google.com`	DNS	Current	`www.blogger.com`	12	2025-12-15	—
`bod.google.com`	CT Log	Current	—	16	2025-12-15T08:38:48Z
`bpui0.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`ca.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:31Z
`calendar.google.com`	CT Log	Current	—	8	2025-12-15T08:39:26Z
`calljoy.area120.google.com`	CT Log	Current	—	8	2025-12-15T08:37:20Z
`campaigns.google.com`	DNS	Current	—	12	2025-12-15	—
`captive.adservice.google.com`	CT Log	Current	—	6	2025-12-15T08:41:01Z
`careers.google.com`	DNS	Current	—	12	2025-12-15	—
`catalog.google.com`	DNS	Current	`books.google.com`	12	2025-12-15	—
`cbf-dc-11.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:45:52Z
`cbf-dc-11.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:45:52Z
`cbf-dc-13.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:46:13Z
`cbf-dc-13.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:46:13Z
`cbf-dc-14.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:46:33Z
`cbf-dc-14.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:46:33Z
`ccure-uat-vws-csrm-emea.corp.google.com`	CT Log	Current	—	1	2025-12-18T14:43:56Z
`cert-test.sandbox.google.com`	CT Log	Current	—	8	2025-12-15T08:38:47Z
`cf.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`ch.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`chat.google.com`	DNS	Current	—	12	2025-12-15	—
`checkout.google.com`	CT Log	Current	—	8	2025-12-15T08:39:41Z
`chrome.google.com`	CT Log	Current	—	8	2025-12-15T08:39:19Z
`classroom.google.com`	CT Log	Current	—	16	2025-12-15T08:39:26Z
`client-channel.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`clients.google.com`	CT Log	Current	—	16	2025-12-15T08:38:56Z
`clients6.google.com`	CT Log	Current	`clients.l.google.com`	2	2025-12-18T19:21:04Z
`cloud.google.com`	CT Log	Current	—	20	2025-12-15T08:37:22Z
`cloud.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`code.google.com`	CT Log	Current	—	8	2025-12-15T08:38:50Z
`colab.research.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`composer-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`composer-qa.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`composer-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`composer.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`console.au.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`console.ca.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:31Z
`console.ch.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`console.eu.cloud.google.com`	CT Log	Current	—	15	2025-12-15T08:37:25Z
`console.il.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`console.in.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:34Z
`console.it.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:34Z
`console.jp.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:35Z
`console.nest.google.com`	CT Log	Current	—	8	2025-12-15T08:37:44Z
`console.sa.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:29Z
`console.uk.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:36Z
`console.us.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:36Z
`contentpartners.maps.google.com`	CT Log	Current	—	14	2025-12-15T08:41:22Z
`conversational-agents.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:03Z
`corp.google.com`	DNS	Current	—	12	2025-12-15	—
`crowdsource.google.com`	CT Log	Current	—	12	2025-12-15T08:37:22Z
`d.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`datacompute.google.com`	CT Log	Current	—	12	2025-12-15T08:37:22Z
`datafusion-api-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`datafusion-api-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`datafusion-api.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`datafusion-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`datafusion-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`datafusion.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`datalab.cloud.google.com`	CT Log	Current	`www3.l.google.com`	7	2025-12-15T08:37:47Z
`dataplex-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`dataplex-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`dataplex.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`dataproc-image-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`dataproc-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`dataproc-test.cloud.google.com`	CT Log	Current	`www3.l.google.com`	7	2025-12-15T08:37:47Z
`dataproc.cloud.google.com`	CT Log	Current	`www3.l.google.com`	7	2025-12-15T08:37:47Z
`datasetsearch.research.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`de-cs-fra50-1-xx-corpa-nvr01.corp.google.com`	CT Log	Current	—	2	2025-12-10T17:29:18Z
`de-cs-fra50-1-xx-corpa-nvr02.corp.google.com`	CT Log	Current	—	2	2025-12-10T17:29:18Z
`deepmind.google.com`	CT Log	Current	—	16	2025-12-15T08:37:32Z
`deliverynavigator.cloud.google.com`	CT Log	Current	—	12	2025-12-15T08:41:15Z
`devconsole-testers.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`developer.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`developers.google.com`	CT Log	Current	—	15	2025-12-15T08:37:47Z
`devsite-sni.developers.google.com`	CT Log	Current	—	8	2025-12-15T08:37:32Z
`dg-meta.video.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`dg.video.google.com`	CT Log	Current	—	8	2025-12-15T08:38:44Z
`digiyaar.pay.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`directory.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`discover.google.com`	CT Log	Current	—	28	2025-12-15T08:37:47Z
`dns.google.com`	CT Log	Current	—	16	2025-12-15T08:39:42Z
`doc.google.com`	DNS	Current	`writely.l.google.com`	12	2025-12-15	—
`docs.google.com`	CT Log	Current	—	16	2025-12-15T08:38:51Z
`docs.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`download.google.com`	DNS	Current	`www2.l.google.com`	12	2025-12-15	—
`downloads.google.com`	DNS	Current	`www2.l.google.com`	12	2025-12-15	—
`drive.google.com`	CT Log	Current	—	16	2025-12-15T08:38:51Z
`drive.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`earthengine.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`ecc-test.sandbox.google.com`	CT Log	Current	—	8	2025-12-15T08:39:17Z
`education.google.com`	DNS	Current	—	12	2025-12-15	—
`ehr-search.health.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`email.google.com`	DNS	Current	`gmail.google.com`	12	2025-12-15	—
`eu.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`europe-central2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:17Z
`europe-north1.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:42:17Z
`europe-north2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:18Z
`europe-southwest1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:26Z
`europe-west1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:26Z
`europe-west10.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:23Z
`europe-west12.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:24Z
`europe-west2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:27Z
`europe-west3.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:21Z
`europe-west4.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:21Z
`europe-west6.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:21Z
`europe-west8.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:22Z
`europe-west9.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:22Z
`europe.apigee.google.com`	CT Log	Current	—	5	2025-12-15T08:41:14Z
`events.google.com`	DNS	Current	—	12	2025-12-15	—
`ew.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`ewoq.google.com`	CT Log	Current	—	15	2025-12-15T08:37:47Z
`ext.google.com`	CT Log	Current	—	16	2025-12-15T08:39:13Z
`febc9c00708987d.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T14:43:56Z
`feeds.google.com`	DNS	Current	`uploads.google.com`	12	2025-12-15	—
`fiber.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`fife.google.com`	CT Log	Current	—	16	2025-12-15T08:39:26Z
`fife.usercontent.google.com`	CT Log	Current	—	16	2025-12-15T08:39:26Z
`files.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`finance.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`firebase.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`forms.google.com`	DNS	Current	—	12	2025-12-15	—
`fra-dc-11.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:46:52Z
`fra-dc-11.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:46:52Z
`fra-dc-12.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:47:12Z
`fra-dc-12.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:47:12Z
`frame.ads.google.com`	CT Log	Current	—	8	2025-12-18T19:20:14Z
`gemini.cloud.google.com`	CT Log	Current	—	12	2025-12-15T08:37:22Z
`geminidataanalytics.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:10Z
`generativeai.google.com`	CT Log	Current	—	8	2025-12-15T08:37:32Z
`get.duo.google.com`	CT Log	Current	—	8	2025-12-15T08:37:44Z
`ggp.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`gmail-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`gmr-mx.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`gmr-smtp-in.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`googlesource-testing.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`googlesource.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`gplex-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`grow.google.com`	CT Log	Current	—	16	2025-12-15T08:38:27Z
`gsuite.google.com`	CT Log	Current	—	8	2025-12-15T08:40:50Z
`guidebooks.google.com`	CT Log	Current	—	12	2025-12-15T08:41:15Z
`gw.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`gw1.google.com`	DNS	Current	`gw.l.google.com`	12	2025-12-15	—
`gw2.google.com`	DNS	Current	`gw.l.google.com`	12	2025-12-15	—
`hangouts.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`hangouts.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`health.google.com`	DNS	Current	—	12	2025-12-15	—
`healthcare.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`help.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`home.google.com`	CT Log	Current	—	16	2025-12-15T08:37:24Z
`hot-dc-11.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:47:32Z
`hot-dc-11.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:47:32Z
`hot-dc-13.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:47:52Z
`hot-dc-13.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:47:52Z
`hot-dc-14.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:48:12Z
`hot-dc-14.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:48:12Z
`hybrid.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`id-edg-cgk02-7-ac-corpa-nvr01.corp.google.com`	CT Log	Current	—	1	2025-12-11T05:35:41Z
`id.google.com`	DNS	Current	—	12	2025-12-15	—
`il.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`image.google.com`	DNS	Current	`images.google.com`	12	2025-12-15	—
`images.google.com`	DNS	Current	`images.l.google.com`	12	2025-12-15	—
`in.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:34Z
`inbox.google.com`	CT Log	Current	—	8	2025-12-15T08:39:41Z
`investor.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`investors.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`it.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:34Z
`jibe.google.com`	CT Log	Current	—	8	2025-12-15T08:39:51Z
`jobs.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`jp-cs-nrt41-3-xx-corpa-nvr02.corp.google.com`	CT Log	Current	—	1	2025-12-10T19:04:35Z
`jp.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:35Z
`labs.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`landing.pay.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`ldap.google.com`	CT Log	Current	—	8	2025-12-15T08:39:41Z
`learn.mapsplatform.google.com`	CT Log	Current	—	16	2025-12-15T08:37:32Z
`learning.google.com`	DNS	Current	—	12	2025-12-15	—
`lh3-da.photos0.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-db.photos1.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-dc.photos2.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-dd.photos3.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-de.photos4.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-df.photos5.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-dg.photos6.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-dy.photos-staging.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lh3-dz.photos-autopush.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`lookerstudio.africa-south1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:08Z
`lookerstudio.asia-east1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:17Z
`lookerstudio.asia-east2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:18Z
`lookerstudio.asia-northeast1.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:18Z
`lookerstudio.asia-northeast2.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:19Z
`lookerstudio.asia-northeast3.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:11Z
`lookerstudio.asia-south1.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:12Z
`lookerstudio.asia-south2.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:14Z
`lookerstudio.asia-southeast1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:15Z
`lookerstudio.asia-southeast2.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:15Z
`lookerstudio.asia-southeast3.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:16Z
`lookerstudio.australia-southeast1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:24Z
`lookerstudio.australia-southeast2.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:17Z
`lookerstudio.eu.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:25Z
`lookerstudio.europe-central2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:17Z
`lookerstudio.europe-north1.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:42:17Z
`lookerstudio.europe-north2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:18Z
`lookerstudio.europe-southwest1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:26Z
`lookerstudio.europe-west1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:26Z
`lookerstudio.europe-west10.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:23Z
`lookerstudio.europe-west12.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:24Z
`lookerstudio.europe-west2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:27Z
`lookerstudio.europe-west3.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:21Z
`lookerstudio.europe-west4.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:21Z
`lookerstudio.europe-west6.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:21Z
`lookerstudio.europe-west8.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:22Z
`lookerstudio.europe-west9.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:22Z
`lookerstudio.me-central1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:24Z
`lookerstudio.me-central2.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:25Z
`lookerstudio.me-west1.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:26Z
`lookerstudio.northamerica-northeast1.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:26Z
`lookerstudio.northamerica-northeast2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:34Z
`lookerstudio.northamerica-south1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:36Z
`lookerstudio.southamerica-east1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:36Z
`lookerstudio.southamerica-west1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:37Z
`lookerstudio.us-central1.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:37Z
`lookerstudio.us-east1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:38Z
`lookerstudio.us-east4.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:31Z
`lookerstudio.us-east5.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:32Z
`lookerstudio.us-south1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:32Z
`lookerstudio.us-west1.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:33Z
`lookerstudio.us-west2.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:33Z
`lookerstudio.us-west3.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:33Z
`lookerstudio.us-west4.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:34Z
`lookerstudio.us-west8.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:43Z
`lookerstudio.us.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:36Z
`lti.drive.usercontent.google.com`	CT Log	Current	—	8	2025-12-15T08:39:26Z
`lti.gemini.google.com`	CT Log	Current	—	8	2025-12-15T08:38:07Z
`lti.gemini.usercontent.google.com`	CT Log	Current	—	8	2025-12-15T08:39:26Z
`lti.meet.usercontent.google.com`	CT Log	Current	—	8	2025-12-15T08:39:26Z
`lti.workspace.usercontent.google.com`	CT Log	Current	—	8	2025-12-15T08:39:26Z
`lz.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`m.google.com`	CT Log	Current	—	8	2025-12-15T08:39:41Z
`machinelearningtools-autopush.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`machinelearningtools-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`machinelearningtools-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`machinelearningtools.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`mail-dispatcher.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-gemini.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-griffin.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-ls0.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-ls1.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-ls2.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-ls3.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-ls4.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-qa0.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-qa1.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-qa2.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-qa3.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-qa4.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`mail-settings.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`mail.google.com`	CT Log	Current	—	16	2025-12-15T08:38:51Z
`mail.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-da.photos0.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-db.photos1.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-dc.photos2.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-dd.photos3.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-de.photos4.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-df.photos5.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-dg.photos6.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-dy.photos-staging.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3-dz.photos-autopush.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`manifest.lh3.photos.google.com`	CT Log	Current	`photos-ugc.l.googleusercontent.com`	8	2025-12-15T08:38:43Z
`map.google.com`	DNS	Current	`maps.google.com`	12	2025-12-15	—
`mapmaker.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`maps.google.com`	DNS	Current	—	12	2025-12-15	—
`me-central1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:24Z
`me-central2.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:25Z
`me-west1.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:26Z
`meet-quality.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`meet.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`meet.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`merchantstories.pay.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`microhost.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`misc-sni.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`misc.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`mlcc.google.com`	CT Log	Current	—	16	2025-12-15T08:37:38Z
`mobile.google.com`	DNS	Current	`mobile.l.google.com`	12	2025-12-15	—
`mtls.clients6.google.com`	CT Log	Current	—	8	2025-12-15T08:40:52Z
`mtls.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:40:52Z
`mtls.hybrid.sandbox.google.com`	CT Log	Current	—	20	2025-12-15T08:38:48Z
`mtls.pa.clients6.google.com`	CT Log	Current	—	8	2025-12-15T08:40:52Z
`mtls.pa.sandbox.google.com`	CT Log	Current	—	20	2025-12-15T08:38:48Z
`mtls.sandbox.google.com`	CT Log	Current	—	15	2025-12-15T08:40:52Z
`mx.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`myaccount.google.com`	DNS	Current	—	12	2025-12-15	—
`nestrenew.google.com`	CT Log	Current	—	16	2025-12-15T08:37:38Z
`news.google.com`	CT Log	Current	—	16	2025-12-15T08:39:20Z
`northamerica-northeast1.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:26Z
`northamerica-northeast2.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:34Z
`northamerica-south1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:36Z
`northamerica.apigee.google.com`	CT Log	Current	—	12	2025-12-15T08:37:47Z
`notebooks.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`notifications.google.com`	DNS	Current	`plus.l.google.com`	12	2025-12-15	—
`ns.google.com`	DNS	Current	—	12	2025-12-15	—
`ns1.google.com`	DNS	Current	—	12	2025-12-15	—
`ns2.google.com`	DNS	Current	—	12	2025-12-15	—
`ns3.google.com`	DNS	Current	—	12	2025-12-15	—
`ns4.google.com`	DNS	Current	—	12	2025-12-15	—
`onetoday-dev.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`p.sandbox.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`pa.clients6.google.com`	CT Log	Current	—	2	2025-12-18T19:21:04Z
`pa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`partners.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`partnertest.fi.google.com`	CT Log	Current	—	6	2025-12-15T08:41:11Z
`pay.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`payments.google.com`	CT Log	Current	—	16	2025-12-15T08:39:56Z
`photos.google.com`	CT Log	Current	—	8	2025-12-15T08:38:56Z
`ping.feedburner.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`pipelines.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`pki.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`plus.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`policies.google.com`	DNS	Current	—	12	2025-12-15	—
`print.google.com`	DNS	Current	`www2.l.google.com`	12	2025-12-15	—
`privacy.google.com`	DNS	Current	—	12	2025-12-15	—
`privacysandbox.google.com`	CT Log	Current	—	40	2025-12-15T08:37:32Z
`products.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`profile.google.com`	DNS	Current	—	12	2025-12-15	—
`programmablesearchengine.google.com`	CT Log	Current	—	8	2025-12-15T08:39:28Z
`prom-gfe-nightly.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`prom-gfe-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`prom-nightly-gp.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`prom-nightly.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`prom-qa-gs.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`prom-test.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`radius-machineauth-anycast.corp.google.com`	CT Log	Current	—	1	2025-12-15T04:58:41Z
`rcs-adamantium-autopush.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`rcs-adamantium-staging-loadtest.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`rcs-adamantium-staging-us.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`realtime.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`recorder.google.com`	CT Log	Current	—	8	2025-12-15T08:39:19Z
`region1.analytics.google.com`	CT Log	Current	—	8	2025-12-15T08:37:30Z
`registry.google.com`	DNS	Current	—	12	2025-12-15	—
`rewards.google.com`	CT Log	Current	—	30	2025-12-15T08:37:47Z
`rtcsupport.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`s.svc-1.google.com`	CT Log	Current	—	14	2025-12-15T08:37:47Z
`sa.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:29Z
`sandbox.google.com`	CT Log	Current	—	26	2025-12-15T08:38:48Z
`sandbox.mtls.google.com`	CT Log	Current	—	8	2025-12-15T08:40:52Z
`script.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`search.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`services.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`shop.google.com`	DNS	Current	—	12	2025-12-15	—
`sites.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`sites.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`skills.google.com`	CT Log	Current	—	16	2025-12-15T08:37:42Z
`smtp-proxy.corp.google.com`	CT Log	Current	—	1	2025-12-15T04:58:41Z
`smtp.google.com`	CT Log	Current	—	8	2025-12-15T08:38:46Z
`solutions.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:41:15Z
`southamerica-east1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:36Z
`southamerica-west1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:37Z
`southamerica.apigee.google.com`	CT Log	Current	—	5	2025-12-15T08:41:14Z
`speech.google.com`	CT Log	Current	—	14	2025-12-15T08:37:47Z
`startup.google.com`	CT Log	Current	—	16	2025-12-15T08:39:27Z
`status.play.google.com`	CT Log	Current	—	6	2025-12-15T08:41:26Z
`status.search.google.com`	CT Log	Current	—	6	2025-12-15T08:41:25Z
`store.google.com`	DNS	Current	—	12	2025-12-15	—
`streetviewstudio.maps.google.com`	CT Log	Current	—	12	2025-12-15T08:41:21Z
`supl.google.com`	CT Log	Current	—	8	2025-12-15T08:39:43Z
`support.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`survey.google.com`	DNS	Current	—	12	2025-12-15	—
`surveys.google.com`	DNS	Current	—	12	2025-12-15	—
`talkgadget.google.com`	CT Log	Current	—	8	2025-12-15T08:38:51Z
`telus-voice-staging.sandbox.google.com`	CT Log	Current	—	8	2025-12-15T08:39:16Z
`telus.voice.google.com`	CT Log	Current	—	8	2025-12-15T08:39:22Z
`tensorboard-autopush.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`tensorboard-dev.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`tensorboard-staging.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`tensorboard-test.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`tensorboard.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:37:47Z
`tensorflow.google.com`	CT Log	Current	—	16	2025-12-15T08:37:37Z
`test-bigquery.eu.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`test-bigquery.us.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`testmx.sandbox.google.com`	CT Log	Current	—	8	2025-12-15T08:38:47Z
`tez.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`time.google.com`	CT Log	Current	—	8	2025-12-15T08:39:53Z
`tokenized.play.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`tools.google.com`	DNS	Current	`tools.l.google.com`	12	2025-12-15	—
`twd-dc-11.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:48:32Z
`twd-dc-11.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:48:32Z
`twd-dc-12.ad.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:48:52Z
`twd-dc-12.corp.google.com`	CT Log	Current	—	1	2025-12-18T17:48:52Z
`tx.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`tz.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`uc.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`ue.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`uk.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:36Z
`uk.r.prom-qa.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`upload.google.com`	CT Log	Current	—	16	2025-12-15T08:38:56Z
`upload.video.google.com`	CT Log	Current	—	8	2025-12-15T08:38:56Z
`uploads.google.com`	DNS	Current	`feedsftp.l.google.com`	12	2025-12-15	—
`url.google.com`	CT Log	Current	—	12	2025-12-15T08:37:22Z
`us-central1.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-central1.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:37Z
`us-central1.mtls.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-central2.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-central2.mtls.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-east1.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-east1.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:38Z
`us-east1.mtls.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-east4.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-east4.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:31Z
`us-east4.mtls.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-east5.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:32Z
`us-south1.cloud.google.com`	CT Log	Current	—	7	2025-12-15T08:42:32Z
`us-west1.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-west1.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:33Z
`us-west1.mtls.cloud-run-qual.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`us-west2.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:33Z
`us-west3.cloud.google.com`	CT Log	Current	—	6	2025-12-15T08:42:33Z
`us-west4.cloud.google.com`	CT Log	Current	—	5	2025-12-15T08:42:34Z
`us-west8.cloud.google.com`	CT Log	Current	—	4	2025-12-15T08:42:43Z
`us.cloud.google.com`	CT Log	Current	—	8	2025-12-15T08:37:36Z
`usercontent.google.com`	CT Log	Current	—	16	2025-12-15T08:39:26Z
`usercontent.sandbox.google.com`	CT Log	Current	—	8	2025-12-15T08:39:26Z
`vault.google.com`	DNS	Current	`www4.l.google.com`	12	2025-12-15	—
`video.google.com`	DNS	Current	`video.l.google.com`	12	2025-12-15	—
`videos.google.com`	DNS	Current	`video.google.com`	12	2025-12-15	—
`voice-search-dev.sandbox.google.com`	CT Log	Current	—	5	2025-12-15T08:38:48Z
`vp.video.l.google.com`	CT Log	Current	—	8	2025-12-15T08:38:44Z
`vpn.google.com`	DNS	Current	—	12	2025-12-15	—
`wallet.google.com`	CT Log	Current	—	8	2025-12-15T08:39:56Z
`web.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`webapp.google.com`	CT Log	Current	—	8	2025-12-15T08:39:45Z
`webapps.google.com`	CT Log	Current	—	8	2025-12-15T08:39:45Z
`wifi.google.com`	CT Log	Current	—	8	2025-12-15T08:39:16Z
`work.google.com`	DNS	Current	`www3.l.google.com`	12	2025-12-15	—
`workspace.google.com`	CT Log	Current	—	8	2025-12-15T08:40:50Z
`www.ads.google.com`	CT Log	Current	—	4	2025-12-18T19:20:14Z
`www.adwords.google.com`	CT Log	Current	—	4	2025-12-18T19:20:14Z
`www.google.com`	CT Log	Current	—	8	2025-12-15T08:39:47Z
`us-edg-iad23-1-ac-corpa-nvr01.corp.google.com`	CT Log	Expired	—	1	2025-12-08T16:31:30Z

Export 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

74.125.69.100

142.251.183.138

74.125.69.138

142.251.183.139

74.125.69.113

142.251.183.100

74.125.69.101

142.251.183.102

74.125.69.139

142.251.183.101

74.125.69.102

142.251.183.113

AAAA Propagating 4 / 4 records

2607:f8b0:4001:c06::66

2607:f8b0:4001:c64::8a

2607:f8b0:4001:c06::8a

2607:f8b0:4001:c64::64

2607:f8b0:4001:c06::8b

2607:f8b0:4001:c64::65

2607:f8b0:4001:c06::65

2607:f8b0:4001:c64::71

CAA RFC 8659 §4 Synchronized 1 / 1 records

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

MTA-STS _mta-sts.google.com RFC 8461 §3 Synchronized 1 / 1 records

v=STSv1; id=20210803T010101;

MX RFC 5321 Synchronized 1 / 1 records

10 smtp.google.com.

NS RFC 1035 Synchronized 4 / 4 records

ns3.google.com.

ns4.google.com.

ns2.google.com.

ns1.google.com.

ns4.google.com.

ns2.google.com.

ns1.google.com.

ns3.google.com.

SOA RFC 1035 Synchronized 1 / 1 records

ns1.google.com. dns-admin.google.com. 879543655 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

TXT RFC 7208 §4 Propagating 13 / 6 records

google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0

MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB

globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=

v=spf1 include:_spf.google.com ~all

google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ

cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b

docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e

onetrust-domain-verification=0d477fe608074e6f9c12bca7826035cc

onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0

facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95

google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o

apple-domain-verification=30afIBcvSuDV2PLX

—

docusign=1b0a6754-49b1-4db5-8540-d2c12664b289

—

v=spf1 include:_spf.google.com ~all

—

google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o

—

MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB

—

onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0

—

docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e

—

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.

25e60ff57f87901d02229fb088f9dc11789ad145206f38be26c722e49cc65bcc12ceba20d29ae65375eaa24a72107157451096debb943a51db529edbc6121b65

Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 8 Mar 2026, 14:06 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/6591/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 74.125.69.100 (Team Cymru)

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

ASN lookup for 74.125.69.138 (Team Cymru)

dig +short 138.69.125.74.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 74.125.69.100 (Team Cymru)

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

ASN lookup for 74.125.69.138 (Team Cymru)

dig +short 138.69.125.74.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? via MTA-STS (CA)

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

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

DNS Server Security Hardened

Delegation Consistency 5 Issues

Nameserver Fleet Matrix Healthy

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

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? Possible DNSSEC is not deployed, DNS responses are not cryptographically 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? 515 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? via MTA-STS (CA)

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

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

DNS Server Security Hardened

Delegation Consistency 5 Issues

Nameserver Fleet Matrix Healthy

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

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? Possible DNSSEC is not deployed, DNS responses are not cryptographically 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? 515 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