getedge.tech - dns.ninja

`getedge.tech`

DNSSEC	⚠️ Not signed
A	5.254.6.103^{🇩🇪 VOXILITY5.254.6.0/24 Voxility}
NS	`ns1.edge.network` ⭐
		A	213.170.141.1^{🇬🇧 edgenet213.170.141.0/24 Vultr Customer Route}
NS	`ns2.edge.network`
		A	213.170.141.2^{🇬🇧 edgenet213.170.141.0/24 Vultr Customer Route}
NS	`ns3.edge.network` ⚠️ Not in zone NS records
		A	213.170.141.1^{🇬🇧 edgenet213.170.141.0/24 Vultr Customer Route}
		A	213.170.141.2^{🇬🇧 edgenet213.170.141.0/24 Vultr Customer Route}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f27.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.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	`google-site-verification=SMBr8jUtPkYf013wauTI7Wh8spM9Oy0EWKv5dOBTrtI`
SOA	`ns1.edge.network`hostmaster@getedge.tech 2024-01-10 #2

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1786329840

Same first word

getedge.tech

getedge.com.au

getedge.ai

getedge.com

getedge.net

DNS History

12 records (9 active, 3 former)

●NSns1.edge.network2026-03-22 → 2026-08-10 · 3 obs

○ 2019-12-19 22:56:28
● 2026-03-22 20:54:46
● 2026-08-10 02:47:44

○NSns11.domaincontrol.com2019-12-19 → 2019-12-19 · 3 obs

● 2019-12-19 22:56:28
○ 2026-03-22 20:54:46
○ 2026-08-10 02:47:44

○NSns12.domaincontrol.com2019-12-19 → 2019-12-19 · 3 obs

● 2019-12-19 22:56:28
○ 2026-03-22 20:54:46
○ 2026-08-10 02:47:44

●NSns2.edge.network2026-03-22 → 2026-08-10 · 3 obs

○ 2019-12-19 22:56:28
● 2026-03-22 20:54:46
● 2026-08-10 02:47:44

●NSns3.edge.network2026-03-22 → 2026-08-10 · 3 obs

○ 2019-12-19 22:56:28
● 2026-03-22 20:54:46
● 2026-08-10 02:47:44

●MXalt1.aspmx.l.google.com2019-12-19 → 2026-08-10 · 5 obs

● 2019-12-19 22:56:28
● 2026-03-24 11:23:26
○ 2026-04-05 19:51:02
● 2026-05-08 10:44:22
● 2026-08-10 02:47:44

●MXalt2.aspmx.l.google.com2019-12-19 → 2026-08-10 · 5 obs

● 2019-12-19 22:56:28
● 2026-03-24 11:23:26
○ 2026-04-05 19:51:02
● 2026-05-08 10:44:22
● 2026-08-10 02:47:44

●MXalt3.aspmx.l.google.com2019-12-19 → 2026-08-10 · 5 obs

● 2019-12-19 22:56:28
● 2026-03-24 11:23:26
○ 2026-04-05 19:51:02
● 2026-05-08 10:44:22
● 2026-08-10 02:47:44

●MXalt4.aspmx.l.google.com2019-12-19 → 2026-08-10 · 5 obs

● 2019-12-19 22:56:28
● 2026-03-24 11:23:26
○ 2026-04-05 19:51:02
● 2026-05-08 10:44:22
● 2026-08-10 02:47:44

●MXaspmx.l.google.com2019-12-19 → 2026-08-10 · 5 obs

● 2019-12-19 22:56:28
● 2026-03-24 11:23:26
○ 2026-04-05 19:51:02
● 2026-05-08 10:44:22
● 2026-08-10 02:47:44

○A3.0.126.1442019-12-19 → 2019-12-19 · 3 obs

● 2019-12-19 22:56:28
○ 2026-03-22 20:54:46
○ 2026-08-10 02:47:44

●A5.254.6.1032026-03-22 → 2026-08-10 · 6 obs

○ 2019-12-19 22:56:28
● 2026-03-22 20:54:46
● 2026-03-24 11:23:26
○ 2026-04-05 19:51:02
● 2026-05-08 10:44:22
● 2026-08-10 02:47:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns10.trs-dns.org, ns10.trs-dns.info, ns01.trs-dns.com, ns01.trs-dns.net	8 records
getedge.tech	ns1.edge.network, ns2.edge.network, ns3.edge.network	-

✅ Authoritative Response

Server:213.170.141.1

NS records: ns1.edge.network, ns2.edge.network, ns3.edge.network

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for getedge.tech (unsigned zone)

⏱️ Timing

Total: 1904ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`5.254.6.103`
NS	2	`ns1.edge.network, ns2.edge.network`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`google-site-verification=SMBr8jUtPkYf013`
SOA	1	`ns1.edge.network hostmaster.getedge.tech`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns10.trs-dns.info, ns10.trs-dns.org, ns01.trs-dns.net...)

Analysis

IP Addresses

getedge.tech has exactly one IP address — 5.254.6.103.

Name Servers

The authoritative name servers for getedge.tech are ns1.edge.network, ns2.edge.network and ns3.edge.network — three in total.

At least some of getedge.tech's name servers are shared with other domains, for example josephdenne.com, film.one, tip.me and two more.

These name servers tend to co-occur with ns1-q2p8r.edge.network, ns2-q2p8r.edge.network, ns1-a3x7k.edge.network and 3 other name servers in the same DNS delegations.

Host names pointing to two IP addresses:

ns3.edge.network directs traffic to 213.170.141.1 and 213.170.141.2.

Host names resolving to a single IP address:

ns1.edge.network has the IP address 213.170.141.1.

ns2.edge.network has the IP address 213.170.141.2.

Both ns3.edge.network and ns1.edge.network resolve to 213.170.141.1 IP addresses each.

Both ns3.edge.network and ns2.edge.network resolve to 213.170.141.2 IP addresses each.

Mail Servers

Five mail servers handle getedge.tech: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by getedge.tech are shared with other domains: ns500765.ns500693.ns500765.ns500699.ns500734.ns500699.ns500699.ns500699.ns500699.ns500693.ns500699.ns500699.ns500693.ns500602.dtrkdll.com, ns500742.ns500671.ns500742.ns500731.ns500688.ns500705.ns500671.ns500671.ns500649.ns500704.ns500666.tenderladiesbz.com, ns500693.ns500693.ns500699.ns500734.ns500588.ns500693.ns500693.ns500632.ns500612.ns500588.ns500632.ns500612.dtrkdll.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com directs traffic to 172.253.63.26 and 2607:f8b0:4004:c09::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

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

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.

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