chu-dijon.fr

Checked 22 October 2026, 02:16 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 6 info

Registration

info

.fr country-code · Orange Business Services SA, direction EOLAS · expires 2027-10-13

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Orange Business Services SA, direction EOLAS
Registered
22 July 1998
Last changed
2 October 2026
Expires
13 October 2027
Status
active
Registry nameservers
dns1.chu-dijon.fr, dns2.chu-dijon.fr
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-10-13 #3
    The registration is valid until 2027-10-13 (356 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

warn

dns1.chu-dijon.fr, dns2.chu-dijon.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
dns1.chu-dijon.fr, dns2.chu-dijon.fr
NS in the zone
dns1.chu-dijon.fr, dns2.chu-dijon.fr
NameserverAddressesNetwork (AS)Glue
dns1.chu-dijon.fr217.108.239.58AS3215 AS3215 - Orange S.A., FR217.108.239.58
dns2.chu-dijon.fr217.108.239.47AS3215 AS3215 - Orange S.A., FR217.108.239.47

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.chu-dijon.fr, dns2.chu-dijon.fr.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: dns1.chu-dijon.fr, dns2.chu-dijon.fr.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 217.108.239.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS3215 (AS3215 - Orange S.A., FR): 2 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 .fr
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.chu-dijon.fr 217.108.239.58NOERROR, 27 ms, authoritativenoyes / yesrefused-
dns2.chu-dijon.fr 217.108.239.47NOERROR, 27 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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 2026090701 · primary dns1.chu-dijon.fr

Found

Primary (MNAME)
dns1.chu-dijon.fr
Contact (RNAME)
postmaster.chu-dijon.fr
Serial
2026090701
Refresh / retry
5400 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.chu-dijon.fr (217.108.239.58)2026090701
dns2.chu-dijon.fr (217.108.239.47)2026090701

Checks

  • ✓ Serial 2026090701 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 90m, retry 1h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.chu-dijon.fr is one of the listed nameservers.
  • ✓ Contact postmaster@chu-dijon.fr #25
    The SOA RNAME postmaster.chu-dijon.fr means postmaster@chu-dijon.fr.
  • ✓ Date-based serial #26
    The serial 2026090701 follows the YYYYMMDDnn convention (2026-09-07).

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

12 records at the apex

Found

Read from
217.108.239.58:53
TypeValueTTL
SOAdns1.chu-dijon.fr. postmaster.chu-dijon.fr. 2026090701 5400 3600 1209600 36003600
NSdns2.chu-dijon.fr.3600
NSdns1.chu-dijon.fr.3600
A90.102.171.2063600
MX10 mail.cleanmail.eu.3600
TXT"9EUk0/mp4etEf3KfnWR2vqo89SMbMpg6y6PBj/0n4jH3Yn8OIOssdRVPBYVpjLZ9OPHEOMb1K6c4IzUgxvuAiw=="3600
TXT"LX0E0VpMgd05NXUDrK0mEHPdmQAdy48vNUbJ8xodRS8="3600
TXT"google-site-verification=AtlfDumz84LMvcTgClYp19E-cuc1ufznxDEedAkB_3g"3600
TXT"L/IfV46Q7SRzZj7cRRIuW+4XQnaKb+LlaJKElV+gaS/5i+6/Me8kc5wOCNXAXJTBMejh1lAKhZh6mckqccJSLw=="3600
TXT"v=spf1 mx include:spf.protection.outlook.com include:spfa.alinto.net ip4:217.108.239.45 ip4:217.108.239.57 ip4:217.108.239.46 -all"3600
TXT"MS=ms17851978"3600
TXT"globalsign-domain-verification=_-U-_35fjIytCpCBDIqRpvSkSAGZUnQ9SXkHOOLFXk"3600

Checks

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