kamazutra.be

Checked 22 October 2026, 06:41 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 0 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

dns1.realtime.at, dns2.realtime.at

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns1.realtime.at, dns2.realtime.at
NS in the zone
dns1.realtime.at, dns2.realtime.at
NameserverAddressesNetwork (AS)Glue
dns1.realtime.at5.9.10.78 2a01:4f8:b13:1001::2AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
dns2.realtime.at95.216.194.108 2a01:4f9:c010:3066::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 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.realtime.at, dns2.realtime.at.
    #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 (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 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 .at
    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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.realtime.at 5.9.10.78NOERROR, 2 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:03 by root@localhost)
dns1.realtime.at 2a01:4f8:b13:1001::2NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:03 by root@localhost)
dns2.realtime.at 95.216.194.108NOERROR, 26 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
dns2.realtime.at 2a01:4f9:c010:3066::1NOERROR, 25 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.realtime.at: "PowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:03 by root@localhost)"; dns2.realtime.at: "PowerDNS Authoritative Server 4.7.3". 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

pass

serial 2026050501 · primary dns1.realtime.at

Found

Primary (MNAME)
dns1.realtime.at
Contact (RNAME)
hostmaster.realtime.at
Serial
2026050501
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns1.realtime.at (5.9.10.78)2026050501
dns1.realtime.at (2a01:4f8:b13:1001::2)2026050501
dns2.realtime.at (95.216.194.108)2026050501
dns2.realtime.at (2a01:4f9:c010:3066::1)2026050501

Checks

  • ✓ Serial 2026050501 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.realtime.at is one of the listed nameservers.
  • ✓ Contact hostmaster@realtime.at #25
    The SOA RNAME hostmaster.realtime.at means hostmaster@realtime.at.
  • ✓ Date-based serial #26
    The serial 2026050501 follows the YYYYMMDDnn convention (2026-05-05).

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

6 records at the apex

Found

Read from
5.9.10.78:53
TypeValueTTL
SOAdns1.realtime.at. hostmaster.realtime.at. 2026050501 28800 7200 604800 8640086400
NSdns1.realtime.at.86400
NSdns2.realtime.at.86400
A185.53.177.3186400
MX10 .86400
TXT"v=spf1 mx -all"86400

Checks

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