Engineer's DNS Intelligence Report
TLP:AMBER
Limited disclosure — recipients may share within their organization only
Engineer's DNS Intelligence Report
google.com
DNS Security & Trust Posture
Risk Level:
Low Risk
6 protocols configured, 2 not configured, 1 unavailable on provider
Why we go beyond letter grades
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 62%
Currency 70/100
Maturity consistent
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent
TTL Compliance Excellent
Completeness Degraded
Source Credibility Excellent
TTL Relevance Stale
ICuAE Details
Enterprise Traffic Engineering Detected
DNS-based Global Server Load Balancing (GSLB)
This domain uses short TTLs across 4 record types (A record at 46s), consistent with DNS-based traffic management (GSLB). Enterprises operating large anycast networks intentionally use short TTLs to enable rapid failover, geographic steering, and load distribution. This is a deliberate infrastructure choice, not a misconfiguration. RFC 1035 §3.2.1 permits any TTL value the zone administrator selects. The findings below reflect deviation from typical values for reference, not necessarily actionable recommendations for this class of infrastructure.
The following DNS record TTLs deviate from typical values. For domains using DNS-based traffic management, short TTLs are expected and intentional.
| Record Type | Observed TTL | Typical TTL | Severity | Context |
|---|---|---|---|---|
| MX | 299s |
1 hour (3600s) |
high | MX TTL is below typical — observed 299s, 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| CAA | 9974s |
1 hour (3600s) |
medium | CAA TTL is above typical — observed 9974s, 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-7 relevance guidance. |
| AAAA | 166s |
1 hour (3600s) |
high | AAAA TTL is below typical — observed 166s, 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| TXT | 5 minutes (300s) |
1 hour (3600s) |
high | TXT 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| SOA | 1 minute (60s) |
1 hour (3600s) |
high | SOA TTL is below typical — observed 1 minute (60s), 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| A | 46s |
1 hour (3600s) |
high | A TTL is below typical — observed 46s, 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
Big Picture Questions
- This domain runs short TTLs across multiple record types. Does it operate a global anycast network where DNS-based traffic steering justifies the query volume?
- Are the short TTLs enabling active failover, geographic routing, or load distribution — or are they leftover from a migration that was never reverted?
- Enterprise-grade DNS infrastructure (sub-5ms authoritative response times, globally distributed nameservers) absorbs short-TTL query volume. Would your authoritative DNS handle the same load?
Primary NS
ns1.google.com
Serial
905477423
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).
Refresh: SOA Refresh is 15 minutes (900s), below the RFC 1912 recommended minimum of 1,200 seconds.
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.
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.
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 |
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 Consistent
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 Consistent
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 Consistent
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 Consistent
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 Consistent
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 Consistent Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)
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).
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 Consistent Warning
Is the brand identity verified and displayed in inboxes?
No
No BIMI record found
CAA RFC 8659 §4 Consistent 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
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
View 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 ns2.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: ns2.google.com, ns3.google.com, ns4.google.com, ns1.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: 9.05477423e+08ns2.google.com: 9.05477423e+08ns3.google.com: 9.05477423e+08ns4.google.com: 9.05477423e+08Nameserver 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 | UDP | TCP | AA | SOA Serial |
|---|---|---|---|---|---|---|---|
ns4.google.com |
216.239.38.10 | 2001:4860:4802:38::a |
AS15169
Google LLC |
905477423 | |||
ns3.google.com |
216.239.36.10 | 2001:4860:4802:36::a |
AS15169
Google LLC |
905477423 | |||
ns2.google.com |
216.239.34.10 | 2001:4860:4802:34::a |
AS15169
Google LLC |
905477423 | |||
ns1.google.com |
216.239.32.10 | 2001:4860:4802:32::a |
AS15169
Google LLC |
905477423 |
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
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
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.comLive 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 0 unique ASN(s) across 10 IP address(es)
IPv4 Mappings:
173.194.193.100 → AS ()173.194.193.101 → AS ()173.194.193.102 → AS ()173.194.193.113 → AS ()173.194.193.138 → AS ()173.194.193.139 → AS ()
IPv6 Mappings:
2607:f8b0:4001:c0f::64 → AS ()2607:f8b0:4001:c0f::65 → AS ()2607:f8b0:4001:c0f::66 → AS ()2607:f8b0:4001:c0f::8a → 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 |
|---|---|
| Microsoft 365 | MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB |
| Apple | apple-domain-verification=30afIBcvSuDV2PLX |
| Cisco Umbrella | cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd3... |
| DocuSign | docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e |
| Facebook / Meta | facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95 |
| Google Workspace | google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0 |
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 Consistent 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
(5 differences found)
Resolver Differences:
A: Quad9 returned different results: [142.250.177.238]
A: Cloudflare returned different results: [142.251.210.206]
A: OpenDNS returned different results: [74.125.202.100 74.125.202.101 74.125.202.102 74.125.202.113 74.125.202.138 74.125.202.139]
A: DNS4EU returned different results: [172.217.20.46]
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]
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
| Priority | Target | ALPN | ECH | Raw |
|---|---|---|---|---|
| 1 | . |
h2, h3 | No | google.com. 15346 IN HTTPS 1 . alpn="h2,h3" |
Traffic & Routing Where does this domain's traffic actually terminate?
AIPv4 Address
173.194.193.100
173.194.193.101
173.194.193.102
173.194.193.113
173.194.193.138
173.194.193.139
Where the domain points for web traffic
AAAAIPv6 Address
2607:f8b0:4001:c0f::64
2607:f8b0:4001:c0f::65
2607:f8b0:4001:c0f::66
2607:f8b0:4001:c0f::8a
IPv6 ready
MXMail Servers
10 smtp.google.com.
Priority + mail server for email delivery
Google Workspace
SRVServices
_carddavs._tcp: 5 0 443 google.com.
_caldavs._tcp: 5 0 443 calendar.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? 833 subdomains discovered
How did we find these?
2500 unique certificates
833 current
0 expired
43 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
Active
46 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 |
|---|---|---|---|---|
|
2500 | 2026-01-27 | 2026-02-20 | Active |
| Subdomain | Source | Status | Provider / CNAME | Certificates | First Seen | Issuer(s) |
|---|---|---|---|---|---|---|
1.google.com
|
CT Log | Current | — | — | — | — |
216-239-33-25.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-10.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-32.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-33.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-36.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-4.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-6.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-63.google.com
|
CT Log | Current | — | — | — | — |
216-239-45-8.google.com
|
CT Log | Current | — | — | — | — |
360suite.google.com
|
CT Log | Current | — | — | — | — |
66-102-14-1.google.com
|
CT Log | Current | — | — | — | — |
a.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
a.cloud-run-test.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
a.serverless-nightly.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
a.serverless-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
aa.google.com
|
CT Log | Current | — | — | — | — |
about.google.com
|
CT Log | Current | — | — | — | — |
aboutme.google.com
|
CT Log | Current | — | — | — | — |
academico.google.com
|
CT Log | Current | — | — | — | — |
accelerator.google.com
|
CT Log | Current | — | — | — | — |
account.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
accounts.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:48Z | |
acs-autopush.voice.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:24Z | |
acs-dev.voice.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:31Z | |
acs-staging.voice.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:25Z | |
acs.voice.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:31Z | |
actions.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
actionscenter.google.com
|
CT Log | Current | — | — | — | — |
activity.google.com
|
CT Log | Current | — | — | — | — |
actualities.google.com
|
CT Log | Current | — | — | — | — |
ad-ds-46-anycast.corp.google.com
|
CT Log | Current | — | 10 | 2026-02-18T17:44:13Z | |
ad-ds-anycast.corp.google.com
|
CT Log | Current | — | 10 | 2026-02-18T17:44:13Z | |
addc.corp.google.com
|
CT Log | Current | — | 10 | 2026-02-18T17:44:13Z | |
admanager.google.com
|
CT Log | Current | — | — | — | — |
admin.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
admob.google.com
|
CT Log | Current | — | — | — | — |
adplanner.google.com
|
CT Log | Current | — | — | — | — |
ads-nightly.qa.adz.google.com
|
CT Log | Current | — | — | — | — |
ads.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:56Z | |
ads1.google.com
|
CT Log | Current | — | — | — | — |
adscreativestudio.google.com
|
CT Log | Current | — | — | — | — |
adsdatahub.google.com
|
CT Log | Current | — | — | — | — |
adsense.google.com
|
CT Log | Current | — | — | — | — |
adservice.google.com
|
CT Log | Current | — | — | — | — |
adsfe-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
adsfe.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
adssettings.google.com
|
CT Log | Current |
www3.l.google.com
|
— | — | — |
adstransparency.google.com
|
CT Log | Current | — | — | — | — |
adviser.google.com
|
CT Log | Current | — | — | — | — |
advisor.google.com
|
CT Log | Current | — | — | — | — |
adwords-sandbox.google.com
|
CT Log | Current | — | — | — | — |
adwords.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:56Z | |
adx.google.com
|
CT Log | Current | — | — | — | — |
adz-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
adz.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
africa-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:58Z | |
agents.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:52Z | |
aiplatform-notebook.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
aiplatform-training.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
aistudio.google.com
|
CT Log | Current | — | 168 | 2026-02-02T08:36:38Z | |
alerts.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
alt1.aspmx.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt1.gmail-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt1.gmr-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt2.aspmx.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt2.gmail-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt2.gmr-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt3.aspmx.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt3.gmail-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt3.gmr-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt4.aspmx.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt4.gmail-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
alt4.gmr-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
an.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
analytics.google.com
|
DNS | Current |
analytics-alv.google.com
|
46 | 2026-02-02 | — |
android.clients.google.com
|
CT Log | Current | — | 46 | 2026-02-02T08:36:38Z | |
android.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:41:21Z | |
anguslab.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
ap.google.com
|
DNS | Current |
www2.l.google.com
|
46 | 2026-02-02 | — |
api.google.com
|
DNS | Current |
api.l.google.com
|
46 | 2026-02-02 | — |
apigee.google.com
|
CT Log | Current | — | 28 | 2026-02-02T08:37:13Z | |
apis.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
apis.google.com
|
CT Log | Current | — | 18 | 2026-02-02T08:38:51Z | |
app.ddl-autopush.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
app.ddl-daily0.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
appengine.google.com
|
CT Log | Current | — | 46 | 2026-02-02T08:36:38Z | |
apps.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
archive.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
area120.google.com
|
CT Log | Current | — | 36 | 2026-02-02T08:37:07Z | |
artsandculture.google.com
|
CT Log | Current | — | 60 | 2026-02-02T08:37:10Z | |
arvr.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:37:13Z | |
asia-east1.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
asia-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:59Z | |
asia-east1.mtls.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
asia-east2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
asia-northeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:59Z | |
asia-northeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:00Z | |
asia-northeast3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:07Z | |
asia-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:01Z | |
asia-south2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
asia-southeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
asia-southeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
asia-southeast3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:03Z | |
asia.apigee.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:13Z | |
asia.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
aspmx.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
au.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:40Z | |
australia-southeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:10Z | |
australia-southeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:04Z | |
australia.apigee.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:13Z | |
auth.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
b05651c67f6953f.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
b067f70f20ac31e.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
backupdr-autopush.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
backupdr-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
backupdr-sandbox.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
backupdr-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
backupdr.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
bandwidth.voice.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:37:13Z | |
baseline.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
bigstore-test.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
bigstore.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
billing.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
blog.google.com
|
DNS | Current |
www.blogger.com
|
46 | 2026-02-02 | — |
bod.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:37:59Z | |
borgmon.evenflow-test.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
borgmon.evenflow.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
bpui0.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
business.corp.google.com
|
CT Log | Current | — | 8 | 2026-02-18T07:34:04Z | |
c.chat.google.com
|
CT Log | Current | — | 4 | 2026-02-17T14:30:54Z | |
c.docs.google.com
|
CT Log | Current | — | 4 | 2026-02-17T14:30:54Z | |
c.drive.google.com
|
CT Log | Current | — | 4 | 2026-02-17T14:30:54Z | |
c.mail.google.com
|
CT Log | Current | — | 4 | 2026-02-17T14:30:54Z | |
c.pack.google.com
|
CT Log | Current | — | 4 | 2026-02-17T14:30:54Z | |
c.play.google.com
|
CT Log | Current | — | 4 | 2026-02-17T14:30:54Z | |
c007b1873622ef2.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
ca-service-gecc.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
ca.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:47Z | |
calendar.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:28Z | |
calljoy.area120.google.com
|
CT Log | Current | — | 66 | 2026-02-02T08:36:35Z | |
campaigns.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
captive.adservice.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:01Z | |
careers.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
catalog.google.com
|
DNS | Current |
books.google.com
|
46 | 2026-02-02 | — |
cbf-dc-11.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:44:13Z | |
cbf-dc-11.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:44:13Z | |
cbf-dc-13.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:44:33Z | |
cbf-dc-13.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:44:33Z | |
cbf-dc-14.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:44:52Z | |
cbf-dc-14.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:44:52Z | |
cbf-nls-3.cbf.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:30:18Z | |
cbf-wsus-1.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:00Z | |
cbf-wsus.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:00Z | |
ccure-csrm-dev1-mas-app.corp.google.com
|
CT Log | Current | — | 1 | 2026-01-30T17:36:29Z | |
ccure-csrm-prod-mas-app.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
ccure-prod-mas.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
cert-test.sandbox.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:37:59Z | |
cert.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:04Z | |
cf.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
ch.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:46Z | |
chat.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
checkout.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
chrome.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:28Z | |
classroom.google.com
|
CT Log | Current | — | 24 | 2026-02-02T08:38:29Z | |
client-channel.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
client-d31feif.xup.corp.google.com
|
CT Log | Current | — | 8 | 2026-02-17T14:31:05Z | |
clients.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:38:01Z | |
clients6.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:58Z | |
cloud.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
cloud.google.com
|
CT Log | Current | — | 57 | 2026-02-02T08:37:54Z | |
cloud.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
cnsviewer-static-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:05Z | |
cnsviewer-static.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:05Z | |
code.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:54Z | |
colab.research.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
composer-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
composer-qa.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
composer-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
composer.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
connect-canary.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
connect-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
connect-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
connect.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
consent.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:05Z | |
console.actions.google.com
|
CT Log | Current | — | — | — | — |
console.au.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:40Z | |
console.ca.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:47Z | |
console.ch.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:46Z | |
console.eu.cloud.google.com
|
CT Log | Current | — | 63 | 2026-02-02T08:36:48Z | |
console.il.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:42Z | |
console.in.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:43Z | |
console.it.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:49Z | |
console.jp.cloud.google.com
|
CT Log | Current | — | 50 | 2026-02-02T08:36:50Z | |
console.nest.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:52Z | |
console.sa.cloud.google.com
|
CT Log | Current | — | 50 | 2026-02-02T08:36:44Z | |
console.uk.cloud.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:50Z | |
console.us.cloud.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:44Z | |
contacts.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
contentpartners.maps.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:40:13Z | |
conversational-agents.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:58Z | |
corp-backups.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
corp-logs-proxy-canary.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
corp-logs-proxy.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
crowdsource.google.com
|
CT Log | Current | — | 46 | 2026-02-02T08:36:38Z | |
csrm-prod-mas.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
d.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
da-cbf-5.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:17:32Z | |
da-cbf-6.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:17:51Z | |
da-cbf-8.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:18:10Z | |
da-fra-5.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:18:28Z | |
da-fra-6.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:18:46Z | |
da-fra-7.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:19:05Z | |
da-hot-4.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:19:23Z | |
da-hot-5.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:19:41Z | |
da-hot-6.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:19:59Z | |
da-mtv-5.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:20:17Z | |
da-mtv-6.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:20:36Z | |
da-mtv-7.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:20:54Z | |
da-twd-5.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:21:12Z | |
da-twd-6.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:21:30Z | |
da-twd-7.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:21:48Z | |
da-twd-8.da.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-11T21:22:07Z | |
dasher-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
dasher.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
datacompute.google.com
|
CT Log | Current |
www3.l.google.com
|
46 | 2026-02-02T08:36:38Z | |
datafusion-api-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datafusion-api-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datafusion-api.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datafusion-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datafusion-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datafusion.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datalab.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataplex-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataplex-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataplex.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataproc-image-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataproc-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataproc-test.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dataproc.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datasetsearch.research.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
datastudio.africa-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:58Z | |
datastudio.asia-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:59Z | |
datastudio.asia-east2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
datastudio.asia-northeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:59Z | |
datastudio.asia-northeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:00Z | |
datastudio.asia-northeast3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:07Z | |
datastudio.asia-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:01Z | |
datastudio.asia-south2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
datastudio.asia-southeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
datastudio.asia-southeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
datastudio.asia-southeast3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:03Z | |
datastudio.australia-southeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:10Z | |
datastudio.australia-southeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:04Z | |
datastudio.eu.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:48Z | |
datastudio.europe-central2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
datastudio.europe-north1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
datastudio.europe-north2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
datastudio.europe-southwest1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:06Z | |
datastudio.europe-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
datastudio.europe-west10.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
datastudio.europe-west12.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:11Z | |
datastudio.europe-west2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:07Z | |
datastudio.europe-west3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:08Z | |
datastudio.europe-west4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:08Z | |
datastudio.europe-west6.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
datastudio.europe-west8.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
datastudio.europe-west9.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
datastudio.me-central1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
datastudio.me-central2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
datastudio.me-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:12Z | |
datastudio.northamerica-northeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
datastudio.northamerica-northeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
datastudio.northamerica-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:20Z | |
datastudio.southamerica-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:14Z | |
datastudio.southamerica-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:21Z | |
datastudio.us-central1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
datastudio.us-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
datastudio.us-east4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:23Z | |
datastudio.us-east5.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:17Z | |
datastudio.us-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:17Z | |
datastudio.us-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
datastudio.us-west2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
datastudio.us-west3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:19Z | |
datastudio.us-west4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:19Z | |
datastudio.us-west8.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:20Z | |
datastudio.us.cloud.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:44Z | |
dclk.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:07Z | |
deepmind.google.com
|
CT Log | Current | — | 94 | 2026-02-02T08:36:49Z | |
deliverynavigator.cloud.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:40:20Z | |
demetrius-codespot.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
demetrius-googlecode.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
demetrius.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
demos-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
demos-strong.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
demos.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
devconsole-testers.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
developer.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
developers.google.com
|
CT Log | Current | — | 23 | 2026-02-02T08:37:13Z | |
devsite-preview.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
devsite-sni.developers.google.com
|
CT Log | Current | — | 47 | 2026-02-02T08:36:49Z | |
devsite.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:01Z | |
df35a0b9d238263.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-01-30T17:36:29Z | |
dfa7.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
dg-meta.video.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
dg.video.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:56Z | |
digiyaar.pay.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
directory.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
discover.google.com
|
CT Log | Current | — | 38 | 2026-02-02T08:37:07Z | |
dns.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:38:49Z | |
doc.google.com
|
DNS | Current |
writely.l.google.com
|
46 | 2026-02-02 | — |
docs-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
docs-platinum.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
docs-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
docs.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:38:01Z | |
docs.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
download.google.com
|
DNS | Current |
www2.l.google.com
|
46 | 2026-02-02 | — |
downloads.google.com
|
DNS | Current |
www2.l.google.com
|
46 | 2026-02-02 | — |
drive-test.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
drive.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:38:01Z | |
drive.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
dthree.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
earthengine.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
ecc-test.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:32Z | |
education.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
ef21fa1facc6746.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-03T09:13:39Z | |
ehr-search.health.google.com
|
CT Log | Current | — | 3 | 2026-02-02T08:37:07Z | |
email.google.com
|
DNS | Current |
gmail.google.com
|
46 | 2026-02-02 | — |
emergencylocator.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
enterprise.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:07Z | |
eu.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:48Z | |
europe-central2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
europe-north1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
europe-north2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
europe-southwest1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:06Z | |
europe-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
europe-west10.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
europe-west12.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:11Z | |
europe-west2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:07Z | |
europe-west3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:08Z | |
europe-west4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:08Z | |
europe-west6.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
europe-west8.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
europe-west9.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
europe.apigee.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:13Z | |
evenflow-test.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
evenflow.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
events.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
ew.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
ewoq.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:37:13Z | |
ext.google.com
|
CT Log | Current | — | 24 | 2026-02-02T08:38:23Z | |
feeds.google.com
|
DNS | Current |
uploads.google.com
|
46 | 2026-02-02 | — |
fiber.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
fife.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:38:37Z | |
fife.usercontent.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:38:37Z | |
files.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
finance.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
firebase-staging-sso.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
firebase-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
firebase.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
focus.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
forms.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
fra-dc-11.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:45:10Z | |
fra-dc-11.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:45:10Z | |
fra-dc-12.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:45:30Z | |
fra-dc-12.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:45:30Z | |
fra-nls-3.fra.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:30:18Z | |
fra-wsus-1.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:15Z | |
fra-wsus.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:15Z | |
frame.ads-devel.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ads-nightly.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ads-prod.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ads.google.com
|
CT Log | Current | — | 24 | 2026-02-02T08:37:56Z | |
frame.adwords-canary.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.adwords-detours-prod.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.adwords-next-external-devel.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.adwords-next-external-prod.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.adwords.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.canary.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ds-next-devel.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ds-next-external-devel.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ds-next-external-prod.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ds-next-nightly.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.ds-next-prod.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.searchads-canary.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
frame.searchads.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
games.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
gcbp-uipath-dev.corp.google.com
|
CT Log | Current | — | 8 | 2026-02-18T07:34:02Z | |
gemini.cloud.google.com
|
CT Log | Current | — | 46 | 2026-02-02T08:36:38Z | |
geminidataanalytics.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:58Z | |
generativeai.google.com
|
CT Log | Current | — | 47 | 2026-02-02T08:36:49Z | |
gerrit.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
get.duo.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:52Z | |
ggp.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
git.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
gleeok-pacserver.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
gmail-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
gmr-mx.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
gmr-smtp-in.l.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
googlesource-testing.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
googlesource.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
goto.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:09Z | |
gplex-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
grow.google.com
|
CT Log | Current | — | 24 | 2026-02-02T08:37:35Z | |
gsuite.google.com
|
CT Log | Current | — | 9 | 2026-02-02T08:39:51Z | |
guidebooks.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:40:14Z | |
gutenberg-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
gutenberg-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
gutenberg.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
gw.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
gw1.google.com
|
DNS | Current |
gw.l.google.com
|
46 | 2026-02-02 | — |
gw2.google.com
|
DNS | Current |
gw.l.google.com
|
46 | 2026-02-02 | — |
gws-demos.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
gws-mobile-demos.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
h5games-autopush.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
h5games-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
h5games-prod.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
h5games-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
h5games.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
hangouts.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
hangouts.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
health.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
healthcare.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
help.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
home.google.com
|
CT Log | Current | — | 114 | 2026-02-02T08:36:39Z | |
hot-dc-11.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:45:49Z | |
hot-dc-11.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:45:49Z | |
hot-dc-13.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:46:08Z | |
hot-dc-13.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:46:08Z | |
hot-dc-14.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:46:27Z | |
hot-dc-14.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:46:27Z | |
hot-nls-3.hot.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:30:18Z | |
hot-wsus-1.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:31Z | |
hot-wsus.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:31Z | |
hybrid.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
ics-devel-east.qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
ics.prod.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
id.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
il.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:42Z | |
image.google.com
|
DNS | Current |
images.google.com
|
46 | 2026-02-02 | — |
images.google.com
|
DNS | Current |
images.l.google.com
|
46 | 2026-02-02 | — |
in.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:43Z | |
inbox.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:47Z | |
investor.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
investors.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
it.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:49Z | |
jibe.google.com
|
CT Log | Current | — | 9 | 2026-02-02T08:38:57Z | |
jobs.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
jotspot-qa08.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
jp.cloud.google.com
|
CT Log | Current | — | 50 | 2026-02-02T08:36:50Z | |
labs.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
landing.pay.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
ld.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
ldap.google.com
|
CT Log | Current | — | 9 | 2026-02-02T08:38:48Z | |
learn.mapsplatform.google.com
|
CT Log | Current | — | 94 | 2026-02-02T08:36:49Z | |
learning.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
legaldms-dev-no-cert.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
legaldms-no-cert.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
legaldms-uat-no-cert.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
lh3-da.photos0.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-db.photos1.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-dc.photos2.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-dd.photos3.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-de.photos4.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-df.photos5.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-dg.photos6.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-dy.photos-staging.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
lh3-dz.photos-autopush.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
litespeed-proxy.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
login-canary.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
login-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
login-stable.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
login-test.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
login.corp.google.com
|
CT Log | Current |
uberproxy.l.google.com
|
4 | 2026-02-18T07:34:14Z | |
lookerstudio.africa-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:58Z | |
lookerstudio.asia-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:59Z | |
lookerstudio.asia-east2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
lookerstudio.asia-northeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:59Z | |
lookerstudio.asia-northeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:00Z | |
lookerstudio.asia-northeast3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:07Z | |
lookerstudio.asia-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:01Z | |
lookerstudio.asia-south2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
lookerstudio.asia-southeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
lookerstudio.asia-southeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:02Z | |
lookerstudio.asia-southeast3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:03Z | |
lookerstudio.australia-southeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:10Z | |
lookerstudio.australia-southeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:04Z | |
lookerstudio.eu.cloud.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:36:48Z | |
lookerstudio.europe-central2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
lookerstudio.europe-north1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
lookerstudio.europe-north2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:05Z | |
lookerstudio.europe-southwest1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:06Z | |
lookerstudio.europe-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
lookerstudio.europe-west10.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
lookerstudio.europe-west12.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:11Z | |
lookerstudio.europe-west2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:07Z | |
lookerstudio.europe-west3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:08Z | |
lookerstudio.europe-west4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:08Z | |
lookerstudio.europe-west6.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
lookerstudio.europe-west8.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
lookerstudio.europe-west9.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
lookerstudio.me-central1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
lookerstudio.me-central2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
lookerstudio.me-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:12Z | |
lookerstudio.northamerica-northeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
lookerstudio.northamerica-northeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
lookerstudio.northamerica-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:20Z | |
lookerstudio.southamerica-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:14Z | |
lookerstudio.southamerica-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:21Z | |
lookerstudio.us-central1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
lookerstudio.us-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
lookerstudio.us-east4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:23Z | |
lookerstudio.us-east5.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:17Z | |
lookerstudio.us-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:17Z | |
lookerstudio.us-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
lookerstudio.us-west2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
lookerstudio.us-west3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:19Z | |
lookerstudio.us-west4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:19Z | |
lookerstudio.us-west8.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:20Z | |
lookerstudio.us.cloud.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:44Z | |
loop.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
lti.drive.usercontent.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:38:37Z | |
lti.gemini.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:37:19Z | |
lti.gemini.usercontent.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:38:37Z | |
lti.meet.usercontent.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:38:37Z | |
lti.workspace.usercontent.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:38:37Z | |
lz.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
m.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:38:53Z | |
m.guts.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
m.gutsdev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
machinelearningtools-autopush.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
machinelearningtools-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
machinelearningtools-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
machinelearningtools.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
mail-dispatcher.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-gemini.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-griffin.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-ls0.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-ls1.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-ls2.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-ls3.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-ls4.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-qa0.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-qa1.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-qa2.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-qa3.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-qa4.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
mail-settings.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
mail.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:38:02Z | |
mail.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
malachite-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
malachite-looker-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
malachite-looker-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
malachite-preprod.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
malachite-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
malachite-test.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
manifest.lh3-da.photos0.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-db.photos1.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-dc.photos2.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-dd.photos3.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-de.photos4.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-df.photos5.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-dg.photos6.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-dy.photos-staging.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3-dz.photos-autopush.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
manifest.lh3.photos.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:55Z | |
map.google.com
|
DNS | Current |
maps.google.com
|
46 | 2026-02-02 | — |
mapmaker.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
maps.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
me-central1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
me-central2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
me-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:12Z | |
meet-quality.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
meet.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
meet.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
merchantstories.pay.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
microhost.google.com
|
CT Log | Current |
www3.l.google.com
|
11 | 2026-02-02T08:37:07Z | |
misc-sni.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
misc.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
mlcc.google.com
|
CT Log | Current | — | 92 | 2026-02-02T08:36:53Z | |
mobile.google.com
|
DNS | Current |
mobile.l.google.com
|
46 | 2026-02-02 | — |
mtls.clients6.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:01Z | |
mtls.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:01Z | |
mtls.hybrid.sandbox.google.com
|
CT Log | Current | — | 31 | 2026-02-02T08:38:12Z | |
mtls.pa.clients6.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:01Z | |
mtls.pa.sandbox.google.com
|
CT Log | Current | — | 31 | 2026-02-02T08:38:12Z | |
mtls.sandbox.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:40:01Z | |
mx.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
myaccount.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
negocio.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:10Z | |
nestrenew.google.com
|
CT Log | Current | — | 92 | 2026-02-02T08:36:53Z | |
news.google.com
|
CT Log | Current | — | 22 | 2026-02-02T08:38:36Z | |
nls-anycast.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:30:18Z | |
northamerica-northeast1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
northamerica-northeast2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:13Z | |
northamerica-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:20Z | |
northamerica.apigee.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:37:13Z | |
notebooks.cloud.google.com
|
CT Log | Current |
www3.l.google.com
|
11 | 2026-02-02T08:37:07Z | |
notifications.google.com
|
DNS | Current |
plus.l.google.com
|
46 | 2026-02-02 | — |
ns.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
ns1.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
ns2.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
ns3.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
ns4.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
onetoday-dev.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
oz-gmail.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
oz-guc.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
oz-s2.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
oz-www.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
p.sandbox.google.com
|
CT Log | Current | — | 14 | 2026-02-02T08:38:54Z | |
pa.clients6.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:58Z | |
pa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
paidtasks-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
paidtasks.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pantheon-ci.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pantheon-demos.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pantheon-sandbox.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pantheon-staging-sso.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pantheon-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pantheon-tests.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
partners.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
partnertest.fi.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:10Z | |
pay.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
payments.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:38:54Z | |
photos.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:01Z | |
ping.feedburner.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
pipelines.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
pki.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
plus.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
plusapis.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
plusone.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
policies.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
postini.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
print.google.com
|
DNS | Current |
www2.l.google.com
|
46 | 2026-02-02 | — |
printer.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:10Z | |
privacy.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
privacysandbox.google.com
|
CT Log | Current | — | 132 | 2026-02-02T08:36:49Z | |
products.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
profile.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
profiles.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
programmablesearchengine.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:37Z | |
projects.x20web-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
projects.x20web.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
prom-gfe-nightly.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom-gfe-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom-nightly-gp.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom-nightly.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom-qa-gs.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom-test.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
prom.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
proxyconfig-canary.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
proxyconfig-testing.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
proxyconfig.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pxecontrol-test.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
pxecontrol.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
qa.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
r.ext.google.com
|
CT Log | Current | — | 2 | 2026-02-09T14:12:35Z | |
radius-machineauth-anycast.corp.google.com
|
CT Log | Current | — | 12 | 2026-02-03T01:08:27Z | |
rcs-adamantium-autopush.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
rcs-adamantium-staging-loadtest.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
rcs-adamantium-staging-us.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
realtime.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
recorder-autopush.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
recorder-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
recorder-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
recorder.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:29Z | |
region1.analytics.google.com
|
CT Log | Current | — | 54 | 2026-02-02T08:36:44Z | |
registry.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
rewards.google.com
|
CT Log | Current | — | 54 | 2026-02-02T08:37:29Z | |
rewsgemini.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
rtcsupport.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
s.svc-1.google.com
|
CT Log | Current | — | 24 | 2026-02-02T08:37:13Z | |
sa.cloud.google.com
|
CT Log | Current | — | 50 | 2026-02-02T08:36:44Z | |
sandbox.google.com
|
CT Log | Current | — | 52 | 2026-02-02T08:38:00Z | |
sandbox.mtls.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:01Z | |
script.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
search.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
search.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
services.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
shop.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
sites-googlegroups-nightly.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
sites-googlegroups-qa06.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
sites-googlegroups-qa07.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
sites-googlegroups-qa08.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
sites-googlegroups-tctest.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
sites.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
sites.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
skills.google.com
|
CT Log | Current | — | 92 | 2026-02-02T08:36:56Z | |
smtp-proxy.corp.google.com
|
CT Log | Current | — | 2 | 2026-02-03T01:09:13Z | |
smtp.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:05Z | |
snaxca-api.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
solutions.cloud.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:40:20Z | |
southamerica-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:14Z | |
southamerica-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:21Z | |
southamerica.apigee.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:13Z | |
spam-test.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
spam.adz.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:02Z | |
speech.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:37:13Z | |
splat-svr.hot.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:03Z | |
sslproxy.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:11Z | |
staging-gerrit.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
staging-git.corp.google.com
|
CT Log | Current |
uberproxy.l.google.com
|
4 | 2026-02-18T07:34:06Z | |
startup.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:38:42Z | |
status.play.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:18Z | |
status.search.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:40:24Z | |
store.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
streetviewstudio.maps.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:40:20Z | |
supl.google.com
|
CT Log | Current | — | 9 | 2026-02-02T08:38:56Z | |
support.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:13Z | |
survey.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
surveys.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
talkgadget.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:02Z | |
teams.x20web-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
teams.x20web.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
telus-voice-staging.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:25Z | |
telus.voice.google.com
|
CT Log | Current |
www3.l.google.com
|
11 | 2026-02-02T08:38:25Z | |
tensorboard-autopush.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
tensorboard-dev.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
tensorboard-staging.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
tensorboard-test.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
tensorboard.cloud.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:37:07Z | |
tensorflow.google.com
|
CT Log | Current | — | 92 | 2026-02-02T08:36:52Z | |
test-bigquery.eu.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
test-bigquery.us.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
test.devsite.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:01Z | |
test.postini.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
testing-git.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
testmx.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:37:59Z | |
tez.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
time.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
tokenized.play.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
tools.google.com
|
DNS | Current |
tools.l.google.com
|
46 | 2026-02-02 | — |
tuf-autopush-qual.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-autopush.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-file-autopush.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-file-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-file-prod.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-file-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-prod.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
tuf-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
twd-dc-11.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:46:45Z | |
twd-dc-11.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:46:45Z | |
twd-dc-12.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:47:04Z | |
twd-dc-12.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T17:47:04Z | |
twd-nls-4.twd.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:30:18Z | |
twd-wsus-1.ad.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:47Z | |
twd-wsus.corp.google.com
|
CT Log | Current | — | 1 | 2026-02-18T16:49:47Z | |
tx.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
tz.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
uberproxy.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
uc.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
ue.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
uk.cloud.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:50Z | |
uk.r.prom-qa.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
up.sandbox.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
upload.google.com
|
CT Log | Current | — | 20 | 2026-02-02T08:38:01Z | |
upload.video.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:01Z | |
uploads.google.com
|
DNS | Current |
feedsftp.l.google.com
|
46 | 2026-02-02 | — |
urchin.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
url.google.com
|
CT Log | Current | — | 46 | 2026-02-02T08:36:38Z | |
us-central1.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-central1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:15Z | |
us-central1.mtls.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-central2.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-central2.mtls.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-east1.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-east1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:16Z | |
us-east1.mtls.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-east4.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-east4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:23Z | |
us-east4.mtls.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-east5.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:17Z | |
us-south1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:17Z | |
us-west1.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-west1.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
us-west1.mtls.cloud-run-qual.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
us-west2.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:18Z | |
us-west3.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:19Z | |
us-west4.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:19Z | |
us-west8.cloud.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:41:20Z | |
us.cloud.google.com
|
CT Log | Current | — | 48 | 2026-02-02T08:36:44Z | |
usercontent.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
usercontent.google.com
|
CT Log | Current | — | 16 | 2026-02-02T08:38:37Z | |
usercontent.sandbox.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:38:37Z | |
users.x20web-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
users.x20web.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:14Z | |
v.ext.google.com
|
CT Log | Current | — | 1 | 2026-01-27T21:42:16Z | |
vault.google.com
|
DNS | Current |
www4.l.google.com
|
46 | 2026-02-02 | — |
vi-old.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:12Z | |
vi-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:12Z | |
vi.corp.google.com
|
CT Log | Current |
uberproxy.l.google.com
|
4 | 2026-02-18T07:34:12Z | |
viceroy-old.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:12Z | |
viceroy-qa.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:12Z | |
viceroy.corp.google.com
|
CT Log | Current |
uberproxy.l.google.com
|
4 | 2026-02-18T07:34:12Z | |
video.google.com
|
DNS | Current |
video.l.google.com
|
46 | 2026-02-02 | — |
videos.google.com
|
DNS | Current |
video.google.com
|
46 | 2026-02-02 | — |
voice-search-dev.sandbox.google.com
|
CT Log | Current | — | 15 | 2026-02-02T08:38:12Z | |
vp.video.l.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:56Z | |
vpn.google.com
|
DNS | Current | — | 46 | 2026-02-02 | — |
wallet.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:54Z | |
web.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
webapp-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webapp-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webapp.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webapp.google.com
|
CT Log | Current | — | 11 | 2026-02-02T08:38:52Z | |
webapps-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webapps-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webapps.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webapps.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:58Z | |
webdrive-test-canary.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webdrive-test-prod.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webview-cider-v-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webview-cider-v-test.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
webview-cider-v.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
wetdocs.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
wetlab.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
wifi.google.com
|
CT Log | Current | — | 10 | 2026-02-02T08:38:25Z | |
work.google.com
|
DNS | Current |
www3.l.google.com
|
46 | 2026-02-02 | — |
workspace.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:39:52Z | |
wpt-autopush.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
wpt-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
wpt-staging.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
www.ads.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:56Z | |
www.adwords.google.com
|
CT Log | Current | — | 12 | 2026-02-02T08:37:56Z | |
www.google.com
|
CT Log | Current | — | 8 | 2026-02-02T08:38:52Z | |
xbox-neko-dev.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
xbox-neko.corp.google.com
|
CT Log | Current | — | 4 | 2026-02-18T07:34:06Z | |
xup.corp.google.com
|
CT Log | Current | — | 8 | 2026-02-17T14:31:05Z |
Δ 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
173.194.193.100
74.125.132.138
173.194.193.101
74.125.132.113
173.194.193.102
74.125.132.100
173.194.193.113
74.125.132.102
173.194.193.138
74.125.132.139
173.194.193.139
74.125.132.101
AAAA
Propagating
4 / 4 records
2607:f8b0:4001:c0f::64
2607:f8b0:4001:c00::64
2607:f8b0:4001:c0f::65
2607:f8b0:4001:c00::71
2607:f8b0:4001:c0f::66
2607:f8b0:4001:c00::8b
2607:f8b0:4001:c0f::8a
2607:f8b0:4001:c00::66
0 issue "pki.goog"
0 issue "pki.goog"
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
v=STSv1; id=20210803T010101;
v=STSv1; id=20210803T010101;
10 smtp.google.com.
10 smtp.google.com.
ns1.google.com.
ns4.google.com.
ns2.google.com.
ns2.google.com.
ns3.google.com.
ns1.google.com.
ns4.google.com.
ns3.google.com.
ns1.google.com. dns-admin.google.com. 905477423 900 900 1800 60
ns1.google.com. dns-admin.google.com. 905477423 900 900 1800 60
v=TLSRPTv1;rua=mailto:sts-reports@google.com
v=TLSRPTv1;rua=mailto:sts-reports@google.com
MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB
onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0
apple-domain-verification=30afIBcvSuDV2PLX
facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b
google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ
docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e
cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b
docusign=1b0a6754-49b1-4db5-8540-d2c12664b289
v=spf1 include:_spf.google.com ~all
facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0
globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=
—
google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0
—
google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ
—
google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o
—
onetrust-domain-verification=0d477fe608074e6f9c12bca7826035cc
—
onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0
—
v=spf1 include:_spf.google.com ~all
—
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA
When was a record added, removed, or changed — and could that change be the problem?
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.
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.
1b9ef1fb5b86aa443f7a41780a8d74a2f8375676a0682f03ac9aeeb1119e3237d25493a4c3fe0a323199b2d2c426483d5abf53f5b222d5e65641cf00a852cea7
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 26 Apr 2026, 18:18 UTC.
Internet Archive — Permanent Record Wayback Machine Can this analysis be independently verified? Archived
This analysis has been automatically submitted to the Internet Archive's Wayback Machine, creating a tamper-evident, third-party-hosted snapshot of the DNS security posture at analysis time. This archived copy is independent of DNS Tool — it provides an independently verifiable record of the analysis at this point in time. Combined with the SHA-3-512 integrity hash, this creates a verifiable chain of evidence for domain security state.
Snapshot preserved at
https://web.archive.org/web/20260426181846/https://dnstool.it-help.tech/analysis/16376/view/E
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/16376/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 TXTEmail 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 TXTDomain 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.1Transport 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 TXTBrand & 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 CAADNS Records
Check HTTPS/SVCB records RFC 9460
dig +noall +answer google.com HTTPSDomain Security
Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer google.com CDSInfrastructure Intelligence
RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/google.com' | python3 -m json.tool | head -50Transport 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 -5Infrastructure 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 -20AI 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 173.194.193.100 (Team Cymru)
dig +short 100.193.194.173.origin.asn.cymru.com TXT
ASN lookup for 173.194.193.101 (Team Cymru)
dig +short 101.193.194.173.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
consistent · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Consistent
15106 runs
DKIM
Consistent
14883 runs
DMARC
Consistent
15087 runs
DANE/TLSA
Consistent
14865 runs
DNSSEC
Consistent
15064 runs
BIMI
Consistent
14880 runs
MTA-STS
Consistent
14901 runs
TLS-RPT
Consistent
14916 runs
CAA
Consistent
14913 runs
Maturity:
Development
→
Verified
→
Consistent
→
Gold
→
Gold Master
Appendix: Verification Commands
DNS Records
dig +noall +answer google.com Adig +noall +answer google.com AAAAdig +noall +answer google.com MXdig +noall +answer google.com NSdig +noall +answer google.com TXTEmail Authentication
dig +short google.com TXT | grep -i spfdig +short _dmarc.google.com TXTdig +short default._domainkey.google.com TXTdig +short google._domainkey.google.com TXTdig +short selector1._domainkey.google.com TXTdig +short selector2._domainkey.google.com TXTDomain Security
dig +dnssec +noall +answer google.com DNSKEYdig +noall +answer google.com DSdig +dnssec +cd google.com A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.smtp.google.com TLSAopenssl s_client -starttls smtp -connect smtp.google.com:25 -servername smtp.google.com 2>/dev/null | openssl x509 -noout -subject -datesdig +short _mta-sts.google.com TXTcurl -sL https://mta-sts.google.com/.well-known/mta-sts.txtdig +short _smtp._tls.google.com TXTBrand & Trust
dig +short default._bimi.google.com TXTdig +noall +answer google.com CAADNS Records
dig +noall +answer google.com HTTPSDomain Security
dig +noall +answer google.com CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/google.com' | python3 -m json.tool | head -50Transport Security
openssl s_client -starttls smtp -connect smtp.google.com:25 -servername smtp.google.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
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 -20curl -sL https://google.com/.well-known/security.txt | head -20AI Surface
curl -sI https://google.com/llms.txt | head -5curl -s https://google.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 100.193.194.173.origin.asn.cymru.com TXTdig +short 101.193.194.173.origin.asn.cymru.com TXT