sweethusky.com - dns.ninja

sweethusky.com

DNSSEC⚠️ Not signed
A3.33.130.190🇺🇸 Amazon3.33.128.0/20
PTRa2aa9ff50de748dbe.awsglobalaccelerator.com
A15.197.148.33🇺🇸 Amazon15.197.144.0/20
NSns51.domaincontrol.com ⭐
A2603:5:2192::1a🇺🇸 GODADDY-DNS2603:5:2190::/44
PTRns51.domaincontrol.com
A97.74.105.26🇺🇸 GODADDY-DNS97.74.104.0/23
PTRns51.domaincontrol.com
NSns52.domaincontrol.com
A2603:5:2292::1a🇺🇸 GODADDY-DNS2603:5:2290::/44
PTRns52.domaincontrol.com
A173.201.73.26🇺🇸 GODADDY-DNS173.201.72.0/23
PTRns52.domaincontrol.com
SOAns51.domaincontrol.comdns@jomax.net 2026-04-09 #1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1783954282
⚠️ On DNS blocklist: tif
🦠 Blackbook: Known malware/C&C domain
WOT: SAFE (19/100)

Same first word

sweethusky.com

DNS History

16 records (4 active, 12 former)

20162017201820192020202120222023202420252026NSns51.domaincontrol.comns52.domaincontrol.comabby.ns.cloudflare.comdns1.registrar-servers.comdns2.registrar-servers.comfred.ns.cloudflare.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA15.197.148.333.33.130.190104.28.18.105104.28.19.105159.65.115.78
○NSabby.ns.cloudflare.com2015-05-29 → 2016-03-19 · 4 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2026-07-13 15:12:42
○NSdns1.registrar-servers.com2019-03-01 → 2019-03-01 · 4 obs
○ 2016-07-17 05:07:10
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○NSdns2.registrar-servers.com2019-03-01 → 2019-03-01 · 4 obs
○ 2016-07-17 05:07:10
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○NSfred.ns.cloudflare.com2015-05-29 → 2016-03-19 · 4 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2026-07-13 15:12:42
●NSns51.domaincontrol.com2026-03-27 → 2026-07-13 · 3 obs
○ 2019-03-01 16:54:24
● 2026-03-27 09:57:30
● 2026-07-13 15:12:42
●NSns52.domaincontrol.com2026-03-27 → 2026-07-13 · 3 obs
○ 2019-03-01 16:54:24
● 2026-03-27 09:57:30
● 2026-07-13 15:12:42
○MXeforward1.registrar-servers.com2015-05-29 → 2019-03-01 · 7 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2017-03-20 02:01:46
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○MXeforward2.registrar-servers.com2015-05-29 → 2019-03-01 · 7 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2017-03-20 02:01:46
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○MXeforward3.registrar-servers.com2015-05-29 → 2019-03-01 · 7 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2017-03-20 02:01:46
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○MXeforward4.registrar-servers.com2015-05-29 → 2019-03-01 · 7 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2017-03-20 02:01:46
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○MXeforward5.registrar-servers.com2015-05-29 → 2019-03-01 · 7 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2017-03-20 02:01:46
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
○A104.28.18.1052015-05-29 → 2016-03-19 · 4 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2026-07-13 15:12:42
○A104.28.19.1052015-05-29 → 2016-03-19 · 4 obs
● 2015-05-29 21:07:58
● 2016-03-19 21:53:10
○ 2016-07-17 05:07:10
○ 2026-07-13 15:12:42
●A15.197.148.332026-03-27 → 2026-07-13 · 3 obs
○ 2019-03-01 16:54:24
● 2026-03-27 09:57:30
● 2026-07-13 15:12:42
○A159.65.115.782019-03-01 → 2019-03-01 · 4 obs
○ 2016-07-17 05:07:10
● 2019-03-01 16:54:24
○ 2026-03-27 09:57:30
○ 2026-07-13 15:12:42
●A3.33.130.1902026-03-27 → 2026-07-13 · 3 obs
○ 2019-03-01 16:54:24
● 2026-03-27 09:57:30
● 2026-07-13 15:12:42

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
sweethusky.comns51.domaincontrol.com, ns52.domaincontrol.com4 records

✅ Authoritative Response

Server:173.201.73.26

NS records: ns51.domaincontrol.com, ns52.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sweethusky.com (unsigned zone)

⏱️ Timing

Total: 108ms | Queries: -

📄 Records

TypeCountSample Data
A23.33.130.190, 15.197.148.33
NS2ns51.domaincontrol.com, ns52.domaincontrol.com
SOA1ns51.domaincontrol.com dns.jomax.net

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns51.domaincontrol.com, ns51.domaincontrol.com, ns52.domaincontrol.com...)

Analysis

IP Addresses

sweethusky.com has two IP addresses: 3.33.130.190 and 15.197.148.33

Among the host names that share IP numbers with sweethusky.com are topconsumerreviews.es, politecnica.co, shotboxx.com and two others.

Name Servers

sweethusky.com uses two name servers for its delegation: ns51.domaincontrol.com and ns52.domaincontrol.com.

sweethusky.com has the same name server delegation as a number of other domains, such as thorpes-joinery.com, originalsantatable.com, paintprotectionwichita.com and two more.

The two host names ns51.domaincontrol.com and ns52.domaincontrol.com each have a pair of IP addresses: ns51.domaincontrol.com has 97.74.105.26 and 2603:5:2192::1a, and ns52.domaincontrol.com has 173.201.73.26 and 2603:5:2292::1a.