rodajc.nl

Checked 22 October 2026, 15:41 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 4 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/rodajc.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/rodajc.nl returned HTTP 429
    #3

Delegation

warn

ns1.notus.info, ns2.notus.info, ns3.notus.info

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.notus.info, ns2.notus.info, ns3.notus.info
NS in the zone
ns1.notus.info, ns2.notus.info, ns3.notus.info
NameserverAddressesNetwork (AS)Glue
ns1.notus.info91.231.5.49AS205185 DCSPINE - Eurofiber Cloud Infra B.V., NL-
ns2.notus.info91.231.5.50AS205185 DCSPINE - Eurofiber Cloud Infra B.V., NL-
ns3.notus.info31.14.97.16AS20857 TRANSIP-AS - Signet B.V., NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.notus.info, ns2.notus.info, ns3.notus.info.
  • ✓ 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: AS205185 (DCSPINE - Eurofiber Cloud Infra B.V., NL): 2 addresses; AS20857 (TRANSIP-AS - Signet B.V., NL): 1 address.
  • i
    All nameserver names under .info
    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

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.notus.info 91.231.5.49NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:20 by root@localhost)
ns2.notus.info 91.231.5.50NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:20 by root@localhost)
ns3.notus.info 31.14.97.16NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:20 by root@localhost)

Checks

  • ✓ All respond #14
    All 3 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.notus.info: "PowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:20 by root@localhost)"; ns2.notus.info: "PowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:20 by root@localhost)"; ns3.notus.info: "PowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:20 by root@localhost)". 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 2026092211 · primary ns1.notus.info

Found

Primary (MNAME)
ns1.notus.info
Contact (RNAME)
hostmaster.stepco.nl
Serial
2026092211
Refresh / retry
86400 s / 7200 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.notus.info (91.231.5.49)2026092211
ns2.notus.info (91.231.5.50)2026092211
ns3.notus.info (31.14.97.16)2026092211

Checks

  • ✓ Serial 2026092211 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.notus.info is one of the listed nameservers.
  • ✓ Contact hostmaster@stepco.nl #25
    The SOA RNAME hostmaster.stepco.nl means hostmaster@stepco.nl.
  • ✓ Date-based serial #26
    The serial 2026092211 follows the YYYYMMDDnn convention (2026-09-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

warn

10 records at the apex

Found

Read from
91.231.5.49:53
TypeValueTTL
SOAns1.notus.info. hostmaster.stepco.nl. 2026092211 86400 7200 1209600 360086400
NSns1.notus.info.86400
NSns2.notus.info.86400
NSns3.notus.info.86400
A212.125.139.560
MX0 rodajc-nl.mail.protection.outlook.com.60
TXT"MS=ms13380520"60
TXT"v=spf1 include:spf.protection.outlook.com include:spf.mandrillapp.com include:spf.wearehostingyou.com include:spf.afas.online include:_spf.mijnwefact.nl ip4:77.93.90.7 ip4:46.231.81.223 ?all"60
TXT"MS=ms31797413"60
TXT"brevo-code:7accf27653bc5f2200cdc7caf186645f"60

Checks

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