blogclair.fr

Checked 22 October 2026, 01:57 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 failed 8 info

Registration

info

.fr country-code · NILYS · expires 2027-10-21

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NILYS
Registered
21 October 2026
Last changed
21 October 2026
Expires
21 October 2027
Status
active, add period
Registry nameservers
ns1.webexpire.com, ns2.webexpire.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-10-21 #3
    The registration is valid until 2027-10-21 (364 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active, add period). 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.webexpire.com, ns2.webexpire.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.webexpire.com, ns2.webexpire.com
NS in the zone
ns1.webexpire.com, ns2.webexpire.com
NameserverAddressesNetwork (AS)Glue
ns1.webexpire.com212.47.239.69 2001:bc8:710:2dcb:dc00:ff:fe37:f350AS12876 AS12876 - Scaleway SAS, FR AS12876 AS12876 - Scaleway SAS, FR-
ns2.webexpire.com51.159.157.89 2001:bc8:1210:e285:dc00:ff:fe5a:5ce0AS12876 AS12876 - Scaleway SAS, FR AS12876 AS12876 - Scaleway SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.webexpire.com, ns2.webexpire.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS12876 (AS12876 - Scaleway SAS, FR): 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.webexpire.com 212.47.239.69NOERROR, 20 ms, authoritativenoyes / yesrefused-
ns1.webexpire.com 2001:bc8:710:2dcb:dc00:ff:fe37:f350NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns2.webexpire.com 51.159.157.89NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns2.webexpire.com 2001:bc8:1210:e285:dc00:ff:fe5a:5ce0NOERROR, 18 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

warn

serial 2026102201 · primary ns1.webxpire.com

Found

Primary (MNAME)
ns1.webxpire.com
Contact (RNAME)
dns.webexpire.com
Serial
2026102201
Refresh / retry
14400 s / 4800 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.webexpire.com (212.47.239.69)2026102201
ns1.webexpire.com (2001:bc8:710:2dcb:dc00:ff:fe37:f350)2026102201
ns2.webexpire.com (51.159.157.89)2026102102
ns2.webexpire.com (2001:bc8:1210:e285:dc00:ff:fe5a:5ce0)2026102102

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2026102102 on ns2.webexpire.com (51.159.157.89), ns2.webexpire.com (2001:bc8:1210:e285:dc00:ff:fe5a:5ce0); 2026102201 on ns1.webexpire.com (212.47.239.69), ns1.webexpire.com (2001:bc8:710:2dcb:dc00:ff:fe37:f350). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 80m, expire 7d, negative TTL 3h.
  • i
    Hidden master (not resolvable)
    The primary nameserver ns1.webxpire.com is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact dns@webexpire.com #25
    The SOA RNAME dns.webexpire.com means dns@webexpire.com.
  • ✓ Date-based serial #26
    The serial 2026102201 follows the YYYYMMDDnn convention (2026-10-22).

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

4 records at the apex

Found

Read from
212.47.239.69:53
TypeValueTTL
SOAns1.webxpire.com. dns.webexpire.com. 2026102201 14400 4800 604800 1080086400
NSns2.webexpire.com.86400
NSns1.webexpire.com.86400
A212.129.27.1933600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ 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
  • 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