| Field | Content |
|---|---|
| Name | google.com (apex) |
| Correlation | Google LLC (organization field in Registrar RDAP, redacted WHOIS-grade details) |
| Country | United States (registration context per RDAP indicators) |
| Website | https://google.com |
| Purpose | Primary OSINT / counterparty perimeter screening against open sources · no subpoena-scope claims |
| Data collected | 2026-05-20 (timezone of query environment: coordinated universal sample timestamps in APIs) |
| Open questions | Which Alphabet/Google contracting entity executes your agreement; geopolitical exposure not exhaustively enumerated in this domain-only pass. |
Object: Internet domain name google.com (apex). Associated organization (technical registration layer): Google LLC appears as the RDAP registrant organization MarkMonitor publishes with privacy redaction.
Identifiers: IANA Registrar ID 292 (MarkMonitor Inc.); RDAP handles include 2138514_DOMAIN_COM-VRSN via Verisign COM RDAP bootstrap.
Operational note: This review is perimeter-level; Alphabet Inc. subsidiaries outside Google LLC are excluded unless public sources tie them to this domain delegation.
Across DNS, Registrar RDAP, and Verisign registry RDAP, google.com behaves like Google’s authoritative production apex: delegated to NS1–NS4.GOOGLE.COM, resolves to IPv4 endpoints inside Google’s routed address space (ASN 15169 per RIPEstat for the queried /24 enclosure), publishes enterprise-style SPF delegation to Google’s SMTP policy, and is locked with standard ICANN transfer/update prohibitions typical of marquee brands.
18 / 100 — low band on the methodology scale: 0–20 · Low risk.
Rationale: No spoofed DNS patterns or obvious typo-squatter footprint were evident in sampled technical channels; reputational/policy exposure exists at the global regulatory level for Alphabet generally, but nothing in these technical registries independently elevates transactional risk comparable to sanctioned, insolvent, or anonymous high-risk hosting clusters.
confirmed fact No materially adverse technical red flags surfaced in Registrar/Registry RDAP status codes sampled on 2026-05-20 (multi-year registration horizon, registrar locks consistent with theft protection).
requires manual check Policy/compliance narratives (competition remedies, privacy orders, geopolitical localization) evolve quickly; correlate with counsel if your use-case imposes sectoral restrictions irrespective of benign DNS fingerprints.
confirmed fact Registry RDAP (Verisign COM RDAP) lists creation 1997-09-15, expiration 2028-09-14 (timezone-normalized timestamps differ slightly vs MarkMonitor mirror), authoritative NS NS1–NS4.GOOGLE.COM, and delegationSigned: false at COM delegation.
confirmed fact Registrar RDAP (MarkMonitor) discloses organizational registrant handle Google LLC; personal/registrant contact fields are GDPR-style redacted with a registrar contact pathway.
probable link Brand-consistency strongly indicates operational control rests with Alphabet’s Google naming operations; further corporate-tree mapping requires SEC filings rather than WHOIS alone.
confirmed fact Public RDAP publishes organization “Google LLC” for the registrant role; natural-person UBO is not surfaced (redacted).
requires manual check Ultimate shareholders of Alphabet publicly trade under NASDAQ:GOOGL/GOOG — reconcile with equities disclosure rather than WHOIS proxies when UBO granularity is mandated.
probable link Organizational ecosystem includes Alphabet subsidiaries and regional affiliates; domain DNS alone cannot enumerate them.
hypothesis Numerous third-party vendor TXT proofs (Adobe, Cisco, DocuSign, Facebook, GlobalSign cues, Apple domain verification tokens) coexist on the apex — consistent with a heavily integrated digital brand perimeter; each token asserts a relationship only with vendor-side verification workflows.
requires manual check This automated perimeter pass did not replace official screening in OFAC Sanctions Search, consolidated EU listings, UN lists, HM Treasury sanctions, or NSDC-derived Ukraine instruments when your policy demands them.
confirmed fact The subject is universally recognized Silicon Valley-origin infrastructure; notwithstanding, deterministic negatives must be queried in your sanctioned-party workflow naming the concrete legal entity of contract.
probable link Alphabet/Google participates in voluminous litigation and regulatory proceedings globally.
requires manual check No case-level docket review was attempted here; escalate with counsel/PACER or national court APIs if filings affect your contractual theory.
requires manual check Domain/WHOIS data do not reveal tax delinquencies or judgments; verifying corporate treasury health is beyond OSINT registrar channels.
probable link Persistent public discourse covers privacy practices, ads policy, geopolitical moderation, AI safety, labor relations, competition — standard major-tech profile.
confirmed fact No reliance was placed here on scraped forums/leaks/off-channel datasets.
confirmed fact Not materially applicable at domain-only scope; procurements referencing Google identifiers would require discrete Prozorro / SAM / national tender registry searches keyed to awarding entity taxonomy.
✅ Clear to proceed — for benign technical counterparty onboarding where the apex domain legitimacy is decisive. Continue with transactional mapping to the contracting legal entity, refreshed sanctions screenings, and contract-specific DPIA/policy checks where warranted.
probable link Lack of delegated DNSSEC (per RDAP secureDNS.delegationSigned = false) is noteworthy for spoofing-conscious architectures but commonplace among major consumer brands weighing operational complexity vs protocol adoption.
requires manual check Natural-person beneficiaries are inaccessible through RDAP; rely on equities filings, contractual reps, or national corporate registers keyed to signer entities.
| Criterion | Triggered | Factual basis (snapshot) |
|---|---|---|
| Sanctions (official lists) | no (not exhaustively enumerated) | Requires your formal workflow requires manual check |
| Connection to RF / RB / occupied territories | n/a | Not assessed geopolitically in this perimeter pass · requires manual check if mandated by policy. |
| Bankruptcy / insolvency | no | No insolvency cues drawn from Registrar/Registry technical objects. |
| High litigation activity | contextual only | Qualitatively plausible for marquee tech — probable link; no tally. |
| Media negative | not scored | Ambient policy debates exist globally — not scored numerically herein. |
| Final risk score · Range | 18 / 100 — 0–20 · Low risk | |
| OFAC SDN snapshot (automated perimeter) | Not enumerated here |
| EU Financial Sanctions / UK OFSI snapshot | Not enumerated here |
| Ukraine · State Register of Sanctions (NSDC) | Not enumerated here · use drs.nsdc.gov.ua in production checks |
| ICANN Registrar accreditation (reference) | MarkMonitor (IANA ID 292) visible in RDAP |
| Brand / DNS alignment | Internal Google NS delegation + routed AS footprint |
Perimeter completeness & access constraints snapshot