colmar.fr

Checked 22 October 2026, 02:23 UTC · via 8.8.8.8
✗Problems found
18 passed 4 warnings 1 failed 8 info

Registration

info

.fr country-code · ILLICOWEB · expires 2028-03-18

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
ILLICOWEB
Registered
18 March 2004
Last changed
4 October 2026
Expires
18 March 2028
Status
client delete prohibited
Registry nameservers
dns.illicoweb.com, dns2.illicoweb.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 2028-03-18 #3
    The registration is valid until 2028-03-18 (513 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: client delete prohibited). 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

dns.illicoweb.com, dns2.illicoweb.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
dns.illicoweb.com, dns2.illicoweb.com
NS in the zone
dns.illicoweb.com, dns2.illicoweb.com
NameserverAddressesNetwork (AS)Glue
dns.illicoweb.com51.75.29.137AS16276 OVH - OVH SAS, FR-
dns2.illicoweb.com141.95.86.46AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns.illicoweb.com, dns2.illicoweb.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH 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 .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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns.illicoweb.com 51.75.29.137NOERROR, 16 ms, authoritativenono / yesrefusedPowerDNS Authoritative Server 4.8.3
dns2.illicoweb.com 141.95.86.46NOERROR, 5 ms, authoritativenono / yesrefusedPowerDNS Authoritative Server 4.8.3

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: dns.illicoweb.com: "PowerDNS Authoritative Server 4.8.3"; dns2.illicoweb.com: "PowerDNS Authoritative Server 4.8.3". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns.illicoweb.com (51.75.29.137): dial tcp 51.75.29.137:53: i/o timeout; dns2.illicoweb.com (141.95.86.46): dial tcp 141.95.86.46:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 2026101605 · primary a.misconfigured.dns.server.invalid

Found

Primary (MNAME)
a.misconfigured.dns.server.invalid
Contact (RNAME)
hostmaster.colmar.fr
Serial
2026101605
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns.illicoweb.com (51.75.29.137)2026101605
dns2.illicoweb.com (141.95.86.46)2026101605

Checks

  • ✓ Serial 2026101605 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • i
    Hidden master (not resolvable)
    The primary nameserver a.misconfigured.dns.server.invalid 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 hostmaster@colmar.fr #25
    The SOA RNAME hostmaster.colmar.fr means hostmaster@colmar.fr.
  • ✓ Date-based serial #26
    The serial 2026101605 follows the YYYYMMDDnn convention (2026-10-16).

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

10 records at the apex

Found

Read from
51.75.29.137:53
TypeValueTTL
SOAa.misconfigured.dns.server.invalid. hostmaster.colmar.fr. 2026101605 10800 3600 604800 36003600
NSdns.illicoweb.com.60
NSdns2.illicoweb.com.60
A51.38.53.793600
MX0 colmar-fr.mail.protection.outlook.com.3600
TXT"qW4dS3s00ZO8qt4-jPCp64_eRa7lqmmvNlOKyzhjnjA"1800
TXT"MS=ms60489606"1800
TXT"v=spf1 include:spf.mailjet.com include:md02.com mx ip4:188.64.240.27 ip4:213.166.202.92 include:spf.protection.outlook.com -all"1800
TXT"_globalsign-domain-verification=Ebce19ackLJFBYLMxtf0vU2wJ0GbECGRbteVGx104V"1800
TXT"AwaEMRiU9G7ldvrtRCS98l8RhlFRfXZijO0eRJU74DI="1800

Checks

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