peugeot.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

ns-240-c.gandi.net, ns-42-b.gandi.net, ns-49-a.gandi.net, z.dns.gandi.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns-240-c.gandi.net, ns-42-b.gandi.net, ns-49-a.gandi.net, z.dns.gandi.net
NS in the zone
ns-240-c.gandi.net, ns-42-b.gandi.net, ns-49-a.gandi.net, z.dns.gandi.net
NameserverAddressesNetwork (AS)Glue
ns-240-c.gandi.net217.70.187.241 2604:3400:aaac::f1AS29169 GANDI-AS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-42-b.gandi.net213.167.230.43 2001:4b98:aaab::2bAS29169 GANDI-AS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-49-a.gandi.net173.246.100.50 2001:4b98:aaaa::32AS209453 GANDI-LIVEDNS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
z.dns.gandi.net162.159.24.51 162.159.25.250 2400:cb00:2049:1::a29f:19fa 2400:cb00:2049:1::a29f:1833AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns-240-c.gandi.net, ns-42-b.gandi.net, ns-49-a.gandi.net, z.dns.gandi.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ 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 5 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 4 addresses; AS209453 (GANDI-LIVEDNS - GANDI SAS, FR): 4 addresses; AS29169 (GANDI-AS - GANDI SAS, FR): 2 addresses.
  • i
    All nameserver names under .net
    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

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-240-c.gandi.net 217.70.187.241NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-240-c.gandi.net 2604:3400:aaac::f1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-42-b.gandi.net 213.167.230.43NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-42-b.gandi.net 2001:4b98:aaab::2bNOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-49-a.gandi.net 173.246.100.50NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-49-a.gandi.net 2001:4b98:aaaa::32NOERROR, 3 ms, authoritativenoyes / yesrefused-
z.dns.gandi.net 162.159.24.51NOERROR, 31 ms, authoritativenoyes / yesrefused2026.10.8
z.dns.gandi.net 162.159.25.250NOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.8
z.dns.gandi.net 2400:cb00:2049:1::a29f:19faNOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.8
z.dns.gandi.net 2400:cb00:2049:1::a29f:1833NOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 10 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: z.dns.gandi.net: "2026.10.8". 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

info

serial 1792022400 · primary ns1.gandi.net

Found

Primary (MNAME)
ns1.gandi.net
Contact (RNAME)
hostmaster.gandi.net
Serial
1792022400
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns-240-c.gandi.net (217.70.187.241)1792022400
ns-240-c.gandi.net (2604:3400:aaac::f1)1792022400
ns-42-b.gandi.net (213.167.230.43)1792022400
ns-42-b.gandi.net (2001:4b98:aaab::2b)1792022400
ns-49-a.gandi.net (173.246.100.50)1792022400
ns-49-a.gandi.net (2001:4b98:aaaa::32)1792022400
z.dns.gandi.net (162.159.24.51)1792022400
z.dns.gandi.net (162.159.25.250)1792022400
z.dns.gandi.net (2400:cb00:2049:1::a29f:19fa)1792022400
z.dns.gandi.net (2400:cb00:2049:1::a29f:1833)1792022400

Checks

  • ✓ Serial 1792022400 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • i
    Hidden master
    The primary nameserver ns1.gandi.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@gandi.net #25
    The SOA RNAME hostmaster.gandi.net means hostmaster@gandi.net.
  • ✓ Timestamp serial #26
    The serial 1792022400 is a Unix timestamp (2026-10-15 00:00 UTC).

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

info

10 records at the apex

Found

Read from
217.70.187.241:53
TypeValueTTL
SOAns1.gandi.net. hostmaster.gandi.net. 1792022400 10800 3600 604800 1080010800
NSz.dns.gandi.net.86400
NSns-240-c.gandi.net.86400
NSns-49-a.gandi.net.86400
NSns-42-b.gandi.net.86400
A217.70.184.5586400
MX10 mail.peugeot.de.86400
TXT"google-site-verification=yL9VWD11K-HWnBndbYSME3DspsyWn52ZB95nlw43iAc"10800
TXT"v=spf1 a mx include:e.digitalsquad-autobiz.com -all"10800
TXT"_xqkcc9kihgjryjl5p5fztz6pvfm4dds"10800

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, NS 1d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35