How is jw.org?

Looks fine risk 0/100

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

130 ms · ends at www.jw.org

HTTPS

179 d

left on a Amazon certificate

Age

28 years

registered 1999-03-06

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	18.160.41.121 18.160.41.16 18.160.41.83 18.160.41.17
MX	10 jw-org.mail.protection.outlook.com
NS	ns-225.awsdns-28.com ns-1737.awsdns-25.co.uk ns-1359.awsdns-41.org ns-708.awsdns-24.net
TXT	MS=ms23705115 YXp1cmVfY29tbW9uX2V1 anthropic-domain-verification-em0drp=kxSo8NpzrChNZtJZx13kHveLw apple-domain-verification=hVUAuSxbkmfyIFha atlassian-domain-verification=xmemxsICHOzzpAl9cRUynt7Q8AQgCRK9CziljXGebyUiGXQ0eKs5MBTbZTeKTxMj autodesk-domain-verification=ekVy6b77OWWD_jLpSN_W google-site-verification=VOTmlP16IwfryxkH6xdOAUnvqIS56bw0QoBxIJEXXu0 openai-domain-verification=dv-LaFTiezHlKKaovifHVxfMcTG v=spf1 include:sendgrid.net include:spf.protection.outlook.com ip4:208.74.140.78 ip4:91.220.88.6 ip4:20.42.36.97 include:amazonses.com -all

RegistrationAmazon Registrar, Inc.

registrar	Amazon Registrar, Inc.
registered	1999-03-06
expires	2027-03-06
last changed	2026-08-12
owner	c/o whoisproxy.com
nameservers	ns-1359.awsdns-41.org ns-1737.awsdns-25.co.uk ns-225.awsdns-28.com ns-708.awsdns-24.net
status	client transfer prohibited

registered 1999-03-06expires 2027-03-06

HTTPS certificate179 days left

valid	yes
issuer	Amazon
covers	jw.org
protocol	TLSv1.3

issued 2026-10-11expires 2027-04-26

DNSSECinsecure

Domain is not signed with DNSSEC

. → org → jw.org

Email authenticationexcellent

SPF	pass `v=spf1 include:sendgrid.net include:spf.protection.outlook.com ip4:208.74.140.78 ip4:91.220.88.6 ip4:20.42.36.97 include:amazonses.com -all`
DMARC	pass policy reject
DKIM	found: selector1, selector2, s1, s2

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 MultidomainSpamCop18.160.41.121Barracuda18.160.41.121UCEPROTECT Level 118.160.41.121SpamCop18.160.41.17Barracuda18.160.41.17UCEPROTECT Level 118.160.41.17SpamCop18.160.41.16Barracuda18.160.41.16UCEPROTECT Level 118.160.41.16SpamCop18.160.41.83Barracuda18.160.41.83UCEPROTECT Level 118.160.41.83

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=jw.org" \ -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=jw.org"

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

Watch jw.org. 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