How is max.com?

Looks fine risk 0/100

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

144 ms · ends at www.hbomax.com

HTTPS

179 d

left on a Amazon certificate

Age

34 years

registered 1992-12-01

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	3.170.42.98 3.170.42.80 3.170.42.103 3.170.42.101
MX	10 max-com.mail.protection.outlook.com
NS	ns-1909.awsdns-46.co.uk ns-1122.awsdns-12.org ns-6.awsdns-00.com ns-826.awsdns-39.net
TXT	google-site-verification=AVoBVpEVgI9a4FFMxuMKHTlhr8k3_df7t0nWNbvWl8s apple-domain-verification=g_9YVNSLKninNRJpEav4qR9C-qeazxSaaWiuLpmoE50 _globalsign-domain-verification=TG_tReQcFSQ3_F4B9OSSwBtArXawkYnttaFD5ioe4o _globalsign-domain-verification=C6c4WGpoKyQN_yv_cvHUUSZ8lVGe3fGQhhHt8l4D-X _globalsign-domain-verification=O9n-uJnURw52fIAfW3Df9r8iezGiOMHVT8RuF08Z5H _globalsign-domain-verification=TmgrLQYBEBhop2MxUx3tq7vCqEMEqAJgmXaTPr9MI2 v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all proxy-ssl.webflow.com _knhvvwqvv7dapz6px7n1ngb6420j4yo google-site-verification=RF7FJzsSrgXSOa3p291GfBDtil-69uIp6-xQRnrGhR4 cb9tnn00375fujif0suvr4ehud ms52949396 miro-verification=1e01f8da769be1241fceefd9abf2c317dcd68323 koqi8pptm473lkoi6msq0q9c80

RegistrationMarkMonitor Inc.

registrar	MarkMonitor Inc.
registered	1992-12-01
expires	2032-10-07
last changed	2023-06-28
owner	REDACTED FOR PRIVACY
nameservers	ns-1122.awsdns-12.org ns-1909.awsdns-46.co.uk ns-6.awsdns-00.com ns-826.awsdns-39.net
status	client delete prohibited client transfer prohibited client update prohibited server delete prohibited server transfer prohibited server update prohibited

registered 1992-12-01expires 2032-10-07

HTTPS certificate179 days left

valid	yes
issuer	Amazon
covers	max.com
protocol	TLSv1.3

issued 2026-10-13expires 2027-04-28

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → max.com

Email authenticationexcellent

SPF	pass `v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all`
DMARC	pass policy quarantine
DKIM	found: selector1

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

Security scoregrade B · 160/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

30/45missing: CAA Records, 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.98Barracuda3.170.42.98UCEPROTECT Level 13.170.42.98SpamCop3.170.42.80Barracuda3.170.42.80UCEPROTECT Level 13.170.42.80SpamCop3.170.42.103Barracuda3.170.42.103UCEPROTECT Level 13.170.42.103SpamCop3.170.42.101Barracuda3.170.42.101UCEPROTECT Level 13.170.42.101

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=max.com" \ -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=max.com"

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

IPv6. Does max.com work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

Watch max.com. 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