HOW.IS
?

How is dmm.co.jp?

Looks fine risk 0/100

Registered 20 years ago, on no blocklists we checked, valid HTTPS, the site did not answer (refused).

Why

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

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

Site
down
refused
HTTPS
146 d
left on a GlobalSign nv-sa certificate
Age
20 years
registered 2006-07-10
Blocklists
0
listings across 4 lists; 1 did not answer

Everything we looked at

DNS records4 record types
A13.248.196.236
MX10 swiss.dmm.co.jp
NSa18-66.akam.net
ns2.p201.dns.oraclecloud.net
a13-64.akam.net
a1-198.akam.net
a12-67.akam.net
ns4.p201.dns.oraclecloud.net
ns3.p201.dns.oraclecloud.net
a14-65.akam.net
a9-67.akam.net
ns1.p201.dns.oraclecloud.net
TXT_globalsign-domain-verification=UwJZ8E3mROVSTuvDs9HdYc_LVc1Qshym4hmdpTN8o3
v=spf1 ip4:203.209.144.0/20 ip4:202.6.244.0/22 ip4:103.254.144.0/22 ip4:157.112.88.58/32 include:cust-spf.exacttarget.com include:md93.maildealer.jp -all
google-site-verification=_Ci92-uIvOKSTOj3ddmCQL6F6C3Y6eJk4LE0G2HEzrE
google-site-verification=JtyOrlh0YaMUYl9bsrBknfQUdQWx4AUF9F53QhOHHSI
google-site-verification=J_DConcX7NP6-GoMx6i3zLb9FtVd6o96c_VjkAmXjfA
google-site-verification=0ckwE20OPaP5en5hOmGdeX4QY5sSm72N9D3twPrGa0o
google-site-verification=QkffC_LJoz60tqjWTUDwamUlzLvcHP5jOvTrKTX5Xp0
google-site-verification=1X3BJ3lM80OZt5pggJD1Rkygcg8-bNBxni9lrUas4dY
google-site-verification=woCIjqAdinOBUmubEGTcJ9_6xGNQSxB9gyGAejoo5lU
google-site-verification=gEWB9py1UwtAA52457BNxah-YeGF_jpiBx2dwIg_-c0
google-site-verification=qGTSGF6UUF0izRJGixvWd1UR4jhE2TzIe0ql08VyMXY
amazonses:qv0RaqRbY/aNsIUOzwskhSDBZI+nJPAFIC8zXRj84Zs=
Registrationregistrar not reported
registered2006-07-10
expires2027-07-31
last changed2026-08-01
ownerDMM.com LLC
nameserversa1-198.akam.net
a12-67.akam.net
a13-64.akam.net
a14-65.akam.net
a18-66.akam.net
a9-67.akam.net
ns1.p201.dns.oraclecloud.net
ns2.p201.dns.oraclecloud.net
ns3.p201.dns.oraclecloud.net
ns4.p201.dns.oraclecloud.net
statusConnected (2027/07/31)
registered 2006-07-10expires 2027-07-31
HTTPS certificate146 days left
validyes
issuerGlobalSign nv-sa
covers*.dmm.co.jp, dmm.co.jp
protocolTLSv1.2
issued 2026-02-20expires 2027-03-24
DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → dmm.co.jp
Email authenticationgood
SPFpass v=spf1 ip4:203.209.144.0/20 ip4:202.6.244.0/22 ip4:103.254.144.0/22 ip4:157.112.88.58/32 include:cust-spf.exacttarget.com include:md93.maildealer.jp -all
DMARCwarning policy none
DKIMfound: default

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 · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop13.248.196.236Barracuda13.248.196.236UCEPROTECT Level 113.248.196.236

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

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

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