beginthier.nl

Checked 21 October 2026, 20:45 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 7 info

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
5 February 2002
Last changed
29 July 2024
Status
active
Registry nameservers
ns1.dns1dns2dns3.com, ns3.dns1dns2dns3.com
RDAP server
https://rdap.sidn.nl/

Checks

  • i
    .nl 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
    .nl is delegated in the root zone and DNSSEC-signed.
  • i
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • 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.dns1dns2dns3.com, ns3.dns1dns2dns3.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.dns1dns2dns3.com, ns3.dns1dns2dns3.com
NS in the zone
ns1.dns1dns2dns3.com, ns3.dns1dns2dns3.com
NameserverAddressesNetwork (AS)Glue
ns1.dns1dns2dns3.com95.211.191.78AS60781 LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V., NL-
ns3.dns1dns2dns3.com54.38.81.184AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dns1dns2dns3.com, ns3.dns1dns2dns3.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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS60781 (LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V., NL): 1 address.
  • 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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dns1dns2dns3.com 95.211.191.78NOERROR, 10 ms, authoritativenoyes / yesrefused9.16.23-RH
ns3.dns1dns2dns3.com 54.38.81.184NOERROR, 12 ms, authoritativenoyes / yesrefused9.16.23-RH

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.dns1dns2dns3.com: "9.16.23-RH"; ns3.dns1dns2dns3.com: "9.16.23-RH". 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 2026091905 · primary ns1.dns1dns2dns3.com

Found

Primary (MNAME)
ns1.dns1dns2dns3.com
Contact (RNAME)
hostmaster.beginthier.nl
Serial
2026091905
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns1.dns1dns2dns3.com (95.211.191.78)2026091905
ns3.dns1dns2dns3.com (54.38.81.184)2026091905

Checks

  • ✓ Serial 2026091905 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 30m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dns1dns2dns3.com is one of the listed nameservers.
  • ✓ Contact hostmaster@beginthier.nl #25
    The SOA RNAME hostmaster.beginthier.nl means hostmaster@beginthier.nl.
  • ✓ Date-based serial #26
    The serial 2026091905 follows the YYYYMMDDnn convention (2026-09-19).

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

6 records at the apex

Found

Read from
95.211.191.78:53
TypeValueTTL
SOAns1.dns1dns2dns3.com. hostmaster.beginthier.nl. 2026091905 3600 3600 1209600 18003600
NSns3.dns1dns2dns3.com.3600
NSns1.dns1dns2dns3.com.3600
A46.105.235.1063600
MX10 mail.beginthier.nl.3600
TXT"v=spf1 a mx ip4:54.38.81.184 ~all"3600

Checks

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