HOW.IS
?

How is oricon.co.jp?

Looks fine risk 0/100

Registered 20 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 497 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How oricon.co.jp looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
497 ms · ends at www.oricon.co.jp
HTTPS
19 d
left on a Cybertrust Japan Co., Ltd. certificate
Age
20 years
registered 2007-01-26
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records3 record types
A104.18.250.41
104.18.251.41
NSlily.ns.cloudflare.com
rommy.ns.cloudflare.com
TXTE2A6xnwPL84CDw2KqQ53mc1gqswpT6
_globalsign-domain-verification=-E_9vshoXtZLbT2RXzc-BvRaxt-UQQ6tMhU1QE8sLh
aeyescan-activation=72494a5065f6f1f4
facebook-domain-verification=1j20wyx203ppt2s3m1hsvf9ajxkhc8
google-site-verification=H7SvcKf2Fp1q-fVPDokKliW9kiZjHNpQPtN1Rre_rBU
google-site-verification=YrKCAGrDuIEhIRN5fRvwCyqVjI56f6Wh0XUdOd7by20
v=spf1 include:spf.oricon.jp ip4:13.113.104.249 ip4:18.176.12.4 ~all
Registrationregistrar not reported
registered2007-01-26
expires2027-01-31
last changed2026-02-01
ownerOricon Inc.
nameserverslily.ns.cloudflare.com
rommy.ns.cloudflare.com
statusConnected (2027/01/31)
registered 2007-01-26expires 2027-01-31
HTTPS certificate19 days left
validyes
issuerCybertrust Japan Co., Ltd.
covers*.oricon.co.jp, oricon.co.jp
protocolTLSv1.3
issued 2025-11-18expires 2026-11-17
DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → oricon.co.jp
Email authenticationfair
SPFpass v=spf1 include:spf.oricon.jp ip4:13.113.104.249 ip4:18.176.12.4 ~all
DMARCpass policy reject
DKIMnone of 1 common selectors

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

Security scoregrade B · 145/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
30/45missing: CAA Records, DKIM Presence
Advanced Security
10/25missing: Mail Server Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop104.18.250.41Barracuda104.18.250.41UCEPROTECT Level 1104.18.250.41SpamCop104.18.251.41Barracuda104.18.251.41UCEPROTECT Level 1104.18.251.41

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

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

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