dhl.fr

Checked 22 October 2026, 02:33 UTC · via 8.8.8.8
!Passed with warnings
26 passed 2 warnings 0 failed 7 info

Registration

info

.fr country-code · KEY-SYSTEMS GmbH · expires 2027-04-29

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
KEY-SYSTEMS GmbH
Registered
21 December 1997
Last changed
21 April 2026
Expires
29 April 2027
Status
active
Registry nameservers
ns1.f5clouddns.com, ns2.f5clouddns.com
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr 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
    .fr is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-04-29 #3
    The registration is valid until 2027-04-29 (189 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.f5clouddns.com, ns2.f5clouddns.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.f5clouddns.com, ns2.f5clouddns.com
NS in the zone
ns1.f5clouddns.com, ns2.f5clouddns.com
NameserverAddressesNetwork (AS)Glue
ns1.f5clouddns.com107.162.234.197 2604:e180:1071::3:1AS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-
ns2.f5clouddns.com107.162.176.221 2604:e180:1071::ffff:6ba2:b0ddAS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.f5clouddns.com, ns2.f5clouddns.com.
    #6
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2604:e180:1071::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS55002 (DEFENSE-NET - F5, Inc., US): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.f5clouddns.com 107.162.234.197NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1.f5clouddns.com 2604:e180:1071::3:1NOERROR, 164 ms, authoritativenoyes / yesrefused-
ns2.f5clouddns.com 107.162.176.221NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.f5clouddns.com 2604:e180:1071::ffff:6ba2:b0ddNOERROR, 26 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2016112473 · primary ns1.f5clouddns.com

Found

Primary (MNAME)
ns1.f5clouddns.com
Contact (RNAME)
netmaster.dhl.com
Serial
2016112473
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.f5clouddns.com (107.162.234.197)2016112473
ns1.f5clouddns.com (2604:e180:1071::3:1)2016112473
ns2.f5clouddns.com (107.162.176.221)2016112473
ns2.f5clouddns.com (2604:e180:1071::ffff:6ba2:b0dd)2016112473

Checks

  • ✓ Serial 2016112473 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.f5clouddns.com is one of the listed nameservers.
  • ✓ Contact netmaster@dhl.com #25
    The SOA RNAME netmaster.dhl.com means netmaster@dhl.com.
  • ✓ Date-based serial #26
    The serial 2016112473 follows the YYYYMMDDnn convention (2016-11-24).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 8-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
18760RSASHA256 (8)SHA256 D67A41A216B72073…yes
4801RSASHA256 (8)SHA256 B5D93A34601CB244…yes

DNSKEY in the zone

Key tagRoleAlgorithm
62103ZSK (256)RSASHA256 (8)
7608ZSK (256)RSASHA256 (8)
18760KSK (257)RSASHA256 (8)
4801KSK (257)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 18760 (SHA256), key tag 4801 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • !
    Signatures expire soon
    The earliest signature expires at 2026-10-29 02:25 UTC (in 168h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 0 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

8 records at the apex

Found

Read from
107.162.234.197:53
TypeValueTTL
SOAns1.f5clouddns.com. netmaster.dhl.com. 2016112473 10800 3600 604800 60086400
NSns2.f5clouddns.com.3600
NSns1.f5clouddns.com.3600
A159.60.134.155300
MX10 smtp.jmsp.net.86400
TXT"globalsign-domain-verification=884CEA410B917F357816ED51BD44A638"3600
TXT"v=spf1 mx include:dpdhl._spf.dhl.com ip4:46.105.111.126 ip4:51.75.141.188 ip4:87.98.179.2 ip4:51.210.12.230 ip4:51.210.10.229 ip4:51.210.13.242 ip4:51.210.13.246 ~all"3600
TXT"_globalsign-domain-verification=9cBULT4hxT9p3D3WiW8nHOMfMq_SH9CcIaTpGOF2Px"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1d, NS 1h.
  • ✓ 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