How is yahoo.co.jp?

Looks fine risk 0/100

Registered 7 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 1512 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

1512 ms · ends at www.yahoo.co.jp

HTTPS

117 d

left on a Cybertrust Japan Co., Ltd. certificate

Age

7 years

registered 2019-09-27

Blocklists

listings across 5 lists

Everything we looked at

DNS records5 record types

A	118.151.252.124 124.83.190.252 124.83.187.252 124.83.190.124 182.22.23.124 118.151.252.252 124.83.187.124 182.22.23.252
MX	10 mx1.mail.yahoo.co.jp 10 mx5.mail.yahoo.co.jp 10 mx3.mail.yahoo.co.jp 10 mx2.mail.yahoo.co.jp
NS	ns02.yahoo.co.jp ns12.yahoo.co.jp ns11.yahoo.co.jp ns01.yahoo.co.jp
TXT	v=spf1 include:spf.yahoo.co.jp ~all google-site-verification=GvbYgNin-mY73VbS4IJK2D8nI3tHEf2NpRdy76VYqBU
CAA	{'type': 'CAA', 'iodef': 'mailto:nic-admin@mail.yahoo.co.jp', 'critical': 0} {'type': 'CAA', 'issue': 'digicert.com;cansignhttpexchanges=yes', 'critical': 0} {'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0} {'type': 'CAA', 'issue': 'cybertrust.ne.jp', 'critical': 0}

Registrationregistrar not reported

registered	2019-09-27
expires	2027-09-30
last changed	2026-10-01
owner	LY Corporation
nameservers	ns01.yahoo.co.jp ns02.yahoo.co.jp ns11.yahoo.co.jp ns12.yahoo.co.jp
status	Connected (2027/09/30)

registered 2019-09-27expires 2027-09-30

HTTPS certificate117 days left

valid	yes
issuer	Cybertrust Japan Co., Ltd.
covers	edge01.yahoo.co.jp, .yahoo.co.jp, .yahooapis.jp, .ane.yahoo.co.jp, .auctions.yahoo.co.jp, .auctions.yahooapis.jp, .box.yahooapis.jp, .bylines.news.yahoo.co.jp, .c.yimg.jp, .carnavi.yahooapis.jp, .carview.co.jp, *.carview.yahoo.co.jp
protocol	TLSv1.3

issued 2026-08-07expires 2027-02-21

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → yahoo.co.jp

Email authenticationgood

SPF	pass `v=spf1 include:spf.yahoo.co.jp ~all`
DMARC	pass policy quarantine
DKIM	none of 1 common selectors

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade C · 140/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

45/45missing: DKIM Presence

Advanced Security

15/25missing: SOA Record Configuration, IPv6 Support

Domain Reputation

35/50missing: Typosquatting Check

Threat Detection

35/45missing: Fast-Flux Detection, Domain Age Check

Blocklists0 listings · 17 lookups

SURBL MultidomainURIBL MultidomainSpamCop182.22.23.124Barracuda182.22.23.124UCEPROTECT Level 1182.22.23.124SpamCop118.151.252.252Barracuda118.151.252.252UCEPROTECT Level 1118.151.252.252SpamCop182.22.23.252Barracuda182.22.23.252UCEPROTECT Level 1182.22.23.252SpamCop124.83.187.124Barracuda124.83.187.124UCEPROTECT Level 1124.83.187.124SpamCop124.83.190.124Barracuda124.83.190.124UCEPROTECT Level 1124.83.190.124

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=yahoo.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=yahoo.co.jp"

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

Watch yahoo.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