Registered 22 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 231 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 192.178.155.94 |
|---|---|
| AAAA | 2607:f8b0:4004:c23::5e |
| MX | 0 smtp.google.com |
| NS | ns2.google.com ns3.google.com ns4.google.com ns1.google.com |
| TXT | v=spf1 -all |
| CAA | {'type': 'CAA', 'issue': 'pki.goog', 'critical': 0} |
| registrar | PT Digital Registra Indonesia |
|---|---|
| registered | 2004-12-18 |
| expires | 2027-09-01 |
| last changed | 2026-08-08 |
| nameservers | ns1.google.com ns2.google.com ns3.google.com ns4.google.com |
| status | client delete prohibited client renew prohibited client transfer prohibited client update prohibited server delete prohibited server transfer prohibited |
| valid | yes |
|---|---|
| issuer | Google Trust Services |
| covers | *.google.co.id, google.co.id |
| protocol | TLSv1.3 |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 -all |
|---|---|
| DMARC | pass policy reject |
| DKIM | none of 1 common selectors |
Whether mail claiming to be from this domain can be checked as genuine.
Green: clean. Red: listed. Grey: the list did not answer.
Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on google.co.id.
Reference: /llms.txt.
IPv6. Does google.co.id work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch google.co.id. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.
Watch — $1 / 30 days