ille-et-vilaine.fr

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

Registration

info

.fr country-code · NAMEBAY · expires 2027-07-19

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NAMEBAY
Registered
16 December 2002
Last changed
18 July 2026
Expires
19 July 2027
Status
active
Registry nameservers
ns1.over-link.net, ns2.over-link.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-07-19 #3
    The registration is valid until 2027-07-19 (270 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

ns1.over-link.net, ns2.over-link.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.over-link.net, ns2.over-link.net
NS in the zone
ns1.over-link.net, ns2.over-link.net
NameserverAddressesNetwork (AS)Glue
ns1.over-link.net91.209.154.3AS48426 OVER-LINK - _OVER-LINK_ s.a.s., FR-
ns2.over-link.net46.183.49.20AS48426 OVER-LINK - _OVER-LINK_ s.a.s., FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.over-link.net, ns2.over-link.net.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS48426 (OVER-LINK - _OVER-LINK_ s.a.s., 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 .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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.over-link.net 91.209.154.3NOERROR, 28 ms, authoritativenoyes / yesrefused9.11.5-P4-5.1+deb10u11-Debian
ns2.over-link.net 46.183.49.20NOERROR, 14 ms, authoritativenoyes / yesrefused9.9.5-9+deb8u19-Debian

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.over-link.net: "9.11.5-P4-5.1+deb10u11-Debian"; ns2.over-link.net: "9.9.5-9+deb8u19-Debian". Hide or replace the version string.
    #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 2012013917 · primary ns1.over-link.net

Found

Primary (MNAME)
ns1.over-link.net
Contact (RNAME)
admin.over-link.net
Serial
2012013917
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.over-link.net (91.209.154.3)2012013917
ns2.over-link.net (46.183.49.20)2012013917

Checks

  • ✓ Serial 2012013917 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.over-link.net is one of the listed nameservers.
  • ✓ Contact admin@over-link.net #25
    The SOA RNAME admin.over-link.net means admin@over-link.net.
  • ✓ Timestamp serial #26
    The serial 2012013917 is a Unix timestamp (2033-10-04 04:45 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
91.209.154.3:53
TypeValueTTL
SOAns1.over-link.net. admin.over-link.net. 2012013917 21600 3600 604800 8640086400
NSns1.over-link.net.86400
NSns2.over-link.net.86400
A46.183.50.3586400
MX10 ille-et-vilaine.in.tmes.trendmicro.eu.86400
TXT"globalsign-domain-verification=F886E0876E78B9D9F252FB405549AC37"86400
TXT"cisco-ci-domain-verification=2c484c16ab4abaa7cf85ddd3010cf472fece035f8e12d0e87bef328e31e5c2c1"86400
TXT"MS=ms42727377"86400
TXT"U3+vUFblwVMphzodh78CTnLZUH9jNOGDD9sVcJ90M01Gw/TkXBtsXdP+WmJacycr/oYHLJgXbNLGfw70OG1MBw=="86400
TXT"google-site-verification=t9Uyv8NEQYMLkqg9wdwY5dL5-ME_fmDtQe0grQtSHOQ"86400
TXT"v=spf1 include:spf.tmes.trendmicro.com ip4:109.2.202.226 ip4:46.183.50.36 ip4:46.183.50.37 ip4:46.183.50.39 ip4:46.183.50.48 ip4:46.183.50.49 include:spf.cap-collectif.com include:spf.protection.outlook.com -all"86400
TXT"MS=6E77C69D3253FCE4C5A3B58AA952978253481E01"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