How is dto.jp?

Looks fine risk 0/100

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

403

40 ms

HTTPS

171 d

left on a Amazon certificate

Age

19 years

registered 2007-11-07

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	3.170.42.111 3.170.42.30 3.170.42.105 3.170.42.119
MX	255 mail.dto.jp
NS	ns-1391.awsdns-45.org ns-2021.awsdns-60.co.uk ns-296.awsdns-37.com ns-887.awsdns-46.net
TXT	google-site-verification=NCRKKD8sFpRvSXeNN0xKyafELBN0Boz0jepejfqbGnc google-site-verification=ykYa4IYRLZecJJksF_iSN7tL3wtT-jWcz_YJHxjPvEk v=spf1 +ip4:54.95.160.128 +ip4:52.199.89.136 +include:spf.mose-mail.jp ~all

Registrationregistrar not reported

registered	2007-11-07
expires	2026-11-30
last changed	2026-02-28
owner	(Not displayed by registrant's request)
nameservers	ns-887.awsdns-46.net ns-296.awsdns-37.com ns-2021.awsdns-60.co.uk ns-1391.awsdns-45.org
status	Active

registered 2007-11-07expires 2026-11-30

HTTPS certificate171 days left

valid	yes
issuer	Amazon
covers	dto.jp, s.dto.jp, www.dto.jp, rd.dto.jp, m.dto.jp
protocol	TLSv1.3

issued 2026-10-04expires 2027-04-19

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → dto.jp

Email authenticationpoor

SPF	pass `v=spf1 +ip4:54.95.160.128 +ip4:52.199.89.136 +include:spf.mose-mail.jp ~all`
DMARC	none
DKIM	none of 1 common selectors

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

Security scoregrade B · 145/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

15/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.111Barracuda3.170.42.111UCEPROTECT Level 13.170.42.111SpamCop3.170.42.105Barracuda3.170.42.105UCEPROTECT Level 13.170.42.105SpamCop3.170.42.119Barracuda3.170.42.119UCEPROTECT Level 13.170.42.119SpamCop3.170.42.30Barracuda3.170.42.30UCEPROTECT Level 13.170.42.30

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

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

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