How is name.com?

Looks fine risk 0/100

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

113 ms · ends at www.name.com

HTTPS

64 d

left on a Google Trust Services certificate

Age

32 years

registered 1995-01-03

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	104.18.7.161 104.18.6.161
MX	20 alt1.aspmx.l.google.com 50 aspmx3.googlemail.com 10 aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com
NS	woz.ns.cloudflare.com margaret.ns.cloudflare.com
TXT	facebook-domain-verification=gkoxjnojf89tvcpephv0kmeai0q9hq google-site-verification=PC0_s7ErYVgSsXUWoHs9zdNlj52_Gz3gr5q7LWTkb2E loaderio=2f3e4512b319ad0026b17185b28ea643 knowbe4-site-verification=63516d66c856ac4db2780d4aec2619ff MS=ms63383492 google-site-verification=lT7aSug60y6uo_OmvFZ9jyHOQGAezVQEqLz9eTq6qyI rovag_verification_token=9A43BC298FFD461EB9A14870C04D35EF cursor-domain-verification-30gr58=u26KeE9rTGmfvUWx5lyqgeIsU anthropic-domain-verification-pnnte9=5UKGNpIs8VM2QFbHjQ2lXG95q status-page-domain-verification=k83rtsjgwgcs klaviyo-site-verification=QSGSkJ v=spf1 include:_spf.name.com include:_spf.google.com include:servers.mcsv.net include:amazonses.com include:mail.zendesk.com include:stspg-customer.com -all atlassian-domain-verification=DI3WvFuf0XVPlefxIHfOH/7Y5tq153xMhKf40oINQUVQj0GKu55ZmPua5W5Ee1Va

RegistrationName.com, Inc.

registrar	Name.com, Inc.
registered	1995-01-03
expires	2032-11-04
last changed	2023-08-29
owner	Domain Protection Services, Inc.
nameservers	margaret.ns.cloudflare.com woz.ns.cloudflare.com
status	client transfer prohibited server delete prohibited server transfer prohibited server update prohibited transfer prohibited delete prohibited update prohibited

registered 1995-01-03expires 2032-11-04

HTTPS certificate64 days left

valid	yes
issuer	Google Trust Services
covers	name.com, *.name.com, api.dev.name.com
protocol	TLSv1.3

issued 2026-09-30expires 2026-12-29

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → name.com

Email authenticationexcellent

SPF	pass `v=spf1 include:_spf.name.com include:_spf.google.com include:servers.mcsv.net include:amazonses.com include:mail.zendesk.com include:stspg-customer.com -all`
DMARC	pass policy quarantine
DKIM	found: default, google, k1

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

Security scoregrade B · 155/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

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 MultidomainSpamCop104.18.7.161Barracuda104.18.7.161UCEPROTECT Level 1104.18.7.161SpamCop104.18.6.161Barracuda104.18.6.161UCEPROTECT Level 1104.18.6.161

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

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

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