SurfaceMap › k › king.com

king.com

Checked 2026-10-22 09:31 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

warn

27 passed 3 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 1h, expire 3d, negative TTL 5m.
    #23
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 1 iteration and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 6h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for king.com ›

Mail

fail

24 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-00381101.gslb.pphosted.com, mxb-00381101.gslb.pphosted.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (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 king.com ›