supremacy.be

Checked 22 October 2026, 07:11 UTC · via 8.8.8.8
✗Problems found
18 passed 5 warnings 1 failed 5 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

warn

dns1.faastic.com, dns2.faastic.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns1.faastic.com, dns2.faastic.com
NS in the zone
dns1.faastic.com
NameserverAddressesNetwork (AS)Glue
dns1.faastic.com185.179.91.9AS216471 DEVOUT - Devout BV, BE-
dns2.faastic.com (parent only)116.203.182.159AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.faastic.com, dns2.faastic.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: dns2.faastic.com. dns1.faastic.com, dns2.faastic.com report NS dns1.faastic.com.
    #7
  • ✓ 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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS216471 (DEVOUT - Devout BV, BE): 1 address; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.faastic.com 185.179.91.9NOERROR, 16 ms, authoritativenoyes / yesALLOWED (5 records)9.18.39-0ubuntu0.22.04.7-Ubuntu
dns2.faastic.com 116.203.182.159NOERROR, 4 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.faastic.com: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; dns2.faastic.com: "9.18.39-0ubuntu0.22.04.7-Ubuntu". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: dns1.faastic.com (185.179.91.9): 5 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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 3 · primary dns1.faastic.com

Found

Primary (MNAME)
dns1.faastic.com
Contact (RNAME)
info.faastic.com
Serial
3
Refresh / retry
900 s / 600 s
Expire
86400 s
Negative TTL
14400 s

Serial per nameserver

NameserverSerial
dns1.faastic.com (185.179.91.9)3
dns2.faastic.com (116.203.182.159)3

Checks

  • ✓ Serial 3 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 15m, retry 10m, expire 1d, negative TTL 4h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.faastic.com is one of the listed nameservers.
  • ✓ Contact info@faastic.com #25
    The SOA RNAME info.faastic.com means info@faastic.com.
  • ✓ Counter serial #26
    The serial 3 is a plain counter.

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

3 records at the apex

Found

Read from
185.179.91.9:53
TypeValueTTL
SOAdns1.faastic.com. info.faastic.com. 3 900 600 86400 1440014400
NSdns1.faastic.com.14400
A185.179.91.814400

Checks

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