rutgerbakt.nl

Checked 22 October 2026, 15:50 UTC · via 8.8.8.8
iAll checks passed
29 passed 0 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/rutgerbakt.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/rutgerbakt.nl returned HTTP 429
    #3

Delegation

info

ns01.forward.antagonist.nl, ns02.forward.antagonist.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns01.forward.antagonist.nl, ns02.forward.antagonist.net
NS in the zone
ns01.forward.antagonist.nl, ns02.forward.antagonist.net
NameserverAddressesNetwork (AS)Glue
ns01.forward.antagonist.nl195.206.121.16 2001:67c:28cc::16AS197495 ONECOM-INFRA - One.com A/S, DK AS197495 ONECOM-INFRA - One.com A/S, DK-
ns02.forward.antagonist.net185.10.11.16 2001:67c:3c0::16AS51468 ONECOM - One.com A/S, DK AS51468 ONECOM - One.com A/S, DK-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.forward.antagonist.nl, ns02.forward.antagonist.net.
    #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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS197495 (ONECOM-INFRA - One.com A/S, DK): 2 addresses; AS51468 (ONECOM - One.com A/S, DK): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .net, .nl.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.forward.antagonist.nl 195.206.121.16NOERROR, 19 ms, authoritativenoyes / yesrefused-
ns01.forward.antagonist.nl 2001:67c:28cc::16NOERROR, 19 ms, authoritativenoyes / yesrefused-
ns02.forward.antagonist.net 185.10.11.16NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns02.forward.antagonist.net 2001:67c:3c0::16NOERROR, 17 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026102201 · primary ns01.forward.antagonist.nl

Found

Primary (MNAME)
ns01.forward.antagonist.nl
Contact (RNAME)
hostmaster.forward.antagonist.nl
Serial
2026102201
Refresh / retry
14400 s / 3600 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns01.forward.antagonist.nl (195.206.121.16)2026102201
ns01.forward.antagonist.nl (2001:67c:28cc::16)2026102201
ns02.forward.antagonist.net (185.10.11.16)2026102201
ns02.forward.antagonist.net (2001:67c:3c0::16)2026102201

Checks

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

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
27220RSASHA256 (8)SHA256 38E0DAE50B292A8A…yes

DNSKEY in the zone

Key tagRoleAlgorithm
27351ZSK (256)RSASHA256 (8)
17524ZSK (256)RSASHA256 (8)
27220KSK (257)RSASHA256 (8)

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 27220 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

11 records at the apex

Found

Read from
195.206.121.16:53
TypeValueTTL
SOAns01.forward.antagonist.nl. hostmaster.forward.antagonist.nl. 2026102201 14400 3600 1209600 60014400
NSns02.forward.antagonist.net.14400
NSns01.forward.antagonist.nl.14400
A62.221.205.413600
AAAA2001:1460:3:2:1c00:74ff:fe00:22883600
MX1 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
MX10 alt4.aspmx.l.google.com.3600
TXT"v=spf1 include:_custspf.g1i.one a mx ip4:195.211.72.0/22 ip4:141.138.168.0/21 ip6:2a03:3c00:a001::/48 ip6:2a03:3c00:a002::/48 include:spf.mailcamp.nl include:_spf.google.com ~all"3600

Checks

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