ville-boulogne-sur-mer.fr

Checked 22 October 2026, 05:44 UTC · via 8.8.8.8
!Passed with warnings
19 passed 6 warnings 0 failed 6 info

Registration

info

.fr country-code · CELESTE · expires 2027-05-29

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
CELESTE
Registered
14 March 2000
Last changed
30 June 2026
Expires
29 May 2027
Status
active
Registry nameservers
ns500013.as16211.net, ns500014.as16211.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-05-29 #3
    The registration is valid until 2027-05-29 (219 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

ns500013.as16211.net, ns500014.as16211.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns500013.as16211.net, ns500014.as16211.net
NS in the zone
ns500013.as16211.net, ns500014.as16211.net
NameserverAddressesNetwork (AS)Glue
ns500013.as16211.net62.193.51.141AS34177 CELESTE-AS - Celeste SAS, FR-
ns500014.as16211.net62.193.51.142AS34177 CELESTE-AS - Celeste SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns500013.as16211.net, ns500014.as16211.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 one network
    all IPv4 addresses are in 62.193.51.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 (AS34177 (CELESTE-AS - Celeste SAS, 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
ns500013.as16211.net 62.193.51.141NOERROR, 14 ms, authoritativenoyes / yesrefused9.11.5-P4-5.1+deb10u5-Debian
ns500014.as16211.net 62.193.51.142NOERROR, 14 ms, authoritativenoyes / yesrefused9.11.5-P4-5.1+deb10u5-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: ns500013.as16211.net: "9.11.5-P4-5.1+deb10u5-Debian"; ns500014.as16211.net: "9.11.5-P4-5.1+deb10u5-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

warn

serial 2026100501 · primary ns500013.as16211.net

Found

Primary (MNAME)
ns500013.as16211.net
Contact (RNAME)
dns.stella-telecom.fr
Serial
2026100501
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns500013.as16211.net (62.193.51.141)2026100501
ns500014.as16211.net (62.193.51.142)2026100501

Checks

  • ✓ Serial 2026100501 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 1000h, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns500013.as16211.net is one of the listed nameservers.
  • ✓ Contact dns@stella-telecom.fr #25
    The SOA RNAME dns.stella-telecom.fr means dns@stella-telecom.fr.
  • ✓ Date-based serial #26
    The serial 2026100501 follows the YYYYMMDDnn convention (2026-10-05).

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

warn

9 records at the apex

Found

Read from
62.193.51.141:53
TypeValueTTL
SOAns500013.as16211.net. dns.stella-telecom.fr. 2026100501 86400 7200 3600000 172800240
NSns500013.as16211.net.240
NSns500014.as16211.net.240
A51.68.75.167240
MX5 mailhost.ville-boulogne-sur-mer.fr.240
TXT"google-site-verification=5TwlhwOVbBXY3xuPHrDUgx3DEH1-epI9goKuLSSmYPg"240
TXT"brevo-code:fe465469e7a872334229ce77c0d8e48c"240
TXT"v=spf1 a mx include:spf.stratis.pro -all"240
TXT"MS=53EE1661BF05DEF745725EFE11D3202A909416E7"240

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (4m), MX (4m), NS (4m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 4m; resolvers may use either.
    #32
  • ✓ 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