`accessremotely.com`

DNSSEC	⚠️ Not signed
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
MX	`eforward1.registrar-servers.com` ⭐
		A	162.255.118.51^{🇺🇸 NAMCHEAP-PH162.255.118.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES}
			PTR	`eforward1.registrar-servers.com`
			PTR	`eforward3.registrar-servers.com`
MX	`eforward2.registrar-servers.com` ⭐
		A	162.255.118.52^{🇺🇸 NAMCHEAP-PH162.255.118.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES}
			PTR	`eforward2.registrar-servers.com`
MX	`eforward3.registrar-servers.com` ⭐
		A	162.255.118.51^{🇺🇸 NAMCHEAP-PH162.255.118.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES}
			PTR	`eforward1.registrar-servers.com`
			PTR	`eforward3.registrar-servers.com`
MX	`eforward4.registrar-servers.com`⁽¹⁵⁾
		A	162.255.118.52^{🇺🇸 NAMCHEAP-PH162.255.118.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES}
			PTR	`eforward2.registrar-servers.com`
MX	`eforward5.registrar-servers.com`⁽²⁰⁾
		A	162.255.118.51^{🇺🇸 NAMCHEAP-PH162.255.118.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES}
			PTR	`eforward1.registrar-servers.com`
			PTR	`eforward3.registrar-servers.com`
TXT	`v=spf1 include:spf.efwd.registrar-servers.com ~all`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1773342397

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

Previously MX for

accessremotely.com

Same first word

accessremotely.com

Similar names

remotelyaccess.com

DNS History

11 records (7 active, 4 former)

●NSdns1.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

●NSdns2.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

○NSns1.elzahosting.com2015-06-30 → 2017-10-06 · 4 obs

● 2015-06-30 17:59:32
● 2017-10-06 07:08:42
○ 2026-03-26 16:46:58
○ 2026-04-12 14:49:06

○NSns2.elzahosting.com2015-06-30 → 2017-10-06 · 4 obs

● 2015-06-30 17:59:32
● 2017-10-06 07:08:42
○ 2026-03-26 16:46:58
○ 2026-04-12 14:49:06

○MXaccessremotely.com2015-06-30 → 2017-10-06 · 4 obs

● 2015-06-30 17:59:32
● 2017-10-06 07:08:42
○ 2026-03-26 16:46:58
○ 2026-04-12 14:49:06

●MXeforward1.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

●MXeforward2.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

●MXeforward3.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

●MXeforward4.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

●MXeforward5.registrar-servers.com2026-03-26 → 2026-04-12 · 3 obs

○ 2017-10-06 07:08:42
● 2026-03-26 16:46:58
● 2026-04-12 14:49:06

○A66.135.32.1002015-06-30 → 2017-10-06 · 4 obs

● 2015-06-30 17:59:32
● 2017-10-06 07:08:42
○ 2026-03-26 16:46:58
○ 2026-04-12 14:49:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
accessremotely.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 records

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for accessremotely.com (unsigned zone)

⏱️ Timing

Total: 107ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10...`
TXT	1	`v=spf1 include:spf.efwd.registrar-server`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

Name Servers

accessremotely.com is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.

accessremotely.com shares the same name server setup as other domains, for example all1.eco, 2xfactorauth.com, playoutube.com, duodenal.com and rembly.com.

accessremotely.com at least partially shares name servers with other domains, for instance letsstartacountry.com, aeronautic.space, goegames.com, tdd-02.com and hedsinc.info.