chatbotgpt.fr

Checked 22 October 2026, 02:13 UTC · via 8.8.8.8
✗Problems found
8 passed 3 warnings 1 failed 4 info

Registration

info

.fr country-code · GANDI · expires 2029-01-12

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
GANDI
Registered
12 January 2023
Last changed
13 March 2026
Expires
12 January 2029
Status
client transfer prohibited
Registry nameservers
ns5.alexhost.md, ns6.alexhost.md
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 2029-01-12 #3
    The registration is valid until 2029-01-12 (813 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns5.alexhost.md, ns6.alexhost.md

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns5.alexhost.md, ns6.alexhost.md
NS in the zone
ns5.alexhost.md, ns6.alexhost.md
NameserverAddressesNetwork (AS)Glue
ns5.alexhost.md176.123.0.83AS200019 AlexHost - ALEXHOST SRL, MD-
ns6.alexhost.md176.123.0.84AS200019 AlexHost - ALEXHOST SRL, MD-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns5.alexhost.md, ns6.alexhost.md.
    #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.
  • !
    Nameservers in one network
    all IPv4 addresses are in 176.123.0.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 (AS200019 (AlexHost - ALEXHOST SRL, MD): 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 .md
    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

fail

0 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns5.alexhost.md 176.123.0.83no responsenono / no--
ns6.alexhost.md 176.123.0.84no responsenono / no--

Checks

  • ✗
    No nameserver responds
    None of the nameserver addresses answered: ns5.alexhost.md (176.123.0.83): read udp 46.225.38.91:55406->176.123.0.83:53: i/o timeout; ns6.alexhost.md (176.123.0.84): read udp 46.225.38.91:55453->176.123.0.84:53: i/o timeout.
    #14
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

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