mpfs.de

Checked 21 October 2026, 23:30 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 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.namesecure.de, ns2.namesecure.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.namesecure.de, ns2.namesecure.de
NS in the zone
ns1.namesecure.de, ns2.namesecure.de
NameserverAddressesNetwork (AS)Glue
ns1.namesecure.de193.227.117.225 2a04:2b00:14cc::225AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.namesecure.de194.50.187.225 2a04:2b00:14dd::225AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.namesecure.de, ns2.namesecure.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
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.namesecure.de 193.227.117.225NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.namesecure.de 2a04:2b00:14cc::225NOERROR, 7 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.namesecure.de 194.50.187.225NOERROR, 14 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.namesecure.de 2a04:2b00:14dd::225NOERROR, 14 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: ns1.namesecure.de: "RcodeZero DNS"; ns2.namesecure.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 2024112600 · primary ns1.namesecure.de

Found

Primary (MNAME)
ns1.namesecure.de
Contact (RNAME)
hostmaster.namesecure.de
Serial
2024112600
Refresh / retry
14400 s / 7200 s
Expire
604800 s
Negative TTL
28800 s

Serial per nameserver

NameserverSerial
ns1.namesecure.de (193.227.117.225)2024112600
ns1.namesecure.de (2a04:2b00:14cc::225)2024112600
ns2.namesecure.de (194.50.187.225)2024112600
ns2.namesecure.de (2a04:2b00:14dd::225)2024112600

Checks

  • ✓ Serial 2024112600 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 7d, negative TTL 8h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.namesecure.de is one of the listed nameservers.
  • ✓ Contact hostmaster@namesecure.de #25
    The SOA RNAME hostmaster.namesecure.de means hostmaster@namesecure.de.
  • ✓ Date-based serial #26
    The serial 2024112600 follows the YYYYMMDDnn convention (2024-11-26).

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

warn

7 records at the apex

Found

Read from
193.227.117.225:53
TypeValueTTL
SOAns1.namesecure.de. hostmaster.namesecure.de. 2024112600 14400 7200 604800 2880086400
NSns1.namesecure.de.60
NSns2.namesecure.de.60
A23.88.92.13060
AAAA2a01:4f8:1061:1080::260
MX50 mail.mpfs.de.60
TXT"v=spf1 mx a ip4:188.40.58.247 ip4:23.88.92.130 ip6:2a01:4f8:1061:1080::2 ~all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; resolvers may use either.
    #32
  • ✓ 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