`localreputationedge.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-t94xdlsqfqezbdhbeaeepo.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=1775059337

Same first word

localreputationedge.com

DNS History

12 records (5 active, 7 former)

●NSns1.afternic.com2026-03-27 → 2026-04-01 · 3 obs

○ 2018-01-31 20:16:38
● 2026-03-27 01:54:48
● 2026-04-01 16:14:28

●NSns2.afternic.com2026-03-27 → 2026-04-01 · 3 obs

○ 2018-01-31 20:16:38
● 2026-03-27 01:54:48
● 2026-04-01 16:14:28

○NSns77.domaincontrol.com2016-12-19 → 2018-01-31 · 4 obs

● 2016-12-19 00:20:56
● 2018-01-31 20:16:38
○ 2026-03-27 01:54:48
○ 2026-04-01 16:14:28

○NSns78.domaincontrol.com2016-12-19 → 2018-01-31 · 4 obs

● 2016-12-19 00:20:56
● 2018-01-31 20:16:38
○ 2026-03-27 01:54:48
○ 2026-04-01 16:14:28

●NSverification-t94xdlsqfqezbdhbeaeepo.ns101.verify.hn2026-03-27 → 2026-04-01 · 3 obs

○ 2018-01-31 20:16:38
● 2026-03-27 01:54:48
● 2026-04-01 16:14:28

○MXlocalreputationedge-com.mail.protection.outlook.com2018-01-31 → 2018-01-31 · 4 obs

○ 2016-12-19 00:20:56
● 2018-01-31 20:16:38
○ 2026-03-27 01:54:48
○ 2026-04-01 16:14:28

○MXmailstore1.secureserver.net2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 00:20:56
○ 2018-01-31 20:16:38
○ 2026-04-01 16:14:28

○MXsmtp.secureserver.net2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 00:20:56
○ 2018-01-31 20:16:38
○ 2026-04-01 16:14:28

●A13.248.169.482026-03-27 → 2026-04-01 · 3 obs

○ 2018-01-31 20:16:38
● 2026-03-27 01:54:48
● 2026-04-01 16:14:28

○A160.153.71.32018-01-31 → 2018-01-31 · 4 obs

○ 2016-12-19 00:20:56
● 2018-01-31 20:16:38
○ 2026-03-27 01:54:48
○ 2026-04-01 16:14:28

○A50.63.202.122016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 00:20:56
○ 2018-01-31 20:16:38
○ 2026-04-01 16:14:28

●A76.223.54.1462026-03-27 → 2026-04-01 · 3 obs

○ 2018-01-31 20:16:38
● 2026-03-27 01:54:48
● 2026-04-01 16:14:28

🔍 DNS Trace

Analysis

IP Addresses

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

Other host names, for instance informationweb.com, elctric.com, healthcarecrew.com, dosuno.com and biz13.com share IP numbers with localreputationedge.com.

Name Servers

The domain localreputationedge.com is delegated to three name servers: ns1.afternic.com, ns2.afternic.com and verification-t94xdlsqfqezbdhbeaeepo.ns101.verify.hn.

localreputationedge.com shares name servers with other domains at least partially, for instance resan.net, mailmta01.bloommg.com, findingkryptonite.com, serveragency.com and simplecomm.com.

these name servers are often used together with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn.

Host names with two IP numbers:

ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69

ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69

verification-t94xdlsqfqezbdhbeaeepo.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146

localreputationedge.com - robtex.com