spaceship.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: launch1.spaceship.com: "48878.33"; launch1.spaceship.com: "48878.32"; launch1.spaceship.com: "2026.10.8"; launch1.spaceship.com: "41824.9"; launch1.spaceship.com: "41824.7"; launch1.spaceship.com: "48878.31"; launch2.spaceship.com: "41824.4"; launch2.spaceship.com: "48878.29"; launch2.spaceship.com: "2026.10.8"; launch2.spaceship.com: "41824.10"; launch2.spaceship.com: "41824.9"; launch2.spaceship.com: "41824.7". Hide or replace the version string.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 30m; resolvers may use either.

MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.spacemail.com, mx2.spacemail.com

DNSSEC · DNSKEY signatures expire at 2026-10-25T01:40:17Z (in 63h0m0s). Check that re-signing works.

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.