How is battle.net?

Looks fine risk 0/100

Registered 31 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

128 d

left on a Amazon certificate

Age

31 years

registered 1996-03-26

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	166.117.214.166 166.117.114.163
MX	0 mxa-00381101.gslb.pphosted.com 0 mxb-00381101.gslb.pphosted.com
NS	ns-1467.awsdns-55.org ns-67.awsdns-08.com ns-599.awsdns-10.net ns-1578.awsdns-05.co.uk
TXT	FHtwAyldtP/7jq5sT93uP2GW7/yWbSKfgD2O/6VU1IwZMpWYTGOpGtjGDCj/JeKWYIJyS90KgprRKqgwLyHMoA== MS=ms91053870 _dr4xj90iri5q4rghrad0eg5v9ix04ux facebook-domain-verification=wr9qqtrkyp1jejv1xr8blfn6dpowbt google-site-verification=5BDURW3z5Ld2Mi_LkCm21d23wHRx9_hqokrh1C68duo google-site-verification=XMBo5g8gfzfd_6yHrk6AD2rMT_1RxWg6j44Zsyuy1yM v=spf1 include:spf1.battle.net include:spf2.battle.net include:spf3.battle.net include:spf4.battle.net include:spf5.battle.net include:spf6.battle.net include:spf7.battle.net -all

RegistrationMarkMonitor Inc.

registrar	MarkMonitor Inc.
registered	1996-03-26
expires	2031-03-27
last changed	2025-02-05
owner	REDACTED FOR PRIVACY
nameservers	ns-1467.awsdns-55.org ns-1578.awsdns-05.co.uk ns-599.awsdns-10.net ns-67.awsdns-08.com
status	client delete prohibited client transfer prohibited client update prohibited

registered 1996-03-26expires 2031-03-27

HTTPS certificate128 days left

valid	yes
issuer	Amazon
covers	battle.net, *.battle.net
protocol	TLSv1.2

issued 2026-08-21expires 2027-03-06

DNSSECinsecure

Domain is not signed with DNSSEC

. → net → battle.net

Email authenticationexcellent

SPF	pass `v=spf1 include:spf1.battle.net include:spf2.battle.net include:spf3.battle.net include:spf4.battle.net include:spf5.battle.net include:spf6.battle.net include:spf7.battle.net -all`
DMARC	pass policy reject
DKIM	found: default, mail

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 · 8 lookups

SURBL MultidomainURIBL MultidomainSpamCop166.117.114.163Barracuda166.117.114.163UCEPROTECT Level 1166.117.114.163SpamCop166.117.214.166Barracuda166.117.214.166UCEPROTECT Level 1166.117.214.166

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=battle.net" \ -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=battle.net"

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

Watch battle.net. 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