HOW.IS
?

How is openssl.org?

Looks fine risk 0/100

Registered 28 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 228 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How openssl.org looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
228 ms
HTTPS
70 d
left on a Let's Encrypt certificate
Age
28 years
registered 1998-12-19
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records6 record types
A34.49.79.89
AAAA2600:1901:0:d50b::
MX10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
NSns-cloud-b3.googledomains.com
ns-cloud-b4.googledomains.com
ns-cloud-b1.googledomains.com
ns-cloud-b2.googledomains.com
TXTbw=8FWhDisk9A5pIZaRqgEVlw9bmNX2JfRXqrMEIQ7H3LDq
google-site-verification=UcenFo8BSxiqYnF3VG-WR2sRg5sA6_rqD95uHRd1XCQ
v=spf1 include:_spf.mailgun.org include:_spf.google.com include:spf.ourmailsender.com include:mail.zendesk.com include:amazonses.com mx:openssl.org -all
google-site-verification=gSC0oSoa_ORUbibpFTgJOzjCiSO1RbQvSLAFNf_Rlyc
MS=ms30329591
anthropic-domain-verification-aak9cc=zhKPG1Uo7ZmC2C0SRXdTupz4B
google-site-verification=Vfn-VvIAKa3dsUvBlPcoj9Fs9n4vjWvTNRblV_fqJJY
openai-domain-verification=dv-yMgwPMed7LsPUgnVC7wKD1yQ
CAA{'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0}
{'type': 'CAA', 'iodef': 'mailto:sec@openssl.org', 'critical': 0}
RegistrationGandi SAS
registrarGandi SAS
registered1998-12-19
expires2032-12-19
last changed2026-10-16
ownerOpenSSL Software Foundation Inc.
nameserversns-cloud-b1.googledomains.com
ns-cloud-b4.googledomains.com
ns-cloud-b2.googledomains.com
ns-cloud-b3.googledomains.com
statusclient transfer prohibited
registered 1998-12-19expires 2032-12-19
HTTPS certificate70 days left
validyes
issuerLet's Encrypt
coversopenssl.org, www.openssl.org
protocolTLSv1.3
issued 2026-10-14expires 2027-01-12
DNSSECsecure

Domain is properly signed — chain validated by an independent validating resolver

. → org → openssl.org
Email authenticationexcellent
SPFpass v=spf1 include:_spf.mailgun.org include:_spf.google.com include:spf.ourmailsender.com include:mail.zendesk.com include:amazonses.com mx:openssl.org -all
DMARCpass policy quarantine
DKIMfound: google

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

Security scoregrade A · 175/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
45/45missing: DKIM Presence
Advanced Security
25/25
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop34.49.79.89Barracuda34.49.79.89UCEPROTECT Level 134.49.79.89

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

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

IPv6. IPv6 readiness grade for openssl.org Does openssl.org work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

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