cryptohashing.com - dns.ninja

`cryptohashing.com`

DNSSEC	⚠️ Not signed
A	207.148.248.143^{🇺🇸 EIG-29873207.148.248.0/24}
NS	`ns.buydomains.com` ⚠️ Not in zone NS records
		A	52.20.26.87^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-20-26-87.compute-1.amazonaws.com`
NS	`this-domain-for-sale.com` ⚠️ Not in zone NS records
		A	52.20.26.87^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-20-26-87.compute-1.amazonaws.com`

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1783002006

Subdomains

mx.cryptohashing.com

Same first word

cryptohashing.com

DNS History

13 records (3 active, 10 former)

●NSns.buydomains.com2026-02-25 → 2026-07-02 · 3 obs

○ 2019-01-25 03:12:38
● 2026-02-25 12:26:02
● 2026-07-02 14:27:52

○NSns1.ipage.com2015-08-23 → 2016-12-02 · 4 obs

● 2015-08-23 16:52:52
● 2016-12-02 13:55:52
○ 2017-06-25 18:56:36
○ 2026-07-02 14:27:52

○NSns11033.ztomy.com2017-06-25 → 2019-01-25 · 5 obs

○ 2016-12-02 13:55:52
● 2017-06-25 18:56:36
● 2019-01-25 03:12:38
○ 2026-02-25 12:26:02
○ 2026-07-02 14:27:52

○NSns2.ipage.com2015-08-23 → 2016-12-02 · 4 obs

● 2015-08-23 16:52:52
● 2016-12-02 13:55:52
○ 2017-06-25 18:56:36
○ 2026-07-02 14:27:52

○NSns21033.ztomy.com2017-06-25 → 2019-01-25 · 5 obs

○ 2016-12-02 13:55:52
● 2017-06-25 18:56:36
● 2019-01-25 03:12:38
○ 2026-02-25 12:26:02
○ 2026-07-02 14:27:52

●NSthis-domain-for-sale.com2026-02-25 → 2026-07-02 · 3 obs

○ 2019-01-25 03:12:38
● 2026-02-25 12:26:02
● 2026-07-02 14:27:52

○MXmx.cryptohashing.com2015-08-23 → 2016-12-02 · 4 obs

● 2015-08-23 16:52:52
● 2016-12-02 13:55:52
○ 2017-06-25 18:56:36
○ 2026-07-02 14:27:52

●A207.148.248.1432026-02-25 → 2026-07-02 · 3 obs

○ 2019-01-25 03:12:38
● 2026-02-25 12:26:02
● 2026-07-02 14:27:52

○A209.99.64.332017-06-25 → 2019-01-25 · 5 obs

○ 2016-12-02 13:55:52
● 2017-06-25 18:56:36
● 2019-01-25 03:12:38
○ 2026-02-25 12:26:02
○ 2026-07-02 14:27:52

○A66.96.147.1642015-08-23 → 2015-12-14 · 4 obs

● 2015-08-23 16:52:52
● 2015-12-14 18:06:46
○ 2016-04-12 16:28:46
○ 2026-07-02 14:27:52

○A66.96.149.162016-04-12 → 2016-12-02 · 5 obs

○ 2015-12-14 18:06:46
● 2016-04-12 16:28:46
● 2016-12-02 13:55:52
○ 2017-06-25 18:56:36
○ 2026-07-02 14:27:52

○A69.172.201.1532017-06-25 → 2017-06-25 · 4 obs

○ 2016-12-02 13:55:52
● 2017-06-25 18:56:36
○ 2019-01-25 03:12:38
○ 2026-07-02 14:27:52

○PTRns11033.ztomy.com2017-06-25 → 2019-01-25 · 4 obs

● 2017-06-25 18:56:36
● 2019-01-25 03:12:38
○ 2026-02-25 12:26:02
○ 2026-07-02 14:27:52

🔍 DNS Trace

Analysis

Hierarchy

cryptohashing.com is a parent domain of mx.cryptohashing.com.

IP Addresses

cryptohashing.com directs to one IP number, which is 207.148.248.143.

Among the host names that share IP numbers with cryptohashing.com are eklet.com, jotnet.com, heritageconcepts.com and two others.

Name Servers

cryptohashing.com uses two name servers for its delegation: this-domain-for-sale.com and ns.buydomains.com.

cryptohashing.com has the same name server delegation as a number of other domains, such as serverbeat.com, printcd.com, esly.org and two more.

cryptohashing.com shares at least some of its name servers with other domains, such as logisticmarketing.com and espb.net.

this-domain-for-sale.com resolves to 52.20.26.87; ns.buydomains.com resolves to the same IP address, 52.20.26.87.

Both this-domain-for-sale.com and ns.buydomains.com resolve to 52.20.26.87 IP addresses each.