fcgroningen.nl

Checked 21 October 2026, 21:15 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

.nl country-code · Claranet Benelux B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Claranet Benelux B.V.
Registered
13 March 1997
Last changed
20 August 2026
Status
active
Registry nameservers
ns0.claranet.com, ns1.clara.net, ns2.claranet.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

info

ns0.claranet.com, ns1.clara.net, ns2.claranet.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns0.claranet.com, ns1.clara.net, ns2.claranet.com
NS in the zone
ns0.claranet.com, ns1.clara.net, ns2.claranet.com
NameserverAddressesNetwork (AS)Glue
ns0.claranet.com185.77.72.50 2001:67c:1088::50AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns1.clara.net185.77.72.11 2001:67c:1088::11AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns2.claranet.com195.245.201.50 2001:a88:0:fffa::50AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns0.claranet.com, ns1.clara.net, ns2.claranet.com.
  • ✓ 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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8426 (CLARANET-AS - Claranet Limited, GB): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.claranet.com 185.77.72.50NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns0.claranet.com 2001:67c:1088::50NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.clara.net 185.77.72.11NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.clara.net 2001:67c:1088::11NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.claranet.com 195.245.201.50NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.claranet.com 2001:a88:0:fffa::50NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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

warn

serial 2026031104 · primary ns0.claranet.com

Found

Primary (MNAME)
ns0.claranet.com
Contact (RNAME)
hostmaster.nl.clara.net
Serial
2026031104
Refresh / retry
172800 s / 3600 s
Expire
1728000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns0.claranet.com (185.77.72.50)2026031104
ns0.claranet.com (2001:67c:1088::50)2026031104
ns1.clara.net (185.77.72.11)2026031104
ns1.clara.net (2001:67c:1088::11)2026031104
ns2.claranet.com (195.245.201.50)2026031104
ns2.claranet.com (2001:a88:0:fffa::50)2026031104

Checks

  • ✓ Serial 2026031104 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 2d is outside 20m–1d; negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2d, retry 1h, expire 20d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.claranet.com is one of the listed nameservers.
  • ✓ Contact hostmaster@nl.clara.net #25
    The SOA RNAME hostmaster.nl.clara.net means hostmaster@nl.clara.net.
  • ✓ Date-based serial #26
    The serial 2026031104 follows the YYYYMMDDnn convention (2026-03-11).

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

13 records at the apex

Found

Read from
185.77.72.50:53
TypeValueTTL
SOAns0.claranet.com. hostmaster.nl.clara.net. 2026031104 172800 3600 1728000 172800300
NSns2.claranet.com.300
NSns0.claranet.com.300
NSns1.clara.net.300
A91.98.67.222300
MX0 fcgroningen-nl.mail.protection.outlook.com.3600
TXT"pardot994502=3dab5eb417d7ed3312fd99be1f5ba1c9e9af324cea25f3164f3cbb1ca132d3d6"300
TXT"v=spf1 ip4:40.92.0.0/15 ip4:51.4.72.0/24 ip4:51.5.72.0/24 ip4:51.5.80.0/27 ip4:51.4.80.0/27 ip4:185.46.182.1 ip4:13.111.0.0/16 ip4:40.107.0.0/16 ip4:52.100.0.0/14 ip4:104.47.0.0/17 ip4:77.94.250.156 ip4:77.94.250.157 ip4:77.94.250.158 ip4:77.94.250.159 ip" "4:69.72.32.0/20 ip4:167.89.61.143 ip4:166.78.68.0/22 ip4:20.82.87.96/28 ip4:198.245.81.0/24 ip6:2a00:f60::2:156 ip6:2a00:f60::2:157 ip6:2a00:f60::2:158 include:_spf0000000.fcgroningen.nl -all"300
TXT"google-site-verification=QKTMsLuvHvitkuCEOiktdqVzOdbrQ72ngzU4KRQiotY"300
TXT"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDh+TstyA2e6G+Q1BqEw2a0dhnKg0EtmwBGdFJRf6Nn/5cYKk4jznm79kJvSkrfzahw7kf4dFbv34AWY2jgm1LI9ZzcrQTb8xUF4y/tRyMxdW0rHKWwunAfKEKw5+DEEwSCT1CPU8TDmWJqlAzNkD8GZNU2Lbjn/kbo8oGS6F4M8wIDAQAB"300
TXT"_globalsign-domain-verification=_CSO7LYqwDWusHCcknls4w7sj4obuqTNULx-m-_lzQ"300
TXT"google-site-verification=qj80LqyWrlRVkqrBTomLFsqTfCbgfAZ9hzNCKgslGM4"300
TXT"vz60clq125zmq63x9y28zdsn750d2w65"300

Checks

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