vueling.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-17.akam.net: "41824.10"; a1-17.akam.net: "41824.4"; a13-64.akam.net: "41824.7"; a13-64.akam.net: "41824.6"; a2-65.akam.net: "48878.26"; a4-66.akam.net: "48878.29"; a4-66.akam.net: "48878.30"; a7-67.akam.net: "41824.11"; a7-67.akam.net: "41824.4"; a8-64.akam.net: "48878.33". Hide or replace the version string.

SOA · refresh 1m is outside 20m–1d; retry 1m should be shorter than refresh 1m; expire 1m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1m must be longer than refresh + retry; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1m, retry 1m, expire 1m, negative TTL 1m.

DNSSEC · 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.

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

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (1024 bits), 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.