pushdata.com - dns.ninja

`pushdata.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.afternic.com` ⭐
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com`
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`verification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net serial=1

`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=1780591334

Same first word

pushdata.io

pushdata.de

pushdata.com

Similar names

phatsadu.net

datashup.com

phatsadu.com

datapush.shop

datapush.cn

datapush.net

DNS History

21 records (5 active, 16 former)

○NSbuy.internettraffic.com2015-06-15 → 2016-04-20 · 4 obs

● 2015-06-15 18:06:16
● 2016-04-20 09:23:48
○ 2016-12-03 08:03:50
○ 2026-06-04 16:47:10

○NSdns1.name-services.com2026-04-05 → 2026-04-05 · 3 obs

○ 2017-05-25 16:53:54
● 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSdns2.name-services.com2026-04-05 → 2026-04-05 · 3 obs

○ 2017-05-25 16:53:54
● 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSdns3.name-services.com2026-04-05 → 2026-04-05 · 3 obs

○ 2017-05-25 16:53:54
● 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSdns4.name-services.com2026-04-05 → 2026-04-05 · 3 obs

○ 2017-05-25 16:53:54
● 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSdns5.name-services.com2026-04-05 → 2026-04-05 · 3 obs

○ 2017-05-25 16:53:54
● 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

●NSns1.afternic.com2026-06-04 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
● 2026-06-04 16:47:10

○NSns1.sedoparking.com2026-04-05 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSns1.uniregistrymarket.link2016-12-03 → 2017-05-25 · 5 obs

○ 2016-04-20 09:23:48
● 2016-12-03 08:03:50
● 2017-05-25 16:53:54
○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

●NSns2.afternic.com2026-06-04 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
● 2026-06-04 16:47:10

○NSns2.sedoparking.com2026-04-05 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSns2.uniregistrymarket.link2016-12-03 → 2017-05-25 · 5 obs

○ 2016-04-20 09:23:48
● 2016-12-03 08:03:50
● 2017-05-25 16:53:54
○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○NSsell.internettraffic.com2015-06-15 → 2016-04-20 · 4 obs

● 2015-06-15 18:06:16
● 2016-04-20 09:23:48
○ 2016-12-03 08:03:50
○ 2026-06-04 16:47:10

●NSverification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn2026-06-04 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
● 2026-06-04 16:47:10

○MXlocalhost2026-04-05 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

●A13.248.169.482026-06-04 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
● 2026-06-04 16:47:10

○A15.197.172.602026-04-05 → 2026-04-05 · 3 obs

○ 2017-05-25 16:53:54
● 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○A64.190.63.2222026-04-05 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○A69.172.201.1532016-04-20 → 2017-05-25 · 5 obs

○ 2016-01-27 08:05:00
● 2016-04-20 09:23:48
● 2017-05-25 16:53:54
○ 2026-04-05 22:56:18
○ 2026-06-04 16:47:10

○A69.172.201.2082015-06-15 → 2016-01-27 · 4 obs

● 2015-06-15 18:06:16
● 2016-01-27 08:05:00
○ 2016-04-20 09:23:48
○ 2026-06-04 16:47:10

●A76.223.54.1462026-06-04 → 2026-06-04 · 2 obs

○ 2026-04-05 22:56:18
● 2026-06-04 16:47:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, b.gtld-servers.net...	-
pushdata.com	ns1.afternic.com, ns2.afternic.com, verification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn	4 records

✅ Authoritative Response

Server:173.201.66.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pushdata.com (unsigned zone)

⏱️ Timing

Total: 1328ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns2.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

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

Analysis

IP Addresses

pushdata.com points to two IP numbers: 13.248.169.48 and 76.223.54.146.

Additional host names — www.mhms.com, timeplastic.com, skl.jsnet.com and two others — share IP numbers with pushdata.com.

Name Servers

The authoritative name servers for pushdata.com are ns1.afternic.com, ns2.afternic.com and verification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn — three in total.

At least some of pushdata.com's name servers are shared with other domains, for example blobus.com, mx1.happyhost.com, dravin.com and two more.

These name servers tend to be deployed in combination with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

ns1.afternic.com, ns2.afternic.com and verification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn all resolve to exactly two IP numbers apiece: ns1.afternic.com → 97.74.98.69 and 2603:5:2126::45; ns2.afternic.com → 173.201.66.69 and 2603:5:2226::45; verification-dv9dy4ykac3xs7zcclohp7.ns101.verify.hn → 13.248.169.48 and 76.223.54.146.