tochat.be

Checked 22 October 2026, 07:20 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

warn

ns.dinahosting.com, ns2.dinahosting.com, ns3.dinahosting.com, ns4.dinahosting.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.dinahosting.com, ns2.dinahosting.com, ns3.dinahosting.com, ns4.dinahosting.com
NS in the zone
ns.dinahosting.com, ns2.dinahosting.com, ns3.dinahosting.com, ns4.dinahosting.com
NameserverAddressesNetwork (AS)Glue
ns.dinahosting.com185.192.220.10AS42612 DINAHOSTING-AS - DinaHosting S.L., ES-
ns2.dinahosting.com185.192.221.10AS42612 DINAHOSTING-AS - DinaHosting S.L., ES-
ns3.dinahosting.com185.192.222.10AS42612 DINAHOSTING-AS - DinaHosting S.L., ES-
ns4.dinahosting.com185.192.223.10AS42612 DINAHOSTING-AS - DinaHosting S.L., ES-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns.dinahosting.com, ns2.dinahosting.com, ns3.dinahosting.com, ns4.dinahosting.com.
  • ✓ 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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS42612 (DINAHOSTING-AS - DinaHosting S.L., ES): 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.dinahosting.com 185.192.220.10NOERROR, 13 ms, authoritativenoyes / yesrefusedDina DNS Server
ns2.dinahosting.com 185.192.221.10NOERROR, 30 ms, authoritativenoyes / yesrefusedDina DNS Server
ns3.dinahosting.com 185.192.222.10NOERROR, 13 ms, authoritativenoyes / yesrefusedDina DNS Server
ns4.dinahosting.com 185.192.223.10NOERROR, 14 ms, authoritativenoyes / yesrefusedDina DNS Server

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: ns.dinahosting.com: "Dina DNS Server"; ns2.dinahosting.com: "Dina DNS Server"; ns3.dinahosting.com: "Dina DNS Server"; ns4.dinahosting.com: "Dina DNS Server".
    #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 2025030201 · primary ns.dinahosting.com

Found

Primary (MNAME)
ns.dinahosting.com
Contact (RNAME)
dnsadmin.dinahosting.com
Serial
2025030201
Refresh / retry
3600 s / 120 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns.dinahosting.com (185.192.220.10)2025030201
ns2.dinahosting.com (185.192.221.10)2025030201
ns3.dinahosting.com (185.192.222.10)2025030201
ns4.dinahosting.com (185.192.223.10)2025030201

Checks

  • ✓ Serial 2025030201 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 2m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.dinahosting.com is one of the listed nameservers.
  • ✓ Contact dnsadmin@dinahosting.com #25
    The SOA RNAME dnsadmin.dinahosting.com means dnsadmin@dinahosting.com.
  • ✓ Date-based serial #26
    The serial 2025030201 follows the YYYYMMDDnn convention (2025-03-02).

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

9 records at the apex

Found

Read from
185.192.220.10:53
TypeValueTTL
SOAns.dinahosting.com. dnsadmin.dinahosting.com. 2025030201 3600 120 1209600 300300
NSns4.dinahosting.com.300
NSns.dinahosting.com.300
NSns3.dinahosting.com.300
NSns2.dinahosting.com.300
A82.98.171.202300
MX10 mail.tochat.be.300
TXT"google-site-verification=WK-IbcXnBuJ-aumVykC9jvzEz-bVaVX33Ih-Fsp1nGI"300
TXT"v=spf1 a mx ~all"300

Checks

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