whyhdc.com - dns.ninja

whyhdc.com

DNSSEC⚠️ Not signed
A156.236.45.171πŸ‡ΊπŸ‡Έ GNET-AS9294156.236.32.0/20
NSns1.domainnamedns.com ⭐
A2604:86c0:6001:14::d86a:b99cπŸ‡ΊπŸ‡Έ AS630232604:86c0:6000::/36 GTHOST-SCL
A216.106.185.75πŸ‡ΊπŸ‡Έ AS63023216.106.185.0/24 GTHost
PTR75-185-106-216.clients.gthost.com
NSns2.domainnamedns.com
A2604:86c0:2001:6::2672:72b7πŸ‡ΊπŸ‡Έ AS630232604:86c0:2000::/36 GTHOST-LAX
A38.114.114.183πŸ‡¨πŸ‡¦ AS6302338.114.114.0/24 Route Registered for Cogent Communications Customer GLOBALTELEHOST CORP.
PTR183-114-114-38.clients.gthost.com
NSns3.domainnamedns.com ⚠️ Not in parent delegation
A2406:da18:e80:ec00:7b68:89e5:1ce1:c481πŸ‡ΈπŸ‡¬ Amazon2406:da18:c00::/38 AWS
A54.151.142.119πŸ‡ΈπŸ‡¬ Amazon54.151.128.0/17 SIN prefix
PTRec2-54-151-142-119.ap-southeast-1.compute.amazonaws.com
NSns4.domainnamedns.com ⚠️ Not in parent delegation
A2604:86c0:2001:c::43dc:4833πŸ‡ΊπŸ‡Έ AS630232604:86c0:2000::/36 GTHOST-LAX
A67.220.72.51πŸ‡ΊπŸ‡Έ AS6302367.220.72.0/24 GTHOST
PTR51-72-220-67.clients.gthost.com
SOAns1.domainnamedns.comsupport@namens.net serial=1781185699

com

Same first word

Similar names

DNS History

19 records (5 active, 14 former)

