lagom.nl

Checked 22 October 2026, 14:10 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 6 info

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
27 January 2005
Last changed
23 March 2021
Status
active
Registry nameservers
ns.lagom.nl, ns1.transip.nl, ns2.transip.eu
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

ns.lagom.nl, ns1.transip.nl, ns2.transip.eu

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns.lagom.nl, ns1.transip.nl, ns2.transip.eu
NS in the zone
ns.lagom.nl, ns0.transip.net, ns1.transip.nl
NameserverAddressesNetwork (AS)Glue
ns.lagom.nl46.19.38.60AS196752 TILAA - Tilaa B.V., NL46.19.38.60
ns0.transip.net (zone only)195.135.195.195 2a01:7c8:dddd:195::195AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL-
ns1.transip.nl195.8.195.195 2a01:7c8:7000:195::195AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL195.8.195.195 2a01:7c8:7000:195::195
ns2.transip.eu (parent only)37.97.199.195 2a01:7c8:f:c1f::195AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.lagom.nl, ns1.transip.nl, ns2.transip.eu.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.transip.eu; only in the zone: ns0.transip.net. ns.lagom.nl, ns0.transip.net, ns1.transip.nl, ns2.transip.eu report NS ns.lagom.nl ns0.transip.net ns1.transip.nl.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns.lagom.nl.
  • ✓ 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 4 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS196752 (TILAA - Tilaa B.V., NL): 1 address; AS20857 (TRANSIP-AS - Signet B.V., NL): 6 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .eu, .nl.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns.lagom.nl.
    #13

Nameservers

pass

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.lagom.nl 46.19.38.60NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns0.transip.net 195.135.195.195NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns0.transip.net 2a01:7c8:dddd:195::195NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns1.transip.nl 195.8.195.195NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns1.transip.nl 2a01:7c8:7000:195::195NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.transip.eu 37.97.199.195NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.transip.eu 2a01:7c8:f:c1f::195NOERROR, 11 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 7 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 2017100400 · primary ns.lagom.nl

Found

Primary (MNAME)
ns.lagom.nl
Contact (RNAME)
postmaster.lagom.nl
Serial
2017100400
Refresh / retry
3600 s / 3600 s
Expire
2419200 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.lagom.nl (46.19.38.60)2017100400
ns0.transip.net (195.135.195.195)2017100400
ns0.transip.net (2a01:7c8:dddd:195::195)2017100400
ns1.transip.nl (195.8.195.195)2017100400
ns1.transip.nl (2a01:7c8:7000:195::195)2017100400
ns2.transip.eu (37.97.199.195)2017100400
ns2.transip.eu (2a01:7c8:f:c1f::195)2017100400

Checks

  • ✓ Serial 2017100400 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.lagom.nl is one of the listed nameservers.
  • ✓ Contact postmaster@lagom.nl #25
    The SOA RNAME postmaster.lagom.nl means postmaster@lagom.nl.
  • ✓ Date-based serial #26
    The serial 2017100400 follows the YYYYMMDDnn convention (2017-10-04).

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

7 records at the apex

Found

Read from
46.19.38.60:53
TypeValueTTL
SOAns.lagom.nl. postmaster.lagom.nl. 2017100400 3600 3600 2419200 8640043200
NSns.lagom.nl.43200
NSns0.transip.net.43200
NSns1.transip.nl.43200
A46.19.38.6043200
MX10 mail.lagom.nl.43200
TXT"v=spf1 a mx ptr ~all"43200

Checks

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