HOW.IS
?

How is lichess.org?

Looks fine risk 0/100

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

Why

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

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

How lichess.org looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
173 ms
HTTPS
81 d
left on a Google Trust Services certificate
Age
16 years
registered 2010-06-14
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records6 record types
A104.20.23.26
172.66.163.69
AAAA2606:4700:10::6814:171a
2606:4700:10::ac42:a345
MX10 alt3.aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
1 aspmx.l.google.com
NSserenity.ns.cloudflare.com
dimitris.ns.cloudflare.com
TXTv=spf1 include:_spf.google.com include:_spf.tem.scaleway.com -all
google-site-verification=iHavQOc6X8aYmnHhfovb-1hseQ3bxT79YJiwhDzhoTo
google-site-verification=fZ08Imok7kcLaGcJg7BKQExO6vXGgSgsJUsW6JalUCo
google-site-verification=nTK9KGLK0Uk6ScCHMRZKQsh7UEFGc3f6NY1nQ2PuHHA
google-site-verification=lcne9sTo24rMZhlrGEXB3TtkTnnpZqH_hNo20DezQEc
CAA{'type': 'CAA', 'issue': 'pki.goog; cansignhttpexchanges=yes', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'}
{'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'comodoca.com'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'pki.goog; cansignhttpexchanges=yes'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'digicert.com; cansignhttpexchanges=yes'}
{'type': 'CAA', 'issue': 'ssl.com', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'ssl.com'}
{'type': 'CAA', 'issue': 'digicert.com; cansignhttpexchanges=yes', 'critical': 0}
{'type': 'CAA', 'issue': 'comodoca.com', 'critical': 0}
RegistrationOVH sas
registrarOVH sas
registered2010-06-14
expires2027-06-14
last changed2026-08-12
nameserversdimitris.ns.cloudflare.com
serenity.ns.cloudflare.com
statusclient delete prohibited
client transfer prohibited
registered 2010-06-14expires 2027-06-14
HTTPS certificate81 days left
validyes
issuerGoogle Trust Services
coverslichess.org, verify.lichess.org, *.verify.lichess.org
protocolTLSv1.3
issued 2026-10-21expires 2027-01-19
DNSSECsecure

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

. → org → lichess.org
Email authenticationgood
SPFpass v=spf1 include:_spf.google.com include:_spf.tem.scaleway.com -all
DMARCpass policy reject
DKIMnone of 1 common selectors

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 · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop104.20.23.26Barracuda104.20.23.26UCEPROTECT Level 1104.20.23.26SpamCop172.66.163.69Barracuda172.66.163.69UCEPROTECT Level 1172.66.163.69

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

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

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