readpulse.com - dns.ninja

`readpulse.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-kqnr5ht7z8pnvuelk6t645.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=1785395767

Same first word

readpulse.com

Similar names

DNS History

17 records (5 active, 12 former)

●NSns1.afternic.com2026-03-16 → 2026-07-30 · 3 obs

○ 2020-01-07 00:45:50
● 2026-03-16 04:28:34
● 2026-07-30 07:32:52

○NSns1.parkingcrew.net2017-02-17 → 2020-01-07 · 5 obs

○ 2016-01-26 22:07:20
● 2017-02-17 07:44:36
● 2020-01-07 00:45:50
○ 2026-03-16 04:28:34
○ 2026-07-30 07:32:52

●NSns2.afternic.com2026-03-16 → 2026-07-30 · 3 obs

○ 2020-01-07 00:45:50
● 2026-03-16 04:28:34
● 2026-07-30 07:32:52

○NSns2.parkingcrew.net2017-02-17 → 2020-01-07 · 5 obs

○ 2016-01-26 22:07:20
● 2017-02-17 07:44:36
● 2020-01-07 00:45:50
○ 2026-03-16 04:28:34
○ 2026-07-30 07:32:52

○NSns27.domaincontrol.com2015-06-15 → 2016-01-26 · 4 obs

● 2015-06-15 15:10:06
● 2016-01-26 22:07:20
○ 2017-02-17 07:44:36
○ 2026-07-30 07:32:52

○NSns28.domaincontrol.com2015-06-15 → 2016-01-26 · 4 obs

● 2015-06-15 15:10:06
● 2016-01-26 22:07:20
○ 2017-02-17 07:44:36
○ 2026-07-30 07:32:52

●NSverification-kqnr5ht7z8pnvuelk6t645.ns101.verify.hn2026-03-16 → 2026-07-30 · 3 obs

○ 2020-01-07 00:45:50
● 2026-03-16 04:28:34
● 2026-07-30 07:32:52

○MX.2026-03-16 → 2026-07-30 · 2 obs

○ 2026-03-16 04:28:34
○ 2026-07-30 07:32:52

○MXmail.h-email.net2017-02-17 → 2020-01-07 · 5 obs

○ 2016-01-26 22:07:20
● 2017-02-17 07:44:36
● 2020-01-07 00:45:50
○ 2026-03-16 04:28:34
○ 2026-07-30 07:32:52

○MXmailstore1.secureserver.net2015-06-15 → 2016-01-26 · 4 obs

● 2015-06-15 15:10:06
● 2016-01-26 22:07:20
○ 2017-02-17 07:44:36
○ 2026-07-30 07:32:52

○MXsmtp.secureserver.net2015-06-15 → 2016-01-26 · 4 obs

● 2015-06-15 15:10:06
● 2016-01-26 22:07:20
○ 2017-02-17 07:44:36
○ 2026-07-30 07:32:52

●A13.248.169.482026-03-16 → 2026-07-30 · 3 obs

○ 2020-01-07 00:45:50
● 2026-03-16 04:28:34
● 2026-07-30 07:32:52

○A141.8.224.932015-06-15 → 2015-11-01 · 4 obs

● 2015-06-15 15:10:06
● 2015-11-01 09:27:46
○ 2016-01-26 22:07:20
○ 2026-07-30 07:32:52

○A185.53.178.62017-02-17 → 2020-01-07 · 5 obs

○ 2016-04-22 15:11:00
● 2017-02-17 07:44:36
● 2020-01-07 00:45:50
○ 2026-03-16 04:28:34
○ 2026-07-30 07:32:52

○A50.63.202.822016-01-26 → 2016-01-26 · 4 obs

○ 2015-11-01 09:27:46
● 2016-01-26 22:07:20
○ 2016-04-22 15:11:00
○ 2026-07-30 07:32:52

○A54.183.99.632016-04-22 → 2016-04-22 · 4 obs

○ 2016-01-26 22:07:20
● 2016-04-22 15:11:00
○ 2017-02-17 07:44:36
○ 2026-07-30 07:32:52

●A76.223.54.1462026-03-16 → 2026-07-30 · 3 obs

○ 2020-01-07 00:45:50
● 2026-03-16 04:28:34
● 2026-07-30 07:32:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net...	-
readpulse.com	ns1.afternic.com, ns2.afternic.com, verification-kqnr5ht7z8pnvuelk6t645.ns101.verify.hn	4 records

✅ Authoritative Response

Server:97.74.98.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for readpulse.com (unsigned zone)

⏱️ Timing

Total: 3278ms | 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	`ns1.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

readpulse.com has two IP addresses: 13.248.169.48 and 76.223.54.146

tkzone.com, ns1.livereef.com, cingular.rebeo.net and two other host names share IP numbers with readpulse.com.

Name Servers

Three name servers are authoritative for readpulse.com: ns1.afternic.com, ns2.afternic.com and verification-kqnr5ht7z8pnvuelk6t645.ns101.verify.hn.

There is at least partial name server overlap between readpulse.com and other domains — myuniversity.org, gumtr.com, addsdigital.com and two more among them.

These name servers tend to appear in combination with the name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn, verification-a6wcjiy3t6u64zppv78yuf.ns101.verify.hn, verification-a3pihk92cq8kttu6igu5bi.ns101.verify.hn and verification-iryqusbri9xlks4ssi7d4w.ns101.verify.hn.

ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45. verification-kqnr5ht7z8pnvuelk6t645.ns101.verify.hn resolves to 13.248.169.48 and 76.223.54.146. All three hostnames point to two IP numbers each.