iospress.nl

Checked 21 October 2026, 21:22 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 0 failed 8 info

Registration

info

.nl country-code · 1API Gmbh

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
1API Gmbh
Registered
11 September 1995
Last changed
11 December 2025
Status
active
Registry nameservers
ns09.domaincontrol.com, ns10.domaincontrol.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

ns09.domaincontrol.com, ns10.domaincontrol.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns09.domaincontrol.com, ns10.domaincontrol.com
NS in the zone
ns09.domaincontrol.com, ns10.domaincontrol.com
NameserverAddressesNetwork (AS)Glue
ns09.domaincontrol.com97.74.104.5 2603:5:2180::5AS44273 GODADDY-DNS - Host Europe GmbH, DE AS44273 GODADDY-DNS - Host Europe GmbH, DE-
ns10.domaincontrol.com173.201.72.5 2603:5:2280::5AS44273 GODADDY-DNS - Host Europe GmbH, DE AS44273 GODADDY-DNS - Host Europe GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns09.domaincontrol.com, ns10.domaincontrol.com.
    #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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS44273 (GODADDY-DNS - Host Europe GmbH, DE): 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns09.domaincontrol.com 97.74.104.5NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns09.domaincontrol.com 2603:5:2180::5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns10.domaincontrol.com 173.201.72.5NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns10.domaincontrol.com 2603:5:2280::5NOERROR, 3 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 2026072300 · primary ns09.domaincontrol.com

Found

Primary (MNAME)
ns09.domaincontrol.com
Contact (RNAME)
dns.jomax.net
Serial
2026072300
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns09.domaincontrol.com (97.74.104.5)2026072300
ns09.domaincontrol.com (2603:5:2180::5)2026072300
ns10.domaincontrol.com (173.201.72.5)2026072300
ns10.domaincontrol.com (2603:5:2280::5)2026072300

Checks

  • ✓ Serial 2026072300 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns09.domaincontrol.com is one of the listed nameservers.
  • ✓ Contact dns@jomax.net #25
    The SOA RNAME dns.jomax.net means dns@jomax.net.
  • ✓ Date-based serial #26
    The serial 2026072300 follows the YYYYMMDDnn convention (2026-07-23).

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

12 records at the apex

Found

Read from
97.74.104.5:53
TypeValueTTL
SOAns09.domaincontrol.com. dns.jomax.net. 2026072300 28800 7200 604800 6003600
NSns09.domaincontrol.com.3600
NSns10.domaincontrol.com.3600
A15.197.225.1283600
A3.33.251.1683600
MX0 iospress-nl.mail.protection.outlook.com.3600
TXT"v=spf1 a mx include:spf.protection.outlook.com include:spf.em.secureserver.net include:email.freshdesk.com a:webserver14.exxtra.net ~all"3600
TXT"MS=ms65519699"3600
TXT"ddion4sej4qql3kkav3g0raupa"3600
TXT"google-site-verification=UXYYKHHKsuk5-p1REl6pT8j5UQF--6XylEOw9Zt_m8M"3600
TXT"MS=44DA573CAD7B7E927FFC805A57429BAFF370FD9F"3600
TXT"i7LJsKkZYlb0BkZYupkEMPCz19rfUXoI5AdUaQ1waQc="3600

Checks

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