fluter.de

Checked 21 October 2026, 22:30 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 7 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de 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
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

warn

ns.teamware-gmbh.de, ns3.teamware-gmbh.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.teamware-gmbh.de, ns3.teamware-gmbh.de
NS in the zone
ns.teamware-gmbh.de, ns3.teamware-gmbh.de
NameserverAddressesNetwork (AS)Glue
ns.teamware-gmbh.de212.29.0.1AS12337 NORIS-NETWORK - noris network AG, DE212.29.0.1
ns3.teamware-gmbh.de217.19.160.3AS12337 NORIS-NETWORK - noris network AG, DE217.19.160.3 2a03:ad00:0:4::f3

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.teamware-gmbh.de, ns3.teamware-gmbh.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns3.teamware-gmbh.de (glue 217.19.160.3, 2a03:ad00:0:4::f3, zone 217.19.160.3). Update the glue at your registrar.
    #8
  • ✓ 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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS12337 (NORIS-NETWORK - noris network AG, DE): 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 .de
    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
ns.teamware-gmbh.de 212.29.0.1NOERROR, 8 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.7-Ubuntu
ns3.teamware-gmbh.de 217.19.160.3NOERROR, 7 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.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: ns.teamware-gmbh.de: "9.18.39-0ubuntu0.24.04.7-Ubuntu"; ns3.teamware-gmbh.de: "9.18.39-0ubuntu0.24.04.7-Ubuntu". 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 2026030451 · primary ns.teamware-gmbh.de

Found

Primary (MNAME)
ns.teamware-gmbh.de
Contact (RNAME)
hostmaster.teamware-gmbh.de
Serial
2026030451
Refresh / retry
86400 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.teamware-gmbh.de (212.29.0.1)2026030451
ns3.teamware-gmbh.de (217.19.160.3)2026030451

Checks

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

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
3 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
10001ECDSAP256SHA256 (13)SHA256 5E5966A9EF6C9B5B…yes

DNSKEY in the zone

Key tagRoleAlgorithm
10001KSK (257)ECDSAP256SHA256 (13)
54721ZSK (256)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 10001 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-03 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-03 08:08 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

9 records at the apex

Found

Read from
212.29.0.1:53
TypeValueTTL
SOAns.teamware-gmbh.de. hostmaster.teamware-gmbh.de. 2026030451 86400 3600 604800 864003600
NSns.teamware-gmbh.de.3600
NSns3.teamware-gmbh.de.3600
A212.29.25.1193600
MX50 mail01.bpb.de.3600
TXT"v=spf1 mx:mail01.bpb.de include:spf.bpb.de -all"3600
CAA0 issue "digicert.com"3600
CAA0 issue "letsencrypt.org"3600
CAA0 iodef "mailto:hostmaster@tw.de"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, letsencrypt.org.