pirateparty.be

Checked 22 October 2026, 07:01 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 6 info

Registration

info

.be country-code

Found

TLD
.be (country-code)
ICANN policies apply
no

Checks

  • i
    .be 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
    .be is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net, ns4.yourdomainprovider.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net, ns4.yourdomainprovider.net
NS in the zone
ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net, ns4.yourdomainprovider.net
NameserverAddressesNetwork (AS)Glue
ns1.yourdomainprovider.net185.88.143.183 2a00:c6c0:0:150:1::1AS47172 Greenhost - Greenhost BV, NL AS47172 Greenhost - Greenhost BV, NL-
ns2.yourdomainprovider.net46.101.153.24 2a03:b0c0:3:d0::124:5001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-
ns3.yourdomainprovider.net104.236.29.251 2604:a880:800:10::9a1:2001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-
ns4.yourdomainprovider.net128.199.185.81 2400:6180:0:d0::258:f001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net, ns4.yourdomainprovider.net.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 6 addresses; AS47172 (Greenhost - Greenhost BV, NL): 2 addresses.
  • i
    All nameserver names under .net
    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

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.yourdomainprovider.net 185.88.143.183NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns1.yourdomainprovider.net 2a00:c6c0:0:150:1::1NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.yourdomainprovider.net 46.101.153.24NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.yourdomainprovider.net 2a03:b0c0:3:d0::124:5001NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns3.yourdomainprovider.net 104.236.29.251NOERROR, 94 ms, authoritativenoyes / yesrefused-
ns3.yourdomainprovider.net 2604:a880:800:10::9a1:2001NOERROR, 90 ms, authoritativenoyes / yesrefused-
ns4.yourdomainprovider.net 128.199.185.81NOERROR, 171 ms, authoritativenoyes / yesrefused-
ns4.yourdomainprovider.net 2400:6180:0:d0::258:f001NOERROR, 160 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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 2025031701 · primary ns1.yourdomainprovider.net

Found

Primary (MNAME)
ns1.yourdomainprovider.net
Contact (RNAME)
hostmaster.metaregistrar.com
Serial
2025031701
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.yourdomainprovider.net (185.88.143.183)2025031701
ns1.yourdomainprovider.net (2a00:c6c0:0:150:1::1)2025031701
ns2.yourdomainprovider.net (46.101.153.24)2025031701
ns2.yourdomainprovider.net (2a03:b0c0:3:d0::124:5001)2025031701
ns3.yourdomainprovider.net (104.236.29.251)2025031701
ns3.yourdomainprovider.net (2604:a880:800:10::9a1:2001)2025031701
ns4.yourdomainprovider.net (128.199.185.81)2025031701
ns4.yourdomainprovider.net (2400:6180:0:d0::258:f001)2025031701

Checks

  • ✓ Serial 2025031701 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 14d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.yourdomainprovider.net is one of the listed nameservers.
  • ✓ Contact hostmaster@metaregistrar.com #25
    The SOA RNAME hostmaster.metaregistrar.com means hostmaster@metaregistrar.com.
  • ✓ Date-based serial #26
    The serial 2025031701 follows the YYYYMMDDnn convention (2025-03-17).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
5 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
24438ZSK (256)RSASHA256 (8)
40519KSK (257)RSASHA256 (8)
57493ZSK (256)RSASHA256 (8)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

9 records at the apex

Found

Read from
185.88.143.183:53
TypeValueTTL
SOAns1.yourdomainprovider.net. hostmaster.metaregistrar.com. 2025031701 3600 3600 1209600 36003600
NSns1.yourdomainprovider.net.3600
NSns4.yourdomainprovider.net.3600
NSns3.yourdomainprovider.net.3600
NSns2.yourdomainprovider.net.3600
A94.130.226.643600
AAAA2a01:4f8:c0c:8fdc::13600
MX10 mta-gw.infomaniak.ch.3600
TXT"v=spf1 include:spf.infomaniak.ch -all"3600

Checks

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