sipa.be

Checked 22 October 2026, 07:10 UTC · via 8.8.8.8
✗Problems found
20 passed 1 warning 1 failed 7 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

pdns1.registrar-servers.com, pdns2.registrar-servers.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
pdns1.registrar-servers.com, pdns2.registrar-servers.com
NS in the zone
pdns1.registrar-servers.com, pdns2.registrar-servers.com
NameserverAddressesNetwork (AS)Glue
pdns1.registrar-servers.com156.154.132.100 2610:a1:1024::100AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US-
pdns2.registrar-servers.com156.154.133.100 2610:a1:1025::100AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pdns1.registrar-servers.com, pdns2.registrar-servers.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 (AS12008 (VERCARA - Vercara, LLC, US): 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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
pdns1.registrar-servers.com 156.154.132.100NOERROR, 13 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
pdns1.registrar-servers.com 2610:a1:1024::100NOERROR, 32 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
pdns2.registrar-servers.com 156.154.133.100NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
pdns2.registrar-servers.com 2610:a1:1025::100NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: pdns1.registrar-servers.com: "UltraDNS Nameserver"; pdns2.registrar-servers.com: "UltraDNS Nameserver".
    #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 1783261530 · primary pdns1.registrar-servers.com

Found

Primary (MNAME)
pdns1.registrar-servers.com
Contact (RNAME)
hostmaster.registrar-servers.com
Serial
1783261530
Refresh / retry
43200 s / 3600 s
Expire
604800 s
Negative TTL
3601 s

Serial per nameserver

NameserverSerial
pdns1.registrar-servers.com (156.154.132.100)1783261530
pdns1.registrar-servers.com (2610:a1:1024::100)1783261530
pdns2.registrar-servers.com (156.154.133.100)1783261530
pdns2.registrar-servers.com (2610:a1:1025::100)1783261530

Checks

  • ✓ Serial 1783261530 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 1h, expire 7d, negative TTL 1h0m1s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pdns1.registrar-servers.com is one of the listed nameservers.
  • ✓ Contact hostmaster@registrar-servers.com #25
    The SOA RNAME hostmaster.registrar-servers.com means hostmaster@registrar-servers.com.
  • ✓ Timestamp serial #26
    The serial 1783261530 is a Unix timestamp (2026-07-05 14:25 UTC).

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

fail

7 records at the apex

Found

Read from
156.154.132.100:53
TypeValueTTL
SOApdns1.registrar-servers.com. hostmaster.registrar-servers.com. 1783261530 43200 3600 604800 36013601
NSpdns1.registrar-servers.com.1800
NSpdns2.registrar-servers.com.1800
MX10 mail.protonmail.ch.1799
MX20 mailsec.protonmail.ch.1799
TXT"v=spf1 include:_spf.protonmail.ch mx ~all"1799
TXT"protonmail-verification=53e6700218cc5f2b16b981fda567441a9d5b5427"1799

Checks

  • ✓ TTLs within range #32
    TTLs: MX 29m59s, NS 30m. The NS TTL at the parent is 1d and in the zone 30m; resolvers may use either.
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to zps.sipa.be. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • ✓ 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