rapidmail.de

Checked 22 October 2026, 00:00 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.nodesecure.com, ns2.nodesecure.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.nodesecure.com, ns2.nodesecure.de
NS in the zone
ns1.nodesecure.com, ns2.nodesecure.de
NameserverAddressesNetwork (AS)Glue
ns1.nodesecure.com192.174.68.102 2001:67c:1bc::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.nodesecure.de176.97.158.102 2001:67c:10b8::102AS1921 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.nodesecure.com, ns2.nodesecure.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
ns1.nodesecure.com 192.174.68.102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.nodesecure.com 2001:67c:1bc::102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.nodesecure.de 176.97.158.102NOERROR, 32 ms, authoritativenoyes / yesrefused-
ns2.nodesecure.de 2001:67c:10b8::102NOERROR, 56 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.nodesecure.com: "RcodeZero DNS"; ns2.nodesecure.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

warn

serial 2026102113 · primary ns1.nodesecure.com

Found

Primary (MNAME)
ns1.nodesecure.com
Contact (RNAME)
it-ops.rapidmail.de
Serial
2026102113
Refresh / retry
43200 s / 3600 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns1.nodesecure.com (192.174.68.102)2026102113
ns1.nodesecure.com (2001:67c:1bc::102)2026102113
ns2.nodesecure.de (176.97.158.102)2026102113
ns2.nodesecure.de (2001:67c:10b8::102)2026102113

Checks

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

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

24 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAns1.nodesecure.com. it-ops.rapidmail.de. 2026102113 43200 3600 1209600 180180
NSns1.nodesecure.com.180
NSns2.nodesecure.de.180
A37.208.111.610800
A37.208.111.710800
MX1 aspmx.l.google.com.360
MX5 alt1.aspmx.l.google.com.360
MX5 alt2.aspmx.l.google.com.360
MX10 alt3.aspmx.l.google.com.360
MX10 alt4.aspmx.l.google.com.360
TXT"unbounce 300530"3600
TXT"5f2d0004b7f54e69b446058e2c8f6de5"3600
TXT"anthropic-domain-verification-7vxcar=OjRCfyyCEut0LWCDSlj3TfNVZ"3600
TXT"yahoo-verification-key=bjAq3SQgr8z8eYHPf/LXtNjKqg7nLV3M1x/4H2aAkX8="3600
TXT"yahoo-verification-key=yYFc7x8gYRi6eKYumzJvX6W6kzmNRSJg5xw//OSTsW4="3600
TXT"google-site-verification=QJIvyWcGUf94D6yTInT-2CKe03iNGAi2STMZhoRkMx8"3600
TXT"google-site-verification=USaoGZM6bLhK4gRTYSaOx47jQeAPJqaxsesBQczficg"3600
TXT"google-site-verification=bbIFoWD80-HWxgNRj_uFSi0Wn7IgsNcTmCJmPTJXfrI"3600
TXT"google-site-verification=dv1pvoS5poNia4SP2Kmrg0WevFTCDI97WOqp-KvU1Qg"3600
TXT"google-site-verification=gm6hmI055agS5T5ScT4nHRAVWbhyWnfDHqHFSRPB_9g"3600
TXT"google-site-verification=n2Om3nJ7PpgiQKq5e9z6UUzZ5W_drqKxsmYxtUcEfDM"3600
TXT"ahrefs-site-verification_c5f484bedbf728c4f97ad47b810707ba300d3cc07ce6a74d79172d23bb6e56bc"3600
TXT"atlassian-domain-verification=Hd0IU7P8ZQaBy7JLrird/Xtze9ofyHpCPVFeO/ouCpoS3uXvw1Jy0HXfd4W9RoWx"3600
TXT"v=spf1 mx ip4:193.238.61.128/25 ip4:193.238.61.126 ip4:89.191.89.0/24 ip4:193.238.60.130 ip4:89.191.67.198 ip4:89.191.68.224 include:spf.rmh1.net ip4:46.253.16.30/31 ip4:46.253.16.32/28 ip4:46.253.16.48/29 ip4:46.253.16.56/30 ip4:185.71.124.0/24 ip4:185.7" "1.125.0/24 ip4:185.71.126.0/24 ip4:185.71.127.0/24 ip4:37.208.111.4 ip4:37.208.109.131 include:helpscoutemail.com include:_spf.google.com include:_spf.mail03-userengage.com include:25089048.spf07.hubspotemail.net ~all"3600

Checks

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