20162017201820192020202120222023202420252026NSns1.domainnamedns.comns2.domainnamedns.comns3.domainnamedns.comns4.domainnamedns.comelisabeth.ns.cloudflare.comexpire1.gname-dns.comexpire2.gname-dns.comf1g1ns1.dnspod.netf1g1ns2.dnspod.netjerome.ns.cloudflare.comA156.236.45.171104.21.56.94139.201.126.135172.67.183.187202.102.85.58208.115.226.2022606:4700:3036::6815:385e2606:4700:3036::ac43:b7bbCNAMEexp.gs-cdn.com
β—‹NSelisabeth.ns.cloudflare.com2026-02-17 β†’ 2026-07-03 Β· 2 obs
β—‹ 2026-02-17 00:56:42
β—‹ 2026-07-03 14:42:24
β—‹NSexpire1.gname-dns.com2026-02-17 β†’ 2026-03-09 Β· 5 obs
β—‹ 2017-03-16 10:22:18
● 2026-02-17 00:56:42
● 2026-03-09 14:53:52
β—‹ 2026-04-07 14:32:04
β—‹ 2026-07-03 14:42:24
β—‹NSexpire2.gname-dns.com2026-02-17 β†’ 2026-03-09 Β· 5 obs
β—‹ 2017-03-16 10:22:18
● 2026-02-17 00:56:42
● 2026-03-09 14:53:52
β—‹ 2026-04-07 14:32:04
β—‹ 2026-07-03 14:42:24
β—‹NSf1g1ns1.dnspod.net2016-04-29 β†’ 2017-03-16 Β· 4 obs
● 2016-04-29 05:39:10
● 2017-03-16 10:22:18
β—‹ 2026-02-17 00:56:42
β—‹ 2026-07-03 14:42:24
β—‹NSf1g1ns2.dnspod.net2016-04-29 β†’ 2017-03-16 Β· 4 obs
● 2016-04-29 05:39:10
● 2017-03-16 10:22:18
β—‹ 2026-02-17 00:56:42
β—‹ 2026-07-03 14:42:24
β—‹NSjerome.ns.cloudflare.com2026-02-17 β†’ 2026-07-03 Β· 2 obs
β—‹ 2026-02-17 00:56:42
β—‹ 2026-07-03 14:42:24
●NSns1.domainnamedns.com2026-06-15 β†’ 2026-07-03 Β· 3 obs
β—‹ 2026-04-07 14:32:04
● 2026-06-15 18:47:12
● 2026-07-03 14:42:24
●NSns2.domainnamedns.com2026-06-15 β†’ 2026-07-03 Β· 3 obs
β—‹ 2026-04-07 14:32:04
● 2026-06-15 18:47:12
● 2026-07-03 14:42:24
●NSns3.domainnamedns.com2026-06-15 β†’ 2026-07-03 Β· 3 obs
β—‹ 2026-04-07 14:32:04
● 2026-06-15 18:47:12
● 2026-07-03 14:42:24
●NSns4.domainnamedns.com2026-06-15 β†’ 2026-07-03 Β· 3 obs
β—‹ 2026-04-07 14:32:04
● 2026-06-15 18:47:12
● 2026-07-03 14:42:24
β—‹A104.21.56.942026-02-17 β†’ 2026-02-17 Β· 4 obs
β—‹ 2017-03-16 10:22:18
● 2026-02-17 00:56:42
β—‹ 2026-03-09 14:53:52
β—‹ 2026-07-03 14:42:24
β—‹A139.201.126.1352016-04-29 β†’ 2016-04-29 Β· 4 obs
β—‹ 2015-11-04 09:25:16
● 2016-04-29 05:39:10
β—‹ 2017-03-16 10:22:18
β—‹ 2026-07-03 14:42:24
●A156.236.45.1712026-06-15 β†’ 2026-07-03 Β· 3 obs
β—‹ 2026-03-09 14:53:52
● 2026-06-15 18:47:12
● 2026-07-03 14:42:24
β—‹A172.67.183.1872026-02-17 β†’ 2026-02-17 Β· 4 obs
β—‹ 2017-03-16 10:22:18
● 2026-02-17 00:56:42
β—‹ 2026-03-09 14:53:52
β—‹ 2026-07-03 14:42:24
β—‹A202.102.85.582017-03-16 β†’ 2026-02-17 Β· 5 obs
β—‹ 2016-04-29 05:39:10
● 2017-03-16 10:22:18
● 2026-02-17 00:56:42
β—‹ 2026-03-09 14:53:52
β—‹ 2026-07-03 14:42:24
β—‹A208.115.226.2022015-06-24 β†’ 2015-11-04 Β· 4 obs
● 2015-06-24 06:24:46
● 2015-11-04 09:25:16
β—‹ 2016-04-29 05:39:10
β—‹ 2026-07-03 14:42:24
β—‹A2606:4700:3036::6815:385e2026-02-17 β†’ 2026-02-17 Β· 4 obs
β—‹ 2017-03-16 10:22:18
● 2026-02-17 00:56:42
β—‹ 2026-03-09 14:53:52
β—‹ 2026-07-03 14:42:24
β—‹A2606:4700:3036::ac43:b7bb2026-02-17 β†’ 2026-02-17 Β· 4 obs
β—‹ 2017-03-16 10:22:18
● 2026-02-17 00:56:42
β—‹ 2026-03-09 14:53:52
β—‹ 2026-07-03 14:42:24
β—‹CNAMEexp.gs-cdn.com2026-02-17 β†’ 2026-03-09 Β· 4 obs
● 2026-02-17 00:56:42
● 2026-03-09 14:53:52
β—‹ 2026-04-07 14:32:04
β—‹ 2026-07-03 14:42:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comh.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net...-
whyhdc.comns1.domainnamedns.com, ns2.domainnamedns.com4 records

βœ… Authoritative Response

Server:38.114.114.183

NS records: ns1.domainnamedns.com, ns2.domainnamedns.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for whyhdc.com (unsigned zone)

⏱️ Timing

Total: 333ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1156.236.45.171
NS4ns2.domainnamedns.com, ns1.domainnamedns.com...
SOA1ns1.domainnamedns.com support.namens.net

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.domainnamedns.com, ns1.domainnamedns.com, ns2.domainnamedns.com...)

Analysis

IP Addresses

whyhdc.com points to a single IP number: 156.236.45.171.

Name Servers

whyhdc.com has four authoritative name servers: ns1.domainnamedns.com, ns2.domainnamedns.com, ns3.domainnamedns.com and ns4.domainnamedns.com.

The name servers of whyhdc.com overlap at least partially with those of other domains β€” among them 6292bbb.com, toonhub.pro, qdjc119.com and two more.

Each of the four hosts ns1.domainnamedns.com, ns2.domainnamedns.com, ns3.domainnamedns.com and ns4.domainnamedns.com has two IP addresses. ns1.domainnamedns.com points to 216.106.185.75 and 2604:86c0:6001:14::d86a:b99c. ns2.domainnamedns.com points to 38.114.114.183 and 2604:86c0:2001:6::2672:72b7. ns3.domainnamedns.com points to 54.151.142.119 and 2406:da18:e80:ec00:7b68:89e5:1ce1:c481. ns4.domainnamedns.com points to 67.220.72.51 and 2604:86c0:2001:c::43dc:4833.