congstar.de

Checked 21 October 2026, 22:10 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 0 failed 6 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

dns1.telekom.de, dns2.telekom.de, ns1.telekom.net, pns.dtag.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.telekom.de, dns2.telekom.de, ns1.telekom.net, pns.dtag.de
NS in the zone
dns1.telekom.de, dns2.telekom.de, ns1.telekom.net, pns.dtag.de
NameserverAddressesNetwork (AS)Glue
dns1.telekom.de194.25.225.19AS3320 DTAG - Deutsche Telekom AG, DE194.25.225.19
dns2.telekom.de194.25.225.3AS3320 DTAG - Deutsche Telekom AG, DE194.25.225.3
ns1.telekom.net212.185.24.65 2003:180:a:1000::53AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE-
pns.dtag.de194.25.0.125 2003:40:8000::100AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE194.25.0.125 2003:40:8000::100

Checks

  • ✓ 4 nameservers #6
    Delegated to dns1.telekom.de, dns2.telekom.de, ns1.telekom.net, pns.dtag.de.
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS3320 (DTAG - Deutsche Telekom AG, DE): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: dns1.telekom.de, dns2.telekom.de.
    #13

Nameservers

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.telekom.de 194.25.225.19NOERROR, 10 ms, authoritativenoyes / yesrefused-
dns2.telekom.de 194.25.225.3NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns1.telekom.net 212.185.24.65NOERROR, 3 ms, authoritativenoyes / yesrefusedDomainNameServer
ns1.telekom.net 2003:180:a:1000::53NOERROR, 4 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 194.25.0.125NOERROR, 10 ms, authoritativenoyes / yesrefusedDomainNameServer
pns.dtag.de 2003:40:8000::100NOERROR, 8 ms, authoritativenoyes / yesrefusedDomainNameServer

Checks

  • ✓ All respond #14
    All 6 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: ns1.telekom.net: "DomainNameServer"; pns.dtag.de: "DomainNameServer".
    #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 393 · primary dns1.telekom.de

Found

Primary (MNAME)
dns1.telekom.de
Contact (RNAME)
dnsadmin.t-systems.com
Serial
393
Refresh / retry
10800 s / 1800 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
dns1.telekom.de (194.25.225.19)393
dns2.telekom.de (194.25.225.3)393
ns1.telekom.net (212.185.24.65)393
ns1.telekom.net (2003:180:a:1000::53)393
pns.dtag.de (194.25.0.125)393
pns.dtag.de (2003:40:8000::100)393

Checks

  • ✓ Serial 393 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 7d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.telekom.de is one of the listed nameservers.
  • ✓ Contact dnsadmin@t-systems.com #25
    The SOA RNAME dnsadmin.t-systems.com means dnsadmin@t-systems.com.
  • ✓ Counter serial #26
    The serial 393 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

12 records at the apex

Found

Read from
194.25.225.19:53
TypeValueTTL
SOAdns1.telekom.de. dnsadmin.t-systems.com. 393 10800 1800 604800 9003600
NSdns2.telekom.de.3600
NSns1.telekom.net.3600
NSpns.dtag.de.3600
NSdns1.telekom.de.3600
A194.150.228.433600
MX10 mail.congstar.de.3600
TXT"google-site-verification=Fx5owvEeUOFaQP8gaJAijNTqAo5T0rD5gUGCV7XqU-A"3600
TXT"v=spf1 mx ip4:194.25.225.128/26 ip4:194.25.225.192/26 ip4:80.158.70.128/30 exists:%{i}.spf.telekom.com include:_spf.salesforce.com ~all"3600
TXT"google-site-verification=tOPd1Kz05VB16KTw6eCDG_ok2T0zUDz0ELnhb-gRHsY"3600
TXT"qv5g3l1kk9nbkrx0l92v4xdgdnv5dygy"3600
TXT"vlz4d3svk32nlj1g8085wjs0tds8vpxs"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