kfzgewerbe.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
19 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

info

ns1.networkteam.com, ns2.networkteam.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.networkteam.com, ns2.networkteam.com
NS in the zone
ns1.networkteam.com, ns2.networkteam.com
NameserverAddressesNetwork (AS)Glue
ns1.networkteam.com212.51.11.77AS25415 ADDIX-AS - ADDIX GmbH, DE-
ns2.networkteam.com212.51.17.255 2a01:780:c000:2::2AS25415 ADDIX-AS - ADDIX GmbH, DE AS25415 ADDIX-AS - ADDIX GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.networkteam.com, ns2.networkteam.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 different networks #10
    The nameservers are spread over 2 IPv4 /24s and 1 IPv6 /48.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS25415 (ADDIX-AS - ADDIX GmbH, DE): 3 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.networkteam.com.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.networkteam.com 212.51.11.77NOERROR, 18 ms, authoritativenoyes / yesrefused-
ns2.networkteam.com 212.51.17.255NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14
ns2.networkteam.com 2a01:780:c000:2::2NOERROR, 20 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14

Checks

  • ✓ All respond #14
    All 3 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: ns2.networkteam.com: "PowerDNS Authoritative Server 4.1.14". 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 2025051401 · primary ns1.networkteam.com

Found

Primary (MNAME)
ns1.networkteam.com
Contact (RNAME)
admin.networkteam.com
Serial
2025051401
Refresh / retry
3600 s / 600 s
Expire
1209600 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.networkteam.com (212.51.11.77)2025051401
ns2.networkteam.com (212.51.17.255)2025051401
ns2.networkteam.com (2a01:780:c000:2::2)2025051401

Checks

  • ✓ Serial 2025051401 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 10m, expire 14d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.networkteam.com is one of the listed nameservers.
  • ✓ Contact admin@networkteam.com #25
    The SOA RNAME admin.networkteam.com means admin@networkteam.com.
  • ✓ Date-based serial #26
    The serial 2025051401 follows the YYYYMMDDnn convention (2025-05-14).

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

7 records at the apex

Found

Read from
212.51.11.77:53
TypeValueTTL
SOAns1.networkteam.com. admin.networkteam.com. 2025051401 3600 600 1209600 603600
NSns2.networkteam.com.3600
NSns1.networkteam.com.3600
A212.51.30.903600
MX10 kfzgewerbe-de.mail.protection.outlook.com.3600
TXT"MS=ms42626999"3600
TXT"v=spf1 include:mail.networkteam.com mx include:spf.mailjet.com include:spf.crsend.com include:spf.protection.outlook.com include:_spf.zimpel.de a:kundenmail.aktivcomm.de ip4:195.201.79.144 ip4:213.23.74.48/28 ip4:213.23.36.118 ip4:94.130.203.167 -all"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.
  • ✓ 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