remoteleverage.com - dns.ninja

`remoteleverage.com`

DNSSEC	⚠️ Not signed
A	160.153.0.11^{🇺🇸 CLOUDFLARESPECTRUM160.153.0.0/24 MWP}
		PTR	`11.0.153.160.host.secureserver.net`
NS	`ns73.domaincontrol.com` ⭐
		A	2603:5:21a4::2f^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns73.domaincontrol.com`
		A	97.74.106.47^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns73.domaincontrol.com`
NS	`ns19.domaincontrol.com` ⚠️ Not in zone NS records
		A	2603:5:21d0::a^{🇺🇸 GODADDY-DNS2603:5:21d0::/44}
			PTR	`ns19.domaincontrol.com`
		A	97.74.109.10^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns19.domaincontrol.com`
NS	`ns20.domaincontrol.com` ⚠️ Not in zone NS records
		A	2603:5:22d0::a^{🇺🇸 GODADDY-DNS2603:5:22d0::/44}
			PTR	`ns20.domaincontrol.com`
		A	173.201.77.10^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns20.domaincontrol.com`
NS	`ns74.domaincontrol.com`
		A	2603:5:22a4::2f^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns74.domaincontrol.com`
		A	173.201.74.47^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns74.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c07::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f26.1e100.net`
		A	2607:f8b0:4004:c07::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f27.1e100.net`
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f26.1e100.net`
		A	172.253.62.26^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f26.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:spf1.hubspotemail.net ~all`
TXT	`anthropic-domain-verification-mx00dk=JIjsR6hWe6hR5da6756mSZHhK`
TXT	`google-site-verification=lC9dSn0StboMyjz6P6VrQBruPwprhS1RYcxe5l-Pofw`
TXT	`google-site-verification=AeTlxlfDA00k8D-5OE5b0d6IaTmZW2ABIkPHdpBH8lc`
TXT	`linkedin-site-verification=d0a1520e-8e2d-49e3-a478-5ca4de657134`
SOA	`ns73.domaincontrol.com`dns@jomax.net 2026-06-23 #5

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

Same first word

remoteleverage.com

DNS History

11 records (11 active, 0 former)

●NSns19.domaincontrol.com2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 20:48:12
● 2026-07-29 07:45:30

●NSns20.domaincontrol.com2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 20:48:12
● 2026-07-29 07:45:30

●NSns73.domaincontrol.com2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 20:48:12
● 2026-07-29 07:45:30

●NSns74.domaincontrol.com2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 20:48:12
● 2026-07-29 07:45:30

●MXalt1.aspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs

● 2026-07-29 07:45:30

●MXalt2.aspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs

● 2026-07-29 07:45:30

●MXalt3.aspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs

● 2026-07-29 07:45:30

●MXalt4.aspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs

● 2026-07-29 07:45:30

●MXaspmx.l.google.com2026-07-29 → 2026-07-29 · 1 obs

● 2026-07-29 07:45:30

●MXsmtp.google.com2026-07-29 → 2026-07-29 · 1 obs

● 2026-07-29 07:45:30

●A160.153.0.112026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 20:48:12
● 2026-07-29 07:45:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net...	-
remoteleverage.com	ns19.domaincontrol.com, ns20.domaincontrol.com, ns73.domaincontrol.com, ns74.domaincontrol.com	8 records

✅ Authoritative Response

Server:97.74.109.10

NS records: ns19.domaincontrol.com, ns20.domaincontrol.com, ns73.domaincontrol.com, ns74.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for remoteleverage.com (unsigned zone)

⏱️ Timing

Total: 359ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`160.153.0.11`
MX	6	`aspmx.l.google.com (pri: 1), smtp.google.com (pri: 1)...`
SOA	1	`ns73.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns19.domaincontrol.com, ns19.domaincontrol.com, ns20.domaincontrol.com...)

Analysis

IP Addresses

remoteleverage.com points to a single IP number: 160.153.0.11.

Additional host names — booksanta.net, yxj.ca, rainsaaronseo.com and two others — share IP numbers with remoteleverage.com.

Name Servers

remoteleverage.com has four authoritative name servers: ns19.domaincontrol.com, ns20.domaincontrol.com, ns73.domaincontrol.com and ns74.domaincontrol.com.

remoteleverage.com partially shares its NS delegation with several other domains, including godriven360.com, oliviaselig.com, liveincanyonlake.com and two others.

ns19.domaincontrol.com, ns20.domaincontrol.com, ns73.domaincontrol.com and ns74.domaincontrol.com each carry two IP addresses. ns19.domaincontrol.com has 97.74.109.10 and 2603:5:21d0::a; ns20.domaincontrol.com has 173.201.77.10 and 2603:5:22d0::a; ns73.domaincontrol.com has 97.74.106.47 and 2603:5:21a4::2f; ns74.domaincontrol.com has 173.201.74.47 and 2603:5:22a4::2f.

Mail Servers

The MX records for remoteleverage.com point to 6 mail servers — smtp.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.

remoteleverage.com shares mail servers — at least in part — with other domains, including kylintv.net, cmxfinance.com, legacycameragr.com and two others.

These mail servers are frequently used alongside the mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com, plus two others.

Host names with 9 IP numbers:

smtp.google.com points to 142.251.167.26, 172.253.62.26, 172.253.62.27 and 6 other IP addresses.

Host names with two IP numbers:

aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.

The host names smtp.google.com and aspmx.l.google.com both resolve to 2607:f8b0:4004:c23::1b IP addresses.