SurfaceMap › w › withings.com

withings.com

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

Domain & DNS

fail

22 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: anycast-dns-01.withings.net (89.30.84.1): dial tcp 89.30.84.1:53: i/o timeout; nsext.withings.net (152.228.208.92): dial tcp 152.228.208.92:53: i/o timeout; nsext2.withings.net (35.198.100.93): dial tcp 35.198.100.93:53: i/o timeout; nsext3.withings.net (15.237.195.81): dial tcp 15.237.195.81:53: i/o timeout.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: nsext.withings.net. anycast-dns-01.withings.net, ns1.withings.net, ns2.withings.net, nsext.withings.net, nsext2.withings.net, nsext3.withings.net report NS anycast-dns-01.withings.net ns1.withings.net ns2.withings.net nsext.withings.net nsext2.withings.net nsext3.withings.net.
    #7
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 7d, negative TTL 30m.
    #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 withings.com ›

Mail

warn

30 passed 2 warn 0 failed

Areas

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

Problems

  • !
    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: google (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

!

Full report

Mail report for withings.com ›