How is ameblo.jp?

Looks fine risk 0/100

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

274 ms

HTTPS

111 d

left on a DigiCert Inc certificate

Age

22 years

registered 2004-07-30

Blocklists

listings across 5 lists

Everything we looked at

DNS records5 record types

A	199.232.210.133 199.232.214.133
MX	10 mail.ameblo.jp
NS	ns-124.awsdns-15.com ns-2038.awsdns-62.co.uk ns-863.awsdns-43.net ns-1218.awsdns-24.org
TXT	cPu1ZpFdt7xvQjanmhmE12k4AmF0MH _mnobpm3nakzeekpqy6i72p451qgv326 google-site-verification=26Ps67bWgQGjeNkTT6hV9VEgczhnzjN78yCdM33v-eo UHgEILc96z9sKmvYTwgZYiwusQbyqI tollbit-domain-verification=e5f400b7a9ee16a9c039d5a7c1ca7587cf4d1c4708b2193bfa9778f5ed1c8d42 google-site-verification=fst_3JQsVLfa2f0Df-x-KdG2tW23U3jDz09k6iF__y8 fastly-domain-delegation-nfkcslan-542735-2022-10-31 fastly-domain-delegation-@X7yV19EoO6Y-2023-06-30 _gmqf0w3hsh1pqlogfw1gkg05zhs88zx v=spf1 ip4:216.255.232.136/32 include:spf-a.ameba.jp include:spf.repica.jp -all
CAA	{'type': 'CAA', 'iodef': 'mailto:ameba_tools+crt@cyberagent.co.jp', 'critical': 0} {'type': 'CAA', 'issue': 'digicert.com; cansignhttpexchanges=yes', 'critical': 0} {'type': 'CAA', 'issue': 'certainly.com', 'critical': 0} {'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0} {'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0} {'type': 'CAA', 'issue': 'amazon.com', 'critical': 0} {'type': 'CAA', 'issue': 'cybertrust.ne.jp', 'critical': 0}

Registrationregistrar not reported

registered	2004-07-30
expires	2027-07-31
last changed	2026-08-01
owner	Atsushi Tanaka
nameservers	ns-1218.awsdns-24.org ns-124.awsdns-15.com ns-863.awsdns-43.net ns-2038.awsdns-62.co.uk
status	Active

registered 2004-07-30expires 2027-07-31

HTTPS certificate111 days left

valid	yes
issuer	DigiCert Inc
covers	*.ameblo.jp, ameblo.jp
protocol	TLSv1.2

issued 2026-08-03expires 2027-02-16

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → ameblo.jp

Email authenticationfair

SPF	pass `v=spf1 ip4:216.255.232.136/32 include:spf-a.ameba.jp include:spf.repica.jp -all`
DMARC	warning policy none
DKIM	none of 20 common selectors

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

Security scoregrade B · 168/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

38/45missing: 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 · 8 lookups

SURBL MultidomainURIBL MultidomainSpamCop199.232.210.133Barracuda199.232.210.133UCEPROTECT Level 1199.232.210.133SpamCop199.232.214.133Barracuda199.232.214.133UCEPROTECT Level 1199.232.214.133

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

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

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