shell.nl

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

Registration

info

.nl country-code · Com Laude

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Com Laude
Registered
25 July 1994
Last changed
6 August 2024
Status
active
Registry nameservers
dns1.shell.com, dns2.shell.com, dns3.shell.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

warn

dns1.shell.com, dns2.shell.com, dns3.shell.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
dns1.shell.com, dns2.shell.com, dns3.shell.com
NS in the zone
dns1.shell.com, dns2.shell.com, dns3.shell.com
NameserverAddressesNetwork (AS)Glue
dns1.shell.com134.146.80.20AS3917 SHELL-3917 - Shell Information Technology International B.V., EU-
dns2.shell.com144.199.196.20AS3918 SHELL-3918 - Shell Information Technology International B.V., EU-
dns3.shell.com134.163.128.20AS11355 SHELL - Shell Information Technology International, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.shell.com, dns2.shell.com, dns3.shell.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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS11355 (SHELL - Shell Information Technology International, Inc., US): 1 address; AS3917 (SHELL-3917 - Shell Information Technology International B.V., EU): 1 address; AS3918 (SHELL-3918 - Shell Information Technology International B.V., EU): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.shell.com 134.146.80.20NOERROR, 13 ms, authoritativenoyes / yesrefused-
dns2.shell.com 144.199.196.20NOERROR, 249 ms, authoritativenoyes / yesrefused-
dns3.shell.com 134.163.128.20NOERROR, 135 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 47053 · primary dns1.shell.com

Found

Primary (MNAME)
dns1.shell.com
Contact (RNAME)
dns.shell.com
Serial
47053
Refresh / retry
10800 s / 1080 s
Expire
2419200 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
dns1.shell.com (134.146.80.20)47053
dns2.shell.com (144.199.196.20)47053
dns3.shell.com (134.163.128.20)47053

Checks

  • ✓ Serial 47053 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 18m, expire 28d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.shell.com is one of the listed nameservers.
  • ✓ Contact dns@shell.com #25
    The SOA RNAME dns.shell.com means dns@shell.com.
  • ✓ Counter serial #26
    The serial 47053 is a plain counter.

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
10 iterations, 6-byte salt
Signatures valid until
25 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
31102RSASHA256 (8)SHA256 A680B6D4BEFF6544…NO
26737RSASHA256 (8)SHA256 32EA97153A025631…yes

DNSKEY in the zone

Key tagRoleAlgorithm
29391ZSK (256)RSASHA256 (8)
6991KSK (257)RSASHA256 (8)
26737KSK (257)RSASHA256 (8)
36811ZSK (256)RSASHA256 (8)
47559ZSK (256)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • i
    Unused DS records
    These DS records match no key in the zone: key tag 31102 (SHA256). That is normal during a key rollover; otherwise remove them.
    #28
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 96h0m0s and created on demand; the current one was made at 2026-10-21 06:38 UTC and expires at 2026-10-25 06:48 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 10 iterations and a 6-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

9 records at the apex

Found

Read from
134.146.80.20:53
TypeValueTTL
SOAdns1.shell.com. dns.shell.com. 47053 10800 1080 2419200 60086400
NSdns3.shell.com.86400
NSdns1.shell.com.86400
NSdns2.shell.com.86400
A4.210.156.18486400
MX20 mail.global.frontbridge.com.900
TXT"_5wtvr6abpj9l6dz0y4zxf6t8lw6l9em"300
TXT"facebook-domain-verification=3v39tfhr3me17yf0z5o38w6bwbq2o1"300
TXT"google-site-verification=3C2442EmT4XjlIEwS_hRGpr7dvNbMPjCfbVR8s2DZ_w"300

Checks

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