looopings.nl

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

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/looopings.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/looopings.nl returned HTTP 429
    #3

Delegation

warn

ns1.loooopings.nl, ns2.loooopings.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.loooopings.nl, ns2.loooopings.nl
NS in the zone
ns1.loooopings.nl, ns2.loooopings.nl
NameserverAddressesNetwork (AS)Glue
ns1.loooopings.nl185.232.249.242AS48635 CLDIN-NL - Your Hosting B.V., NL185.232.249.242
ns2.loooopings.nl185.232.249.245AS48635 CLDIN-NL - Your Hosting B.V., NL185.232.249.245

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.loooopings.nl, ns2.loooopings.nl.
    #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 one network
    all IPv4 addresses are in 185.232.249.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS48635 (CLDIN-NL - Your Hosting B.V., NL): 2 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 .nl
    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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.loooopings.nl 185.232.249.242NOERROR, 10 ms, authoritativenoyes / yesrefusednone
ns2.loooopings.nl 185.232.249.245NOERROR, 10 ms, authoritativenoyes / yesrefusednone

Checks

  • ✓ All respond #14
    All 2 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.loooopings.nl: "none"; ns2.loooopings.nl: "none".
    #17
  • ✓ 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 2026100701 · primary ns2.loooopings.nl

Found

Primary (MNAME)
ns2.loooopings.nl
Contact (RNAME)
hostmaster.looopings.nl
Serial
2026100701
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.loooopings.nl (185.232.249.242)2026100701
ns2.loooopings.nl (185.232.249.245)2026100701

Checks

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

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

9 records at the apex

Found

Read from
185.232.249.242:53
TypeValueTTL
SOAns2.loooopings.nl. hostmaster.looopings.nl. 2026100701 10800 3600 604800 1080014400
NSns1.loooopings.nl.14400
NSns2.loooopings.nl.14400
A185.232.249.24214400
MX10 mail.looopings.nl.14400
TXT"google-site-verification=VgcZx-0D5NlC7FXHUmkEJaG-HRrbmXXZ5etj1ssSGhM"14400
TXT"google-site-verification=62rya9e5_2EjUA7pbgvjfM4Sgt5qqKZ4IodL-7Cm2Uo"14400
TXT"brevo-code:276f3fcf328d87f671fc28ce0445b7e7"14400
TXT"v=spf1 mx a ip4:185.232.249.242 ip4:185.28.58.46 -all"14400

Checks

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