intersolar.de

Checked 21 October 2026, 23:00 UTC · via 8.8.8.8
!Passed with warnings
20 passed 1 warning 0 failed 8 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

sec1.rcode0.net, sec2.rcode0.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
sec1.rcode0.net, sec2.rcode0.net
NS in the zone
sec1.rcode0.net, sec2.rcode0.net
NameserverAddressesNetwork (AS)Glue
sec1.rcode0.net192.174.68.100 2001:67c:1bc::100AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
sec2.rcode0.net176.97.158.100 2001:67c:10b8::100AS1921 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: sec1.rcode0.net, sec2.rcode0.net.
    #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 .net
    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
sec1.rcode0.net 192.174.68.100NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
sec1.rcode0.net 2001:67c:1bc::100NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
sec2.rcode0.net 176.97.158.100NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
sec2.rcode0.net 2001:67c:10b8::100NOERROR, 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: sec1.rcode0.net: "RcodeZero DNS"; sec2.rcode0.net: "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 2026100701 · primary sec1.rcode0.net

Found

Primary (MNAME)
sec1.rcode0.net
Contact (RNAME)
hostmaster.mpcnet.de
Serial
2026100701
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
sec1.rcode0.net (192.174.68.100)2026100701
sec1.rcode0.net (2001:67c:1bc::100)2026100701
sec2.rcode0.net (176.97.158.100)2026100701
sec2.rcode0.net (2001:67c:10b8::100)2026100701

Checks

  • ✓ Serial 2026100701 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver sec1.rcode0.net is one of the listed nameservers.
  • ✓ Contact hostmaster@mpcnet.de #25
    The SOA RNAME hostmaster.mpcnet.de means hostmaster@mpcnet.de.
  • ✓ Date-based serial #26
    The serial 2026100701 follows the YYYYMMDDnn convention (2026-10-07).

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

13 records at the apex

Found

Read from
192.174.68.100:53
TypeValueTTL
SOAsec1.rcode0.net. hostmaster.mpcnet.de. 2026100701 10800 3600 604800 3003600
NSsec1.rcode0.net.3600
NSsec2.rcode0.net.3600
A82.96.75.164300
MX10 mx01.hornetsecurity.com.300
MX20 mx02.hornetsecurity.com.300
MX30 mx03.hornetsecurity.com.300
MX40 mx04.hornetsecurity.com.300
TXT"MS=ms16808228"300
TXT"brevo-code:e13c46f0806f3862ea3a89c93cfb9a74"300
TXT"facebook-domain-verification=vy6jk4fyvn80axa478o4ismxnxb84n"300
TXT"google-site-verification=WKlvavLXhIu4PZQGrfh2AG9XOWj-kw93GZtLeMngeJo"300
TXT"v=spf1 include:spf.intersolar.de include:mpcnet.de include:spf.nl2go.com include:spf.protection.outlook.com include:spf.hornetsecurity.com -all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, 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.
  • 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