afspraakjes.be

Checked 22 October 2026, 06:03 UTC · via 8.8.8.8
!Passed with warnings
15 passed 6 warnings 0 failed 8 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

ns1.afspraakjes.com, ns2.afspraakjes.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.afspraakjes.com, ns2.afspraakjes.com
NS in the zone
ns1.afspraakjes.com, ns2.afspraakjes.com
NameserverAddressesNetwork (AS)Glue
ns1.afspraakjes.com149.210.207.37AS20857 TRANSIP-AS - Signet B.V., NL-
ns2.afspraakjes.com149.210.207.23AS20857 TRANSIP-AS - Signet B.V., NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.afspraakjes.com, ns2.afspraakjes.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 one network
    all IPv4 addresses are in 149.210.207.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 (AS20857 (TRANSIP-AS - Signet 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 .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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.afspraakjes.com 149.210.207.37NOERROR, 10 ms, authoritativenoyes / yesrefusedMicrosoft DNS 6.1.7601 (1DB15F75)
ns2.afspraakjes.com 149.210.207.23NOERROR, 11 ms, authoritativenoyes / yesrefusedMicrosoft DNS 6.1.7601 (1DB15F75)

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: ns1.afspraakjes.com: "Microsoft DNS 6.1.7601 (1DB15F75)"; ns2.afspraakjes.com: "Microsoft DNS 6.1.7601 (1DB15F75)". Hide or replace the version string.
    #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

warn

serial 14 · primary genk

Found

Primary (MNAME)
genk
Contact (RNAME)
hostmaster
Serial
14
Refresh / retry
900 s / 600 s
Expire
86400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.afspraakjes.com (149.210.207.37)14
ns2.afspraakjes.com (149.210.207.23)14

Checks

  • ✓ Serial 14 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 1h.
    #23
  • i
    Hidden master (not resolvable)
    The primary nameserver genk is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • !
    Invalid contact address
    The SOA RNAME "hostmaster" is not a valid mailbox (expected e.g. hostmaster.example.com).
    #25
  • ✓ Counter serial #26
    The serial 14 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

4 records at the apex

Found

Read from
149.210.207.37:53
TypeValueTTL
SOAgenk. hostmaster. 14 900 600 86400 36003600
NSns2.afspraakjes.com.3600
NSns1.afspraakjes.com.3600
A149.210.198.1353600

Checks

  • ✓ TTLs within range #32
    TTLs: A 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