How is google.co.jp?

Looks fine risk 0/100

Registered 26 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 142 ms.

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.

Site

200

142 ms · ends at www.google.com

HTTPS

53 d

left on a Google Trust Services certificate

Age

26 years

registered 2001-03-22

Blocklists

listings across 5 lists

Everything we looked at

DNS records6 record types

A	192.178.155.94
AAAA	2607:f8b0:4004:c1b::5e
MX	0 smtp.google.com
NS	ns3.google.com ns4.google.com ns2.google.com ns1.google.com
TXT	v=spf1 -all
CAA	{'type': 'CAA', 'issue': 'pki.goog', 'critical': 0}

Registrationregistrar not reported

registered	2001-03-22
expires	2027-03-31
last changed	2026-04-01
owner	Google Japan G.K.
nameservers	ns1.google.com ns2.google.com ns3.google.com ns4.google.com
status	Connected (2027/03/31)

registered 2001-03-22expires 2027-03-31

HTTPS certificate53 days left

valid	yes
issuer	Google Trust Services
covers	*.google.co.jp, google.co.jp
protocol	TLSv1.3

issued 2026-09-28expires 2026-12-21

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → google.co.jp

Email authenticationgood

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.

Security scoregrade B · 150/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

45/45missing: DKIM Presence

Advanced Security

15/25missing: Mail Server Configuration, SOA Record Configuration

Domain Reputation

35/50missing: Typosquatting Check

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop142.251.179.94Barracuda142.251.179.94UCEPROTECT Level 1142.251.179.94

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

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.

curl "https://how.is/v1/domain/trust?domain=google.co.jp" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=google.co.jp"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on google.co.jp. Reference: /llms.txt.

Watch google.co.jp. 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