Domain report: berlios.de

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

launch1.spaceship.net, launch2.spaceship.net

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: launch1.spaceship.net, launch2.spaceship.net
NS in the zone: launch1.spaceship.net, launch2.spaceship.net

Nameserver	Addresses	Network (AS)	Glue
launch1.spaceship.net	162.159.26.38 2400:cb00:2049:1::a29f:1a26	AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US	-
launch2.spaceship.net	162.159.27.32 2400:cb00:2049:1::a29f:1b20	AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: launch1.spaceship.net, launch2.spaceship.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.
i

One address family in one network

all IPv6 addresses are in 2400:cb00:2049::/48, while the other address family is spread over several networks.

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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

warn

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
launch1.spaceship.net 162.159.26.38	NOERROR, 96 ms, authoritative	no	yes / yes	refused	2026.10.8
launch1.spaceship.net 2400:cb00:2049:1::a29f:1a26	NOERROR, 97 ms, authoritative	no	yes / yes	refused	2026.10.8
launch2.spaceship.net 162.159.27.32	NOERROR, 29 ms, authoritative	no	yes / yes	refused	2026.10.8
launch2.spaceship.net 2400:cb00:2049:1::a29f:1b20	NOERROR, 29 ms, authoritative	no	yes / yes	refused	2026.10.8

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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: launch1.spaceship.net: "2026.10.8"; launch2.spaceship.net: "2026.10.8". Hide or replace the version string.

#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 1790584895 · primary launch1.spaceship.net

Found

Primary (MNAME): launch1.spaceship.net
Contact (RNAME): support.spaceship.com
Serial: 1790584895
Refresh / retry: 43200 s / 3600 s
Expire: 604800 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
launch1.spaceship.net (162.159.26.38)	1790584895
launch1.spaceship.net (2400:cb00:2049:1::a29f:1a26)	1790584895
launch2.spaceship.net (162.159.27.32)	1790584895
launch2.spaceship.net (2400:cb00:2049:1::a29f:1b20)	1790584895

Checks

✓ Serial 1790584895 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 12h, retry 1h, expire 7d, negative TTL 1h.
✓ Primary is a public nameserver #24

The primary nameserver launch1.spaceship.net is one of the listed nameservers.
✓ Contact support@spaceship.com #25

The SOA RNAME support.spaceship.com means support@spaceship.com.
✓ Timestamp serial #26

The serial 1790584895 is a Unix timestamp (2026-09-28 08:41 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 tag	Algorithm	Digest	Matches a key
7613	ECDSAP256SHA256 (13)	SHA256 7ED951713F7674A1…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
7613	KSK (257)	ECDSAP256SHA256 (13)
55491	ZSK (256)	ECDSAP256SHA256 (13)

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 7613 (SHA256).
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13).
✓ 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

6 records at the apex

Found

Read from: 162.159.26.38:53

Type	Value	TTL
SOA	launch1.spaceship.net. support.spaceship.com. 1790584895 43200 3600 604800 3600	1800
NS	launch1.spaceship.net.	1800
NS	launch2.spaceship.net.	1800
A	63.250.43.137	300
A	63.250.43.136	300
TXT	"v=spf1 include:spf.easywp.com ~all"	300

Checks

✓ TTLs within range #32

TTLs: A 5m, NS 30m. The NS TTL at the parent is 1d and in the zone 30m; resolvers may use either.
✓ 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