SurfaceMap › s › secondlife.com

secondlife.com

Checked 2026-10-22 10:35 UTC · first added 2026-10-21
✗Problems found Score 59 of 100

Domain & DNS

warn

23 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: a1-228.akam.net: "41824.10"; a1-228.akam.net: "41824.5"; a18-67.akam.net: "48878.32"; a18-67.akam.net: "48878.29"; a24-64.akam.net: "48878.31"; a24-64.akam.net: "48878.29"; a3-65.akam.net: "41824.6"; a3-65.akam.net: "41824.4"; a4-66.akam.net: "48878.29"; a4-66.akam.net: "48878.33"; a9-67.akam.net: "41824.6". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 10m, expire 14d, 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for secondlife.com ›

Mail

fail

22 passed 3 warn 2 failed

Areas

✗SPF ✗DMARC !DKIM !DNSSEC ✓MX !TLS iBIMI

Problems

  • ✗
    No 'all' mechanism
    SPF · SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.
    #3
  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    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.
    #32

Recent checks

✗

Full report

Mail report for secondlife.com ›