How is firefox.com?

Looks fine risk 0/100

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

314 ms · ends at www.firefox.com

HTTPS

41 d

left on a Let's Encrypt certificate

Age

28 years

registered 1998-10-06

Blocklists

listings across 5 lists

Everything we looked at

DNS records6 record types

A	35.190.14.201
AAAA	2600:1901:0:c197::
MX	1 smtp.google.com
NS	ns1-240.akam.net ns5-65.akam.net ns7-66.akam.net ns4-64.akam.net
TXT	v=spf1 mx a include:amazonses.com include:mail.zendesk.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email -all kr1887r7cjn94rzlgp1bpnj8v94wd3mg _vrrc3v9222jxd6yhvt728lc4om6z0ff google-site-verification=NZ6YuiV9PaFX7rWqXJZxDpunitn7M8mtlnoaN2Z8Dcs facebook-domain-verification=wcer1w80xkwrzqftwc3shhkel9ys8m google-site-verification=ZqFMUZ8Gzf13U_nchwvBgRE_sRAxAR5xLz-X5w4BU4s google-gws-recovery-domain-verification=70476672 3mjnbdj3h9wpslgz0gfly0pbr94wd12y
CAA	{'type': 'CAA', 'issue': 'amazontrust.com', 'critical': 128} {'type': 'CAA', 'issue': 'amazonaws.com', 'critical': 128} {'type': 'CAA', 'iodef': 'mailto:foxsec+caaiodef@mozilla.com', 'critical': 128} {'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 128} {'type': 'CAA', 'issue': 'awstrust.com', 'critical': 128} {'type': 'CAA', 'issue': 'digicert.com', 'critical': 128} {'type': 'CAA', 'issue': 'amazon.com', 'critical': 128}

RegistrationMarkMonitor Inc.

registrar	MarkMonitor Inc.
registered	1998-10-06
expires	2028-10-05
last changed	2026-09-11
owner	Mozilla Corporation
nameservers	ns1-240.akam.net ns4-64.akam.net ns5-65.akam.net ns7-66.akam.net
status	client delete prohibited client transfer prohibited client update prohibited server delete prohibited server transfer prohibited server update prohibited

registered 1998-10-06expires 2028-10-05

HTTPS certificate41 days left

valid	yes
issuer	Let's Encrypt
covers	firefox.com
protocol	TLSv1.3

issued 2026-09-08expires 2026-12-07

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → firefox.com

Email authenticationgood

SPF	pass `v=spf1 mx a include:amazonses.com include:mail.zendesk.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email -all`
DMARC	pass policy reject
DKIM	none of 1 common selectors

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

Security scoregrade B · 165/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

45/45missing: DKIM Presence

Advanced Security

15/25missing: Mail Server Configuration, SOA Record Configuration

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop35.190.14.201Barracuda35.190.14.201UCEPROTECT Level 135.190.14.201

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

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

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