SurfaceMap › s › sanook.com

sanook.com

Checked 2026-10-22 10:34 UTC · first added 2026-10-21
!Passed with warnings Score 73 of 100

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns01.sanookonline.net, ns02.sanookonline.net, ns03.sanookonline.net, ns04.sanookonline.net. ns-1078.awsdns-06.org, ns-113.awsdns-14.com, ns-1845.awsdns-38.co.uk, ns-731.awsdns-27.net report NS ns-1078.awsdns-06.org ns-113.awsdns-14.com ns-1845.awsdns-38.co.uk ns-731.awsdns-27.net. ns01.sanookonline.net, ns02.sanookonline.net, ns03.sanookonline.net, ns04.sanookonline.net report NS ns01.sanookonline.net ns02.sanookonline.net ns03.sanookonline.net ns04.sanookonline.net.
    #7
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1 on ns-1078.awsdns-06.org (205.251.196.54), ns-1078.awsdns-06.org (2600:9000:5304:3600::1), ns-113.awsdns-14.com (205.251.192.113), ns-113.awsdns-14.com (2600:9000:5300:7100::1), ns-1845.awsdns-38.co.uk (205.251.199.53), ns-1845.awsdns-38.co.uk (2600:9000:5307:3500::1), ns-731.awsdns-27.net (205.251.194.219), ns-731.awsdns-27.net (2600:9000:5302:db00::1); 2026102200 on ns01.sanookonline.net (203.151.135.90), ns02.sanookonline.net (203.151.135.91), ns03.sanookonline.net (61.91.95.90), ns04.sanookonline.net (61.91.95.91). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 sanook.com ›

Mail

warn

23 passed 6 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (sanook-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (sanook-com.mail.protection.outlook.com). Ask your hosting provider to set one.
    #30
  • !
    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 sanook.com ›