How is keirin.jp?

Looks fine risk 0/100

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

890 ms

HTTPS

121 d

left on a DigiCert Inc certificate

Age

26 years

registered 2001-03-26

Blocklists

listings across 4 lists; 1 did not answer

Everything we looked at

DNS records4 record types

A	3.170.42.11 3.170.42.30 3.170.42.66 3.170.42.69
MX	10 feedback-smtp.ap-northeast-1.amazonses.com
NS	ns-128.awsdns-16.com ns-1314.awsdns-36.org ns-1760.awsdns-28.co.uk ns-873.awsdns-45.net
TXT	_zeplq5etxjr2my01ojis9usskdkyha1 google-site-verification=ZPvi3sfcdDJldOxiofcH4x5tA8eIbZC2JyCRA3d-qV8 google-site-verification=dIoL01bjHs4Iz7AxEihKYvJL_phKNmY_-LIDX_BIT1c v=spf1 include:amazonses.com include:spf.haihaimail.jp ~all

Registrationregistrar not reported

registered	2001-03-26
expires	2027-03-31
last changed	2026-04-01
owner	JKA
nameservers	ns-128.awsdns-16.com ns-873.awsdns-45.net ns-1314.awsdns-36.org ns-1760.awsdns-28.co.uk
status	Active

registered 2001-03-26expires 2027-03-31

HTTPS certificate121 days left

valid	yes
issuer	DigiCert Inc
covers	*.keirin.jp, keirin.jp
protocol	TLSv1.3

issued 2026-02-13expires 2027-02-28

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → keirin.jp

Email authenticationfair

SPF	pass `v=spf1 include:amazonses.com include:spf.haihaimail.jp ~all`
DMARC	warning policy none
DKIM	none of 1 common selectors

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

Security scoregrade B · 153/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

23/45missing: CAA Records, DMARC Record, DKIM Presence

Advanced Security

15/25missing: Mail Server Configuration, IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 14 lookups

SURBL MultidomainURIBL MultidomainSpamCop3.170.42.66Barracuda3.170.42.66UCEPROTECT Level 13.170.42.66SpamCop3.170.42.30Barracuda3.170.42.30UCEPROTECT Level 13.170.42.30SpamCop3.170.42.69Barracuda3.170.42.69UCEPROTECT Level 13.170.42.69SpamCop3.170.42.11Barracuda3.170.42.11UCEPROTECT Level 13.170.42.11

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

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

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