SurfaceMap › u › uk.linkedin.com

uk.linkedin.com

Checked 2026-10-22 11:15 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

warn

25 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC ✓Records

Problems

  • !
    Software version disclosed
    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.
    #17
  • !
    Serials differ
    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); 1789612855 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.
    #22
  • !
    Unusual SOA timers
    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.
    #23
  • !
    Not signed
    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.
    #27

Recent checks

!

Full report

Domain & DNS report for uk.linkedin.com ›

Mail

error

9 passed 1 warn 2 failed 1 errors

lookups failed for dnssec; results are incomplete

Areas

✗SPF ✓DMARC ✗DKIM iDNSSEC !MX ✓BIMI

Problems

  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.uk.linkedin.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    No MX records
    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 .").
    #9

Recent checks

!

Full report

Mail report for uk.linkedin.com ›