ssb-ag.de

Checked 22 October 2026, 00:30 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 warnings 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

warn

dns02.ssb-ag.de, dns03.ssb-ag.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns02.ssb-ag.de, dns03.ssb-ag.de
NS in the zone
dns02.ssb-ag.de, dns03.ssb-ag.de
NameserverAddressesNetwork (AS)Glue
dns02.ssb-ag.de193.105.223.200AS51215 SSB-AG - Stuttgarter Strassenbahnen AG, DE193.105.223.200
dns03.ssb-ag.de94.186.155.242AS48918 GLOBALWAYS - Globalways GmbH, DE94.186.155.242

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns02.ssb-ag.de, dns03.ssb-ag.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: dns02.ssb-ag.de, dns03.ssb-ag.de.
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS48918 (GLOBALWAYS - Globalways GmbH, DE): 1 address; AS51215 (SSB-AG - Stuttgarter Strassenbahnen AG, DE): 1 address.
  • 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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns02.ssb-ag.de 193.105.223.200NOERROR, 12 ms, authoritativenoyes / yesrefused-
dns03.ssb-ag.de 94.186.155.242NOERROR, 7 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026101601 · primary dns01.ssb-ag.de

Found

Primary (MNAME)
dns01.ssb-ag.de
Contact (RNAME)
dnsteam.mail.ssb-ag.de
Serial
2026101601
Refresh / retry
300 s / 120 s
Expire
432000 s
Negative TTL
120 s

Serial per nameserver

NameserverSerial
dns02.ssb-ag.de (193.105.223.200)2026101601
dns03.ssb-ag.de (94.186.155.242)2026101601

Checks

  • ✓ Serial 2026101601 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; expire 5d is shorter than 7d; secondaries stop answering too soon when the primary is down; negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 5m, retry 2m, expire 5d, negative TTL 2m.
    #23
  • i
    Hidden master (not resolvable)
    The primary nameserver dns01.ssb-ag.de is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact dnsteam@mail.ssb-ag.de #25
    The SOA RNAME dnsteam.mail.ssb-ag.de means dnsteam@mail.ssb-ag.de.
  • ✓ Date-based serial #26
    The serial 2026101601 follows the YYYYMMDDnn convention (2026-10-16).

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

14 records at the apex

Found

Read from
193.105.223.200:53
TypeValueTTL
SOAdns01.ssb-ag.de. dnsteam.mail.ssb-ag.de. 2026101601 300 120 432000 12086400
NSdns03.ssb-ag.de.86400
NSdns02.ssb-ag.de.86400
A3.121.244.5386400
MX10 ssbag-de0i.mail.protection.outlook.com.86400
TXT"swisssign-check=t60BX1uGKtju9sOE_tEG0RWSV2A"3600
TXT"cisco-ci-domain-verification=5a879b1ca972d07ced5ccfb4a9d563072bf709dfaa470d90f14410014cd96c7a"3600
TXT"WKIw12EPQN0VFQAlM1uRQMU7SFqXDbYp8nz0cEnsnA/EOUMTJ5OIVLuYQnRuqZjsZpUD2qYlqjvj2JRpRpMbfQ=="3600
TXT"4ZkPecssp4P5wn/L8zwIlgBnIQmZGc0AIEohbs47rg2ZCWVV5lUDKqbHT8yI9KWof55eDZs6IJRh1U+5h5uIWQ=="3600
TXT"MS=ms78352328"3600
TXT"atlassian-sending-domain-verification=54ea367f-fa9c-450c-b211-5f19635ce8b7"3600
TXT"atlassian-domain-verification=JW58WNNDAg52fi7SXZ1I0En00isUzz8Nvp8IfNsbZco9emz7lUYqG2XbdUDFTitI"3600
TXT"v=spf1 include:spf.protection.outlook.com a:exosmtp.ssb-ag.de a:mailx3.ssb-ag.de ip4:193.105.223.99 ip4:193.105.223.202 ip4:35.156.150.49 ip4:18.194.159.172 ip4:18.198.163.238 include:spf.mail.aas.services include:spf.mandrillapp.com -all"3600
TXT"google-site-verification=uOM8UjhPQ7ZglrAKc06PfWSCsC3LZEEpjJ4mOsvwMKw"3600

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.
  • ✓ 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