olympics.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1-17.akam.net: "41824.6"; ns1-17.akam.net: "41824.11"; ns1-239.akam.net: "41824.7"; ns1-239.akam.net: "41824.8"; usc4.akam.net: "48878.26"; use4.akam.net: "48878.32"; use5.akam.net: "48878.27"; usw1.akam.net: "41824.8"; usw2.akam.net: "48878.32". Hide or replace the version string.

SOA · The nameservers serve different versions of the zone: 2015010247 on ns11.constellix.com (96.45.80.1), ns11.constellix.com (2600:180a:1001::1), ns21.constellix.com (46.31.236.1), ns21.constellix.com (2600:180b:2001::1), ns31.constellix.com (43.247.170.1), ns31.constellix.com (2600:180c:3001::1), ns41.constellix.net (96.45.81.1), ns41.constellix.net (2600:180a:4001::1), ns51.constellix.net (46.31.237.1), ns51.constellix.net (2600:180b:5001::1), ns61.constellix.net (43.247.171.1), ns61.constellix.net (2600:180c:6001::1); 2020112701 on ns1-17.akam.net (193.108.91.17), ns1-17.akam.net (2600:1401:2::11), ns1-239.akam.net (193.108.91.239), ns1-239.akam.net (2600:1401:2::ef), usc4.akam.net (184.26.160.65), use4.akam.net (23.211.133.65), use5.akam.net (2.16.40.64), use5.akam.net (2600:1403:a::40), usw1.akam.net (23.61.199.66), usw2.akam.net (184.26.161.64). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

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), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

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

MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").