Domain report: novacollege.nl

Registration

info

.nl country-code

Found

TLD: .nl (country-code)
ICANN policies apply: no

Lookup error: https://rdap.sidn.nl/domain/novacollege.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/novacollege.nl returned HTTP 429

#3

Delegation

warn

ns1.qsp.nl, ns2.qsp.nl

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns1.qsp.nl, ns2.qsp.nl
NS in the zone: ns1.qsp.nl, ns2.qsp.nl

Nameserver	Addresses	Network (AS)	Glue
ns1.qsp.nl	193.254.215.240 2a04:c580:0:f0::1	AS12315 QSP-AS - Quality Service Provider BV, NL AS12315 QSP-AS - Quality Service Provider BV, NL	193.254.215.240
ns2.qsp.nl	193.254.215.241 2a04:c580:0:f1::1	AS12315 QSP-AS - Quality Service Provider BV, NL AS12315 QSP-AS - Quality Service Provider BV, NL	193.254.215.241

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.qsp.nl, ns2.qsp.nl.

#6
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
!

Glue differs from the zone

The addresses at the parent (glue) differ from the addresses in the zone: ns1.qsp.nl (glue 193.254.215.240, zone 193.254.215.240, 2a04:c580:0:f0::1); ns2.qsp.nl (glue 193.254.215.241, zone 193.254.215.241, 2a04:c580:0:f1::1). Update the glue at your registrar.

#8
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
!

Nameservers in one network

all IPv4 addresses are in 193.254.215.0/24; all IPv6 addresses are in 2a04:c580::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS12315 (QSP-AS - Quality Service Provider BV, NL): 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 .nl

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
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.qsp.nl 193.254.215.240	NOERROR, 36 ms, authoritative	no	yes / yes	refused	undisclosed
ns1.qsp.nl 2a04:c580:0:f0::1	NOERROR, 15 ms, authoritative	no	yes / yes	refused	undisclosed
ns2.qsp.nl 193.254.215.241	NOERROR, 35 ms, authoritative	no	yes / yes	refused	undisclosed
ns2.qsp.nl 2a04:c580:0:f1::1	NOERROR, 15 ms, authoritative	no	yes / yes	refused	undisclosed

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.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns1.qsp.nl: "undisclosed"; ns2.qsp.nl: "undisclosed".

#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 2026092400 · primary ns1.qsp.nl

Found

Primary (MNAME): ns1.qsp.nl
Contact (RNAME): domain.qsp.nl
Serial: 2026092400
Refresh / retry: 14400 s / 1800 s
Expire: 604800 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
ns1.qsp.nl (193.254.215.240)	2026092400
ns1.qsp.nl (2a04:c580:0:f0::1)	2026092400
ns2.qsp.nl (193.254.215.241)	2026092400
ns2.qsp.nl (2a04:c580:0:f1::1)	2026092400

Checks

✓ Serial 2026092400 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 4h, retry 30m, expire 7d, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver ns1.qsp.nl is one of the listed nameservers.
✓ Contact domain@qsp.nl #25

The SOA RNAME domain.qsp.nl means domain@qsp.nl.
✓ Date-based serial #26

The serial 2026092400 follows the YYYYMMDDnn convention (2026-09-24).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 33 iterations, 8-byte salt
Signatures valid until: 15 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
10760	RSASHA512 (10)	SHA256 E3E0E1D349AFB825…	yes
54966	RSASHA512 (10)	SHA256 1EE3881607E02975…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
10760	ZSK (256)	RSASHA512 (10)
54966	KSK (257)	RSASHA512 (10)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 10760 (SHA256), key tag 54966 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA512 (10).
✓ Signatures valid until 2026-11-15 #30

The earliest DNSKEY/SOA signature expires at 2026-11-15 01:47 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 33 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

#31

Records

info

6 records at the apex

Found

Read from: 193.254.215.240:53

Type	Value	TTL
SOA	ns1.qsp.nl. domain.qsp.nl. 2026092400 14400 1800 604800 86400	86400
NS	ns2.qsp.nl.	86400
NS	ns1.qsp.nl.	86400
A	20.50.2.93	86400
MX	0 novacollege-nl.mail.protection.outlook.com.	86400
TXT	"v=spf1 mx include:spf.protection.outlook.com ip4:62.204.93.131 ip4:207.244.98.227 ip4:83.149.98.72 ip4:81.17.56.1 ip4:83.149.98.73 ip4:13.88.226.191 ip4:40.115.66.46 ip4:13.94.232.90 ip4:191.238.213.99 ip4:51.13.102.144 ip4:178.162.177.161" " ip4:13.74.56.125 ip4:4.185.96.20 ip4:20.162.206.62 ip4:172.172.139.18 ip4:4.223.229.111 ip4:185.51.192.213/32 ip4:185.51.192.82/32 ip6:2a01:b2e0:2::213/128 ip6:2a01:b2e0:2::82/128 ip4:46.31.48.0/21 ip4:37.221.216.0/21 ip4:185.136.64.0/23 i" "p4:185.53.16.0/22 ip4:91.197.72.0/22 ip4:194.88.230.0/23 ip4:195.137.214.0/23 ip4:135.84.216.0/22 ip4:66.240.227.0/24 ip4:63.143.59.128/25 ip4:63.143.57.128/25 ip4:216.98.158.0/24 ip4:74.63.212.0/24 ip4:52.200.59.0/24 ip4:34.245.210.0/24 ip" "4:34.245.210.0/24 ip4:87.233.189.160/27 ip4:87.233.196.64/27 ip4:87.233.187.16/28 ip4:87.233.143.149/28 ip4:149.210.201.157/32 ip4:54.194.237.169 ip4:147.253.222.19 include:_spf.sparkpostmail.com ip4:213.206.97.206 ip4:213.206.97.207 ip4:46" ".19.217.0/24 ip4:80.247.220.50 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.145.0/24 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.177.0/24 ip4:198" ".2.178.0/23 ip4:198.2.180.0/24 ip4:31.7.1.24 ip4:213.206.97.206 ip4:213.206.97.207 ip4:80.250.142.37 ip4:80.250.142.66 ip4:80.250.142.115 ip4:80.250.142.14 ip4:46.19.217.0/24 ip4:80.250.128.0/24 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100" ".0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 include:spf-flat.8m.nl ip4:167.89.91.217 ip4:85.17.2.229 ip4:147.253.222.19 ip4:167.89.91.217 include:spf.mailjet.com ip4:52.28.145.0 ip4:85.90.64.176/28 ip4:85.90.64.192/28 ~all" ""	86400

Checks

✓ TTLs within range #32

TTLs: A 1d, MX 1d, 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.
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