HOW.IS
?

How is odoo.com?

Looks fine risk 0/100

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

Why

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

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

How odoo.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
879 ms · ends at www.odoo.com
HTTPS
57 d
left on a Let's Encrypt certificate
Age
26 years
registered 2001-01-25
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records6 record types
A178.33.40.43
AAAA2001:41d0:249:e200::
MX10 mx1d.odoo.com
10 mx1c.odoo.com
NSns3.odoo.com
ns2.odoo.com
ns1.odoo.com
ns0.odoo.com
TXTgoogle-site-verification=f43tnyyRm5QkCU9n53-tWjsYjPFoj1E6gE4-KiZx2cY
google-site-verification=iNBIN8rSHf6Q3LbzPsEqEztmMmsn-eGM5PW5KLakXNM
v=spf1 include:_spf.odoo.com include:_spf.google.com ip4:5.135.141.8 -all
google-site-verification=pgjyH0qvN69B0m_HrTKV6h8TVnbRXp5etEHo19unPy4
google-site-verification=HPrQ2HXxHN60Ev-JQ9yZ_6d1eOR_grkVFyGe8JHuzOg
google-site-verification=V4lCmbjYG6Iobcm3fd4CTkdUeVaUShT_Ys48adxeLmI
google-site-verification=GTR7w9X5rUnftXj6VRMSaHzHvJd2AuIqlSBGouHTLcE
google-site-verification=WFR4flJwpLbDVn-63zHuEKfTJkWSI6cDqwd2uIFbgZ8
CAA{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'}
{'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0}
{'type': 'CAA', 'iodef': 'mailto:abuse@odoo.com', 'critical': 0}
RegistrationOVH sas
registrarOVH sas
registered2001-01-25
expires2034-01-25
last changed2025-05-26
nameserversns0.odoo.com
ns1.odoo.com
ns2.odoo.com
ns3.odoo.com
statusclient delete prohibited
client transfer prohibited
registered 2001-01-25expires 2034-01-25
HTTPS certificate57 days left
validyes
issuerLet's Encrypt
covers*.odoo.com, odoo.com
protocolTLSv1.3
issued 2026-09-25expires 2026-12-24
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → odoo.com
Email authenticationexcellent
SPFpass v=spf1 include:_spf.odoo.com include:_spf.google.com ip4:5.135.141.8 -all
DMARCpass policy reject
DKIMfound: google, k1, mail

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 MultidomainSpamCop178.33.40.43Barracuda178.33.40.43UCEPROTECT Level 1178.33.40.43

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

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

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