techtastic.nl

Checked 22 October 2026, 16:30 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 5 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/techtastic.nl returned HTTP 429

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
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/techtastic.nl returned HTTP 429
    #3

Delegation

warn

ns1.megpanel.com, ns2.megpanel.com, ns3.megpanel.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.megpanel.com, ns2.megpanel.com, ns3.megpanel.com
NS in the zone
ns1.megpanel.com, ns2.megpanel.com, ns3.megpanel.com, ns4.megpanel.com
NameserverAddressesNetwork (AS)Glue
ns1.megpanel.com172.233.145.179AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns2.megpanel.com173.255.230.136AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns3.megpanel.com178.79.188.107AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns4.megpanel.com (zone only)172.233.56.199AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.megpanel.com, ns2.megpanel.com, ns3.megpanel.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns4.megpanel.com. ns1.megpanel.com, ns2.megpanel.com, ns3.megpanel.com, ns4.megpanel.com report NS ns1.megpanel.com ns2.megpanel.com ns3.megpanel.com ns4.megpanel.com.
    #7
  • ✓ 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 4 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS63949 (AKAMAI-LINODE-AP - Akamai Connected Cloud, SG): 4 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.megpanel.com 172.233.145.179NOERROR, 156 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
ns2.megpanel.com 173.255.230.136NOERROR, 91 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
ns3.megpanel.com 178.79.188.107NOERROR, 17 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
ns4.megpanel.com 172.233.56.199NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)

Checks

  • ✓ All respond #14
    All 4 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.megpanel.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; ns2.megpanel.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)"; ns3.megpanel.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)"; ns4.megpanel.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)". 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 2026102205 · primary ns1.megpanel.com

Found

Primary (MNAME)
ns1.megpanel.com
Contact (RNAME)
admin.megpanel.com
Serial
2026102205
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.megpanel.com (172.233.145.179)2026102205
ns2.megpanel.com (173.255.230.136)2026102205
ns3.megpanel.com (178.79.188.107)2026102205
ns4.megpanel.com (172.233.56.199)2026102205

Checks

  • ✓ Serial 2026102205 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.megpanel.com is one of the listed nameservers.
  • ✓ Contact admin@megpanel.com #25
    The SOA RNAME admin.megpanel.com means admin@megpanel.com.
  • ✓ Date-based serial #26
    The serial 2026102205 follows the YYYYMMDDnn convention (2026-10-22).

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

9 records at the apex

Found

Read from
172.233.145.179:53
TypeValueTTL
SOAns1.megpanel.com. admin.megpanel.com. 2026102205 3600 1800 1209600 8640086400
NSns1.megpanel.com.86400
NSns2.megpanel.com.86400
NSns3.megpanel.com.86400
NSns4.megpanel.com.86400
A178.63.185.161300
MX0 techtastic.nl.300
TXT"v=spf1 ip4:46.4.10.218 include:relay.mailbaby.net ip4:185.56.137.130 +a +mx +ip4:185.28.189.216 +ip4:185.28.189.208 ~all"300
TXT"google-site-verification=HzWtYeyR6QxIzu9Mk225f7eoao_jnRQwtEct85cCuoI"300

Checks

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