odoo.com

Checked 22 October 2026, 10:05 UTC · via 8.8.8.8
!Passed with warnings
24 passed 4 warnings 0 failed 3 info

Registration

info

.com generic · OVH sas · expires 2034-01-25

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
OVH sas
Registered
25 January 2001
Last changed
26 May 2025
Expires
25 January 2034
Status
client delete prohibited, client transfer prohibited
Registry nameservers
ns0.odoo.com, ns1.odoo.com, ns2.odoo.com, ns3.odoo.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2034-01-25 #3
    The registration is valid until 2034-01-25 (2652 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns0.odoo.com, ns1.odoo.com, ns2.odoo.com, ns3.odoo.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns0.odoo.com, ns1.odoo.com, ns2.odoo.com, ns3.odoo.com
NS in the zone
ns0.odoo.com, ns1.odoo.com, ns2.odoo.com, ns3.odoo.com
NameserverAddressesNetwork (AS)Glue
ns0.odoo.com178.32.109.180 2001:41d0:34c:1200::AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR178.32.109.180
ns1.odoo.com51.91.164.65 2001:41d0:261:2700::AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR51.91.164.65
ns2.odoo.com35.205.186.208 2600:1900:4011:4e1:0:1::AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US35.205.186.208
ns3.odoo.com35.205.106.18 2600:1900:4011:4e1:0:2::AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US35.205.106.18

Checks

  • ✓ 4 nameservers #6
    Delegated to ns0.odoo.com, ns1.odoo.com, ns2.odoo.com, ns3.odoo.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns0.odoo.com (glue 178.32.109.180, zone 178.32.109.180, 2001:41d0:34c:1200::); ns1.odoo.com (glue 51.91.164.65, zone 51.91.164.65, 2001:41d0:261:2700::); ns2.odoo.com (glue 35.205.186.208, zone 35.205.186.208, 2600:1900:4011:4e1:0:1::); ns3.odoo.com (glue 35.205.106.18, zone 35.205.106.18, 2600:1900:4011:4e1:0:2::). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 4 addresses; AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US): 4 addresses.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.odoo.com 178.32.109.180NOERROR, 16 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns0.odoo.com 2001:41d0:34c:1200::NOERROR, 16 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns1.odoo.com 51.91.164.65NOERROR, 19 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns1.odoo.com 2001:41d0:261:2700::NOERROR, 19 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns2.odoo.com 35.205.186.208NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns2.odoo.com 2600:1900:4011:4e1:0:1::NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns3.odoo.com 35.205.106.18NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)
ns3.odoo.com 2600:1900:4011:4e1:0:2::NOERROR, 17 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0.odoo.com: "PowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)"; ns1.odoo.com: "PowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)"; ns2.odoo.com: "PowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)"; ns3.odoo.com: "PowerDNS Authoritative Server 4.9.5 (built May 7 2025 09:30:52 by root@localhost)". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2021050400 · primary ns3.odoo.com

Found

Primary (MNAME)
ns3.odoo.com
Contact (RNAME)
admin.odoo.com
Serial
2021050400
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns0.odoo.com (178.32.109.180)2021050400
ns0.odoo.com (2001:41d0:34c:1200::)2021050400
ns1.odoo.com (51.91.164.65)2021050400
ns1.odoo.com (2001:41d0:261:2700::)2021050400
ns2.odoo.com (35.205.186.208)2021050400
ns2.odoo.com (2600:1900:4011:4e1:0:1::)2021050400
ns3.odoo.com (35.205.106.18)2021050400
ns3.odoo.com (2600:1900:4011:4e1:0:2::)2021050400

Checks

  • ✓ Serial 2021050400 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.odoo.com is one of the listed nameservers.
  • ✓ Contact admin@odoo.com #25
    The SOA RNAME admin.odoo.com means admin@odoo.com.
  • ✓ Date-based serial #26
    The serial 2021050400 follows the YYYYMMDDnn convention (2021-05-04).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

20 records at the apex

Found

Read from
178.32.109.180:53
TypeValueTTL
SOAns3.odoo.com. admin.odoo.com. 2021050400 10800 3600 604800 3600600
NSns0.odoo.com.14400
NSns3.odoo.com.14400
NSns1.odoo.com.14400
NSns2.odoo.com.14400
A178.33.40.4360
AAAA2001:41d0:249:e200::60
MX10 mx1c.odoo.com.600
MX10 mx1d.odoo.com.600
TXT"google-site-verification=f43tnyyRm5QkCU9n53-tWjsYjPFoj1E6gE4-KiZx2cY"600
TXT"google-site-verification=pgjyH0qvN69B0m_HrTKV6h8TVnbRXp5etEHo19unPy4"600
TXT"google-site-verification=GTR7w9X5rUnftXj6VRMSaHzHvJd2AuIqlSBGouHTLcE"600
TXT"google-site-verification=iNBIN8rSHf6Q3LbzPsEqEztmMmsn-eGM5PW5KLakXNM"600
TXT"google-site-verification=HPrQ2HXxHN60Ev-JQ9yZ_6d1eOR_grkVFyGe8JHuzOg"600
TXT"v=spf1 include:_spf.odoo.com include:_spf.google.com ip4:5.135.141.8 -all"600
TXT"google-site-verification=WFR4flJwpLbDVn-63zHuEKfTJkWSI6cDqwd2uIFbgZ8"600
TXT"google-site-verification=V4lCmbjYG6Iobcm3fd4CTkdUeVaUShT_Ys48adxeLmI"600
CAA0 issuewild "letsencrypt.org"600
CAA0 iodef "mailto:abuse@odoo.com"600
CAA0 issue "letsencrypt.org"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 4h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.