brest-metropole-tourisme.fr

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

Registration

info

.fr country-code · DIGITAL RURAL INFORMATIQUE · expires 2027-03-10

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
DIGITAL RURAL INFORMATIQUE
Registered
10 March 2005
Last changed
30 April 2026
Expires
10 March 2027
Status
active
Registry nameservers
ns1.produhost.net, ns2.produhost.net, ns3.produhost.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-03-10 #3
    The registration is valid until 2027-03-10 (139 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.produhost.net, ns2.produhost.net, ns3.produhost.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.produhost.net, ns2.produhost.net, ns3.produhost.net
NS in the zone
ns1.produhost.net, ns2.produhost.net, ns3.produhost.net
NameserverAddressesNetwork (AS)Glue
ns1.produhost.net195.114.26.27AS6738 DRI - DRI SAS, FR-
ns2.produhost.net185.42.31.29AS197816 ETIX-EVERYWHERE - Etix Everywhere Ouest SAS, FR-
ns3.produhost.net141.94.162.140AS16276 OVH - OVH SAS, FR-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.produhost.net, ns2.produhost.net, ns3.produhost.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 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS197816 (ETIX-EVERYWHERE - Etix Everywhere Ouest SAS, FR): 1 address; AS6738 (DRI - DRI SAS, FR): 1 address.
  • 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

fail

2 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.produhost.net 195.114.26.27no responsenono / no--
ns2.produhost.net 185.42.31.29NOERROR, 21 ms, authoritativenoyes / yesrefused-
ns3.produhost.net 141.94.162.140NOERROR, 18 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.produhost.net (195.114.26.27): read udp 46.225.38.91:44867->195.114.26.27:53: i/o timeout.
    #14
  • ✓ 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 2026101501 · primary ns1.produhost.net

Found

Primary (MNAME)
ns1.produhost.net
Contact (RNAME)
hostmaster.brest-metropole-tourisme.fr
Serial
2026101501
Refresh / retry
21600 s / 3600 s
Expire
2419200 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns2.produhost.net (185.42.31.29)2026101501
ns3.produhost.net (141.94.162.140)2026102201

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2026101501 on ns2.produhost.net (185.42.31.29); 2026102201 on ns3.produhost.net (141.94.162.140). 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 6h, retry 1h, expire 28d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.produhost.net is one of the listed nameservers.
  • ✓ Contact hostmaster@brest-metropole-tourisme.fr #25
    The SOA RNAME hostmaster.brest-metropole-tourisme.fr means hostmaster@brest-metropole-tourisme.fr.
  • ✓ Date-based serial #26
    The serial 2026101501 follows the YYYYMMDDnn convention (2026-10-15).

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

11 records at the apex

Found

Read from
185.42.31.29:53
TypeValueTTL
SOAns1.produhost.net. hostmaster.brest-metropole-tourisme.fr. 2026101501 21600 3600 2419200 864003600
NSns3.produhost.net.86400
NSns1.produhost.net.86400
NSns2.produhost.net.86400
A195.95.168.2053600
MX10 de-smtp-inbound-2.mimecast.com.3600
MX10 de-smtp-inbound-1.mimecast.com.3600
MX50 brestmetropoletourisme-fr01c1i.mail.protection.outlook.com.3600
TXT"MS=ms77451312"3600
TXT"v=spf1 include:eu.zcsend.net include:spf.protection.outlook.com include:spf.voxpay.fr ~all"3600
TXT"MS=ms14865311"3600

Checks

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