How is nginx.com?

Looks fine risk 0/100

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

308 ms · ends at www.f5.com

HTTPS

32 d

left on a Let's Encrypt certificate

Age

22 years

registered 2004-12-23

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	159.60.134.0
MX	10 mx1.hc5801-97.iphmx.com 10 mx2.hc5801-97.iphmx.com
NS	ns2.f5clouddns.com ns1.f5clouddns.com
TXT	atlassian-domain-verification=Iv/Cm1UielF25k9FOYOH+QWS9iqMJUFKzUNVB9RqH3uwzIEPziCRKryf2/dKbws8 citrix-verification-code=7e4cb6c1-154c-48ed-bdfa-65d310d86ec1 google-site-verification=m76lJj_wpFCOdcQ91QngVK7pk83_xTMtIp9m0Vi8qjQ dropbox-domain-verification=gl56nwvh4szl docusign=ec7fb56d-ee75-4979-b3e5-10bfbff0ab9e v=spf1 ip4:104.219.104.14 ip4:104.219.105.14 ip4:104.219.106.14 ip4:104.219.107.14 include:spf.protection.outlook.com exists:%{i}.spf.hc5801-97.iphmx.com ~all libera-verification=libera-RDmNyEJHyhbWgEZwNf3L9fUN google-site-verification=JrwNJWq0sLGx6H5Voxu-bQyH6-Fj6ifMzyNzIppraFc MS=ms49391549 google-site-verification=uUuJd81gBFhTSzGpOtmzRFJndx0uHcICLcicMmjP_eQ google-site-verification=Q2uo9nRIztLd374gimJdAb-Bfkw-MdywUFjH59AAkeE

RegistrationCSC Corporate Domains, Inc.

registrar	CSC Corporate Domains, Inc.
registered	2004-12-23
expires	2026-12-23
last changed	2025-12-19
owner	F5, Inc.
nameservers	ns1.f5clouddns.com ns2.f5clouddns.com
status	client transfer prohibited

registered 2004-12-23expires 2026-12-23

HTTPS certificate32 days left

valid	yes
issuer	Let's Encrypt
covers	*.nginx.com, nginx.com
protocol	TLSv1.3

issued 2026-08-29expires 2026-11-27

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → nginx.com

Email authenticationexcellent

SPF	pass `v=spf1 ip4:104.219.104.14 ip4:104.219.105.14 ip4:104.219.106.14 ip4:104.219.107.14 include:spf.protection.outlook.com exists:%{i}.spf.hc5801-97.iphmx.com ~all`
DMARC	pass policy reject
DKIM	found: selector1, selector2

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

SURBL MultidomainURIBL MultidomainSpamCop159.60.134.0Barracuda159.60.134.0UCEPROTECT Level 1159.60.134.0

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

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

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