pepites-en-champagne.fr

Checked 22 October 2026, 04:45 UTC · via 8.8.8.8
!Passed with warnings
24 passed 1 warning 0 failed 6 info

Registration

info

.fr country-code · NETIM · expires 2027-09-28

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NETIM
Registered
8 October 2021
Last changed
25 September 2026
Expires
28 September 2027
Status
active
Registry nameservers
ns1.netim.net, ns2.netim.net, ns3.netim.net
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-09-28 #3
    The registration is valid until 2027-09-28 (341 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.netim.net, ns2.netim.net, ns3.netim.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.netim.net, ns2.netim.net, ns3.netim.net
NS in the zone
ns1.netim.net, ns2.netim.net, ns3.netim.net
NameserverAddressesNetwork (AS)Glue
ns1.netim.net198.50.216.33AS16276 OVH - OVH SAS, FR-
ns2.netim.net192.174.68.97 2001:67c:1bc::97AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns3.netim.net176.97.158.97 2001:67c:10b8::97AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.netim.net, ns2.netim.net, ns3.netim.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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.netim.net.
    #13

Nameservers

info

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.netim.net 198.50.216.33NOERROR, 105 ms, authoritativenoyes / yesrefused-
ns2.netim.net 192.174.68.97NOERROR, 7 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.netim.net 2001:67c:1bc::97NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns3.netim.net 176.97.158.97NOERROR, 19 ms, authoritativenoyes / yesrefusedreg-wie1
ns3.netim.net 2001:67c:10b8::97NOERROR, 16 ms, authoritativenoyes / yesrefusedreg-wie1

Checks

  • ✓ All respond #14
    All 5 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns2.netim.net: "RcodeZero DNS"; ns3.netim.net: "reg-wie1".
    #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

pass

serial 2601200025 · primary ns1.netim.net

Found

Primary (MNAME)
ns1.netim.net
Contact (RNAME)
hostmaster.netim.net
Serial
2601200025
Refresh / retry
10800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.netim.net (198.50.216.33)2601200025
ns2.netim.net (192.174.68.97)2601200025
ns2.netim.net (2001:67c:1bc::97)2601200025
ns3.netim.net (176.97.158.97)2601200025
ns3.netim.net (2001:67c:10b8::97)2601200025

Checks

  • ✓ Serial 2601200025 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.netim.net is one of the listed nameservers.
  • ✓ Contact hostmaster@netim.net #25
    The SOA RNAME hostmaster.netim.net means hostmaster@netim.net.
  • ✓ Timestamp serial #26
    The serial 2601200025 is a Unix timestamp (2052-06-05 11:33 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

12 records at the apex

Found

Read from
198.50.216.33:53
TypeValueTTL
SOAns1.netim.net. hostmaster.netim.net. 2601200025 10800 7200 604800 8640086400
NSns3.netim.net.86400
NSns1.netim.net.86400
NSns2.netim.net.86400
A216.150.1.186400
MX5 alt2.aspmx.l.google.com.86400
MX10 alt4.aspmx.l.google.com.86400
MX5 alt1.aspmx.l.google.com.86400
MX1 aspmx.l.google.com.86400
MX10 alt3.aspmx.l.google.com.86400
TXT"brevo-code:b851786d88ee9b0ead973799e0e9e362"86400
TXT"pinterest-site-verification=6c3058c83a7947b8128f88c2a326418e"86400

Checks

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