igloorecords.be

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

Registration

info

.be country-code

Found

TLD
.be (country-code)
ICANN policies apply
no

Checks

  • i
    .be 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
    .be is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

warn

ns1.modns.fr, ns2.modns.fr

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.modns.fr, ns2.modns.fr
NS in the zone
ns1.modns.fr, ns2.modns.fr
NameserverAddressesNetwork (AS)Glue
ns1.modns.fr195.144.11.50AS34177 CELESTE-AS - Celeste SAS, FR-
ns2.modns.fr212.83.170.39AS12876 AS12876 - Scaleway SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.modns.fr, ns2.modns.fr.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12876 (AS12876 - Scaleway SAS, FR): 1 address; AS34177 (CELESTE-AS - Celeste SAS, FR): 1 address.
  • i
    All nameserver names under .fr
    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.modns.fr 195.144.11.50NOERROR, 14 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns2.modns.fr 212.83.170.39NOERROR, 15 ms, authoritativenoyes / 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: ns1.modns.fr: "PowerDNS Authoritative Server 4.8.3"; ns2.modns.fr: "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.
  • ✓ 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 2026020910 · primary ns1.modns.fr

Found

Primary (MNAME)
ns1.modns.fr
Contact (RNAME)
whois.phpnet.org
Serial
2026020910
Refresh / retry
14400 s / 7200 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.modns.fr (195.144.11.50)2026020910
ns2.modns.fr (212.83.170.39)2026020910

Checks

  • ✓ Serial 2026020910 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 28d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.modns.fr is one of the listed nameservers.
  • ✓ Contact whois@phpnet.org #25
    The SOA RNAME whois.phpnet.org means whois@phpnet.org.
  • ✓ Date-based serial #26
    The serial 2026020910 follows the YYYYMMDDnn convention (2026-02-09).

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
195.144.11.50:53
TypeValueTTL
SOAns1.modns.fr. whois.phpnet.org. 2026020910 14400 7200 2419200 36003600
NSns1.modns.fr.8300
NSns2.modns.fr.8300
A51.91.68.513600
MX1 aspmx.l.google.com.3600
MX10 alt4.aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
TXT"v=spf1 include:servers.mcsv.net ?all"3600
TXT"google-site-verification=7imEkUtXGkIO3MHrLtfw8a8KufuYBvoPaHm40i4Xsro"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 2h18m20s. The NS TTL at the parent is 1d and in the zone 2h18m20s; 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