oetinger.de

Checked 21 October 2026, 23:41 UTC · via 8.8.8.8
iAll checks passed
26 passed 0 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

a.managed-ns.com, b.managed-ns.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
a.managed-ns.com, b.managed-ns.de
NS in the zone
a.managed-ns.com, b.managed-ns.de
NameserverAddressesNetwork (AS)Glue
a.managed-ns.com192.174.68.102 2001:67c:1bc::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
b.managed-ns.de176.97.158.102 2001:67c:10b8::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT176.97.158.102 2001:67c:10b8::102

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: a.managed-ns.com, b.managed-ns.de.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 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
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .de.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a.managed-ns.com 192.174.68.102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
a.managed-ns.com 2001:67c:1bc::102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
b.managed-ns.de 176.97.158.102NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
b.managed-ns.de 2001:67c:10b8::102NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1

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: a.managed-ns.com: "RcodeZero DNS"; b.managed-ns.de: "reg-wie1".
    #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 2026084663 · primary a.managed-ns.com

Found

Primary (MNAME)
a.managed-ns.com
Contact (RNAME)
domainadmin.managed-ip.com
Serial
2026084663
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
a.managed-ns.com (192.174.68.102)2026084663
a.managed-ns.com (2001:67c:1bc::102)2026084663
b.managed-ns.de (176.97.158.102)2026084663
b.managed-ns.de (2001:67c:10b8::102)2026084663

Checks

  • ✓ Serial 2026084663 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a.managed-ns.com is one of the listed nameservers.
  • ✓ Contact domainadmin@managed-ip.com #25
    The SOA RNAME domainadmin.managed-ip.com means domainadmin@managed-ip.com.
  • ✓ Timestamp serial #26
    The serial 2026084663 is a Unix timestamp (2034-03-16 01:17 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
7324RSASHA256 (8)SHA256 AD1DD19E30275DC5…yes

DNSKEY in the zone

Key tagRoleAlgorithm
10339ZSK (256)RSASHA256 (8)
7324KSK (257)RSASHA256 (8)

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 7324 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

13 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAa.managed-ns.com. domainadmin.managed-ip.com. 2026084663 43200 7200 1209600 300300
NSa.managed-ns.com.300
NSb.managed-ns.de.300
A212.224.92.166300
MX0 oetinger-de.mail.protection.outlook.com.300
TXT"MS=ms99376975"300
TXT"d365mktkey=SmdE1hYruvS2hGTrd0W7mLsQg7xImBKqp1YPxpoxrTEx"300
TXT"d365mktkey=j3jxYCxx9zThxO2kZxWYRUWWTxrcBIRJ9zCdDzFAMiEx"300
TXT"langdock-verify=2-qqHGG-xFgIpMotoG4iP7G3ZSGzntDLipxXmikPoTA"300
TXT"extensis-domain-verification=b30417ea-b251-493b-888a-a3a1f45e4147"300
TXT"google-site-verification=mqM8TkdhWgtSHxlZfpjl9wgTCOwVm-eUd3YHfV3SQVk"300
TXT"_globalsign-domain-verification=Jp-HLLpC4NZA7UtNndC1eP0TGVNPtbpBxtYv9ptU16"300
TXT"v=spf1 ip4:217.243.208.107/32 include:spf.protection.outlook.com include:novalnet.de include:brevo.com -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