licdn.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2-42.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-42.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.

SOA · The nameservers serve different versions of the zone: 1 on ns1-42.azure-dns.com (150.171.10.42), ns2-42.azure-dns.net (150.171.16.42), ns3-42.azure-dns.org (13.107.222.42), ns4-42.azure-dns.info (13.107.206.42); 1659352058 on dns1.p09.nsone.net (198.51.44.9), dns1.p09.nsone.net (2620:4d:4000:6259:7:9:0:1), dns2.p09.nsone.net (198.51.45.9), dns2.p09.nsone.net (2a00:edc0:6259:7:9::2), dns3.p09.nsone.net (198.51.44.73), dns3.p09.nsone.net (2620:4d:4000:6259:7:9:0:3), dns4.p09.nsone.net (198.51.45.73), dns4.p09.nsone.net (2a00:edc0:6259:7:9::4). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 10m, expire 7d, 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.

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 .").