HOW.IS
?

How is who.int?

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.

How who.int looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
314 ms · ends at www.who.int
HTTPS
62 d
left on a Google Trust Services certificate
Age
28 years
registered 1998-06-05
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A192.133.11.1
MX10 who-int.mail.protection.outlook.com
NSwhqdns3.who.int
whqdns2.who.int
whqdns1.who.int
ext-dns-2.cern.ch
ns1.wpro.who.int
TXTZOOM_verify_bTI318yfSumXtVIVnfEdzQ
kfjFGux2GvIgH+XwWJgA8YLNiX6Jc9lZEtHz+2cfDoLo4cB03zeofnNz9eioELQriSHy0S6EuDQyrFY6DuoFqA==
plausible-sso-verification=4a284955-853c-4175-8f58-11542690cae7
MS=ms38766037
apple-domain-verification=cYOp0B6FuXeoDFAX
v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int -all
google-gws-recovery-domain-verification=44731192
atlassian-sending-domain-verification=31e3711a-2a4c-4ec1-bc7a-83c2d4137226
atlassian-domain-verification=UxKawy8Zm9aw6Yg8NrPBUbu9anpgfXtL2NS3L7DNt0MGYKfhw/WOXGuRCTcQMKqi
docusign=c346709c-41f2-43fd-8a5a-cf7992d6e560
docusign=9f72d1bd-efd7-4a97-b385-83d687978e8d
ca3-5fc9c6c655cf481e9d53b30866a6e690
zoho-verification=zb18164630.zmverify.zoho.eu
ciscocidomainverification=17f32bae2ea200dbca5879cd0dc89294b7e78220da17554d099fed05e3f7e8f4
CAA{'type': 'CAA', 'issue': 'awstrust.com', 'critical': 0}
{'type': 'CAA', 'issue': 'godaddy.com', 'critical': 0}
{'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'sectigo.com'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'}
{'type': 'CAA', 'issue': 'digicert.com', 'critical': 0}
{'type': 'CAA', 'issue': 'sectigo.com', 'critical': 0}
{'type': 'CAA', 'issue': 'pki.goog', 'critical': 0}
Registrationregistrar not reported
registered1998-06-05
last changed2020-12-10
nameserverswhqdns1.who.int
whqdns2.who.int
whqdns3.who.int
ext-dns-2.cern.ch
ns1.wpro.who.int
statusactive
HTTPS certificate62 days left
validyes
issuerGoogle Trust Services
coverswho.int
protocolTLSv1.3
issued 2026-09-28expires 2026-12-27
DNSSECinsecure

Domain is not signed with DNSSEC

. → int → who.int
Email authenticationexcellent
SPFpass v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int -all
DMARCpass policy reject
DKIMfound: selector1

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

Security scoregrade A · 175/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
45/45missing: DKIM Presence
Advanced Security
15/25missing: Mail Server Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop192.133.11.1Barracuda192.133.11.1UCEPROTECT Level 1192.133.11.1

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=who.int" \ -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=who.int"

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

Watch who.int. 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