wsdly.com - dns.ninja

wsdly.com

DNSSEC⚠️ Not signed
A54.157.68.44🇺🇸 Amazon54.156.0.0/14 EC2 IAD prefix
NSns1.digitalocean.com
A2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
A172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.digitalocean.com
A2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
A172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns3.digitalocean.com ⚠️ Not in zone NS records
A2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
A172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns3digitalocean.com ⚠️ Not in parent delegation
MXaspmx.l.google.com
A2607:f8b0:4004:c08::1a🇺🇸 Google2607:f8b0:4004::/48
PTRbi-in-f26.1e100.net
A173.194.45.26🇺🇸 Google173.194.0.0/16
PTRyuiadum-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1b🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
MXalt2.aspmx.l.google.com(5)
A2a00:1450:400b:c02::1a🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f26.1e100.net
A172.253.116.27🇺🇸 Google172.253.116.0/24
MXalt3.aspmx.l.google.com(10)
A2a00:1450:4009:c0f::1b🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f27.1e100.net
A192.178.223.26🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f26.1e100.net
MXalt4.aspmx.l.google.com(10)
A2a00:1450:400c:c23::1a🇧🇪 Google2a00:1450:400c::/48
PTRyubrupd-in-f26.1e100.net
A172.253.157.27🇺🇸 Google172.253.0.0/16
TXTgoogle-site-verification=MAeOkrgOk6qVgmVfb86JEOAOU3AlXv7kreKvxx7unrI
SOAns1.digitalocean.comhostmaster@wsdly.com serial=0

com

Same first word

Similar names

DNS History

15 records (10 active, 5 former)

20162017201820192020202120222023202420252026NSns1.digitalocean.comns2.digitalocean.comns3.digitalocean.comns3digitalocean.comf1g1ns1.dnspod.netf1g1ns2.dnspod.netjm1.dns.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA54.157.68.44156.237.107.20523.224.75.243
NSf1g1ns1.dnspod.net2015-05-30 → 2016-05-03 · 4 obs
● 2015-05-30 05:37:04
● 2016-05-03 15:51:18
○ 2020-02-02 15:24:52
○ 2026-06-28 12:29:32
NSf1g1ns2.dnspod.net2015-05-30 → 2016-05-03 · 4 obs
● 2015-05-30 05:37:04
● 2016-05-03 15:51:18
○ 2026-02-21 11:10:44
○ 2026-06-28 12:29:32
NSjm1.dns.com2020-02-02 → 2020-02-02 · 4 obs
○ 2016-05-03 15:51:18
● 2020-02-02 15:24:52
○ 2026-02-21 11:10:44
○ 2026-06-28 12:29:32
NSns1.digitalocean.com2026-02-21 → 2026-06-28 · 3 obs
○ 2020-02-02 15:24:52
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
NSns2.digitalocean.com2026-02-21 → 2026-06-28 · 3 obs
○ 2020-02-02 15:24:52
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
NSns3.digitalocean.com2026-02-21 → 2026-06-28 · 3 obs
○ 2020-02-02 15:24:52
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
NSns3digitalocean.com2026-02-21 → 2026-06-28 · 3 obs
○ 2020-02-02 15:24:52
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
MXalt1.aspmx.l.google.com2026-02-21 → 2026-06-28 · 2 obs
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
MXalt2.aspmx.l.google.com2026-02-21 → 2026-06-28 · 2 obs
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
MXalt3.aspmx.l.google.com2026-02-21 → 2026-06-28 · 2 obs
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
MXalt4.aspmx.l.google.com2026-02-21 → 2026-06-28 · 2 obs
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
MXaspmx.l.google.com2026-02-21 → 2026-06-28 · 2 obs
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32
A156.237.107.2052020-02-02 → 2020-02-02 · 4 obs
○ 2017-01-09 22:21:34
● 2020-02-02 15:24:52
○ 2026-02-21 11:10:44
○ 2026-06-28 12:29:32
A23.224.75.2432017-01-09 → 2017-01-09 · 3 obs
● 2017-01-09 22:21:34
○ 2020-02-02 15:24:52
○ 2026-06-28 12:29:32
A54.157.68.442026-02-21 → 2026-06-28 · 3 obs
○ 2020-02-02 15:24:52
● 2026-02-21 11:10:44
● 2026-06-28 12:29:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
wsdly.comns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com3 records

✅ Authoritative Response

Server:172.64.49.209

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wsdly.com (unsigned zone)

⏱️ Timing

Total: 245ms | Queries: -

📄 Records

TypeCountSample Data
A154.157.68.44
NS3ns2.digitalocean.com, ns3digitalocean.com...
MX5alt1.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)...
TXT1google-site-verification=MAeOkrgOk6qVgmV
SOA1ns1.digitalocean.com hostmaster.wsdly.co

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

wsdly.com has exactly one IP address — 54.157.68.44.

ec2-54-157-68-44.compute-1.amazonaws.com, for instance, is one of the other host names sharing IP numbers with wsdly.com.

Name Servers

Four name servers handle the delegation for wsdly.com: ns3digitalocean.com, ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

wsdly.com partially shares its NS delegation with several other domains, including 206.198.143.in-addr.arpa, mascotdata.com, 19.190.146.in-addr.arpa and two others.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

Mail for wsdly.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by wsdly.com are shared with other domains: ns500671.ns500754.ns500671.ns500731.ns500742.ns500731.ns500731.ns500704.ns500704.ns500705.ns500678.ns500671.lustychickser.com, ns500671.ns500671.ns500731.ns500742.ns500671.ns500705.ns500705.ns500705.ns500705.ns500678.ns500649.tenderladiesbz.com, ns500758.ns500758.ns500758.ns500759.ns500736.ns500698.ns500736.ns500735.ns500735.ns500735.ns500708.ns500576.ns500686.ns500652.ns500576.ns500576.trackreceptor.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com directs traffic to 173.194.45.26 and 2607:f8b0:4004:c08::1a.

alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.