withings.com

Checked 22 October 2026, 11:31 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 1 failed 5 info

Registration

info

.com generic · Gandi SAS · expires 2030-05-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Gandi SAS
Registered
16 May 2008
Last changed
16 March 2026
Expires
16 May 2030
Status
client transfer prohibited
Registry nameservers
anycast-dns-01.withings.net, ns1.withings.net, ns2.withings.net, nsext2.withings.net, nsext3.withings.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2030-05-16 #3
    The registration is valid until 2030-05-16 (1301 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

anycast-dns-01.withings.net, ns1.withings.net, ns2.withings.net, nsext2.withings.net, nsext3.withings.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
anycast-dns-01.withings.net, ns1.withings.net, ns2.withings.net, nsext2.withings.net, nsext3.withings.net
NS in the zone
anycast-dns-01.withings.net, ns1.withings.net, ns2.withings.net, nsext.withings.net, nsext2.withings.net, nsext3.withings.net
NameserverAddressesNetwork (AS)Glue
anycast-dns-01.withings.net89.30.84.1AS4455 BSO - IX Reach Ltd, GB-
ns1.withings.net89.30.121.111 2a01:8200:1001:1:89:30:121:111AS4455 BSO - IX Reach Ltd, GB AS4455 BSO - IX Reach Ltd, GB-
ns2.withings.net89.30.121.112 2a01:8200:1001:1:89:30:121:112AS4455 BSO - IX Reach Ltd, GB AS4455 BSO - IX Reach Ltd, GB-
nsext.withings.net (zone only)152.228.208.92 2001:41d0:304:300::20f9AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
nsext2.withings.net35.198.100.93AS396982 GOOGLE-CLOUD-PLATFORM - Google LLC, US-
nsext3.withings.net15.237.195.81AS16509 AMAZON-02 - Amazon.com, Inc., US-

Checks

  • ✓ 5 nameservers #6
    Delegated to anycast-dns-01.withings.net, ns1.withings.net, ns2.withings.net, nsext2.withings.net, nsext3.withings.net.
  • !
    NS sets differ
    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
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 5 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 1 address; AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US): 1 address; AS4455 (BSO - IX Reach Ltd, GB): 5 addresses.
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • i
    Partly IPv6
    These nameservers have no IPv6 address: anycast-dns-01.withings.net, nsext2.withings.net, nsext3.withings.net.
    #13

Nameservers

fail

9 of 9 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
anycast-dns-01.withings.net 89.30.84.1NOERROR, 16 ms, authoritativenono / yesrefusedNot supported
ns1.withings.net 89.30.121.111NOERROR, 16 ms, authoritativenoyes / yesrefusedNot supported
ns1.withings.net 2a01:8200:1001:1:89:30:121:111NOERROR, 17 ms, authoritativenoyes / yesrefusedNot supported
ns2.withings.net 89.30.121.112NOERROR, 17 ms, authoritativenoyes / yesrefusedNot supported
ns2.withings.net 2a01:8200:1001:1:89:30:121:112NOERROR, 18 ms, authoritativenoyes / yesrefusedNot supported
nsext.withings.net 152.228.208.92NOERROR, 16 ms, authoritativenono / yesrefusedNot supported
nsext.withings.net 2001:41d0:304:300::20f9NOERROR, 16 ms, authoritativenoyes / yesrefusedNot supported
nsext2.withings.net 35.198.100.93NOERROR, 4 ms, authoritativenono / yesrefusedNot supported
nsext3.withings.net 15.237.195.81NOERROR, 12 ms, authoritativenono / yesrefusedNot supported

Checks

  • ✓ All respond #14
    All 9 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: anycast-dns-01.withings.net: "Not supported"; ns1.withings.net: "Not supported"; ns2.withings.net: "Not supported"; nsext.withings.net: "Not supported"; nsext2.withings.net: "Not supported"; nsext3.withings.net: "Not supported".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    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
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026100601 · primary ns1.withings.net

Found

Primary (MNAME)
ns1.withings.net
Contact (RNAME)
postmaster.withings.com
Serial
2026100601
Refresh / retry
3600 s / 3600 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
anycast-dns-01.withings.net (89.30.84.1)2026100601
ns1.withings.net (89.30.121.111)2026100601
ns1.withings.net (2a01:8200:1001:1:89:30:121:111)2026100601
ns2.withings.net (89.30.121.112)2026100601
ns2.withings.net (2a01:8200:1001:1:89:30:121:112)2026100601
nsext.withings.net (152.228.208.92)2026100601
nsext.withings.net (2001:41d0:304:300::20f9)2026100601
nsext2.withings.net (35.198.100.93)2026100601
nsext3.withings.net (15.237.195.81)2026100601

Checks

  • ✓ Serial 2026100601 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 7d, negative TTL 30m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.withings.net is one of the listed nameservers.
  • ✓ Contact postmaster@withings.com #25
    The SOA RNAME postmaster.withings.com means postmaster@withings.com.
  • ✓ Date-based serial #26
    The serial 2026100601 follows the YYYYMMDDnn convention (2026-10-06).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

13 records at the apex

Found

Read from
89.30.84.1:53
TypeValueTTL
SOAns1.withings.net. postmaster.withings.com. 2026100601 3600 3600 604800 1800600
NSnsext.withings.net.604800
NSns1.withings.net.604800
NSnsext3.withings.net.604800
NSanycast-dns-01.withings.net.604800
NSns2.withings.net.604800
NSnsext2.withings.net.604800
A23.227.38.65300
MX20 ALT1.ASPMX.L.GOOGLE.COM.604800
MX30 ALT3.ASPMX.L.GOOGLE.COM.604800
MX30 ALT4.ASPMX.L.GOOGLE.COM.604800
MX10 ASPMX.L.GOOGLE.COM.604800
MX20 ALT2.ASPMX.L.GOOGLE.COM.604800

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 7d, NS 7d. The NS TTL at the parent is 2d and in the zone 7d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35