How is alphapolis.co.jp?

Looks fine risk 0/100

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

777 ms · ends at www.alphapolis.co.jp

HTTPS

67 d

left on a DigiCert Inc certificate

Age

26 years

registered 2000-09-12

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	3.170.22.98
MX	10 aspmx.l.google.com 30 alt3.aspmx.l.google.com 30 alt4.aspmx.l.google.com 20 alt1.aspmx.l.google.com 20 alt2.aspmx.l.google.com
NS	ns-373.awsdns-46.com ns-1608.awsdns-09.co.uk ns-862.awsdns-43.net ns-1468.awsdns-55.org
TXT	v=spf1 +ip4:52.69.43.103 include:spf.baremetal.jp include:_spf.google.com include:spf.rakurakuhanbai.jp ~all box-domain-verification=35fcf9e5f9ac85caca2f62e642c7ee1b8b45ca94a1ef82df3de288347d3ab2eb

Registrationregistrar not reported

registered	2000-09-12
expires	2027-09-30
last changed	2026-10-01
owner	alphapolis
nameservers	ns-373.awsdns-46.com ns-862.awsdns-43.net ns-1608.awsdns-09.co.uk ns-1468.awsdns-55.org
status	Connected (2027/09/30)

registered 2000-09-12expires 2027-09-30

HTTPS certificate67 days left

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

issued 2026-01-05expires 2027-01-05

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → alphapolis.co.jp

Email authenticationexcellent

SPF	pass `v=spf1 +ip4:52.69.43.103 include:spf.baremetal.jp include:_spf.google.com include:spf.rakurakuhanbai.jp ~all`
DMARC	pass policy quarantine
DKIM	found: google

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

Security scoregrade B · 165/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

30/45missing: CAA Records, DKIM Presence

Advanced Security

20/25missing: IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop3.170.22.98Barracuda3.170.22.98UCEPROTECT Level 13.170.22.98

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

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

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