techmango.net - dns.ninja

`techmango.net`

DNSSEC	⚠️ Not signed
A	3.7.139.72^{🇮🇳 Amazon3.6.0.0/15 EC2 GRU prefix}
		PTR	`ec2-3-7-139-72.ap-south-1.compute.amazonaws.com`
NS	`ns65.domaincontrol.com` ⭐
		A	2603:5:2164::2b^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns65.domaincontrol.com`
		A	97.74.102.43^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns65.domaincontrol.com`
NS	`ns66.domaincontrol.com`
		A	2603:5:2264::2b^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns66.domaincontrol.com`
		A	173.201.70.43^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns66.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 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::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.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	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`google-site-verification=z5tV8sTwFIPFS8O9-_KT2HhbUyZ12UYg4-u_2ET8rR8`
TXT	`google-site-verification=HCrDj02LaUPUkIiBynwxEA9YmgSbWmhJ6noSBJuhGeE`
TXT	`anthropic-domain-verification-5t3bm8=dahi0uWSZXkBoVcXR4zCZTcY0`
TXT	`linkedin-site-verification=d305a644-6d9e-4ae7-97ca-6f3e64d62511`
TXT	`zoho-verification=zb86266330.zmverify.zoho.in`
TXT	`atlassian-domain-verification=xGPA1r077wbEvKsniQ6b6uaJzTuqZ3VL02pmKxI75JC3UFb...`
TXT	`google-site-verification=vdZX6D2JY1n131sMjpdvGC-HmT6d_5SKYEnGaPz9aq8`
TXT	`v=spf1 include:dc-3ae7784a9e._spfm.techmango.net ~all`
TXT	`MS=ms21096945`
SOA	`ns65.domaincontrol.com`dns@jomax.net 2026-07-08 #4

`net`

	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=17862(0x37313735)9

Same first word

techmango.nl

techmango.net

techmango.top

techmango.com

Similar names

DNS History

13 records (8 active, 5 former)

●NSns65.domaincontrol.com2017-01-03 → 2026-08-09 · 2 obs

● 2017-01-03 20:08:34
● 2026-08-09 10:39:36

●NSns66.domaincontrol.com2017-01-03 → 2026-08-09 · 2 obs

● 2017-01-03 20:08:34
● 2026-08-09 10:39:36

●MXalt1.aspmx.l.google.com2017-01-03 → 2026-08-09 · 2 obs

● 2017-01-03 20:08:34
● 2026-08-09 10:39:36

●MXalt2.aspmx.l.google.com2017-01-03 → 2026-08-09 · 2 obs

● 2017-01-03 20:08:34
● 2026-08-09 10:39:36

○MXalt3.aspmx.l.google.com2017-01-03 → 2017-11-28 · 4 obs

● 2017-01-03 20:08:34
● 2017-11-28 23:39:08
○ 2026-06-10 04:32:20
○ 2026-08-09 10:39:36

○MXalt4.aspmx.l.google.com2017-01-03 → 2017-11-28 · 4 obs

● 2017-01-03 20:08:34
● 2017-11-28 23:39:08
○ 2026-06-10 04:32:20
○ 2026-08-09 10:39:36

●MXaspmx.l.google.com2017-01-03 → 2026-08-09 · 2 obs

● 2017-01-03 20:08:34
● 2026-08-09 10:39:36

●MXaspmx2.googlemail.com2026-06-10 → 2026-08-09 · 3 obs

○ 2017-11-28 23:39:08
● 2026-06-10 04:32:20
● 2026-08-09 10:39:36

●MXaspmx3.googlemail.com2026-06-10 → 2026-08-09 · 3 obs

○ 2017-11-28 23:39:08
● 2026-06-10 04:32:20
● 2026-08-09 10:39:36

○A15.197.225.1282026-06-10 → 2026-06-10 · 4 obs

○ 2017-11-28 23:39:08
● 2026-06-10 04:32:20
○ 2026-07-09 22:58:30
○ 2026-08-09 10:39:36

○A3.33.251.1682026-06-10 → 2026-06-10 · 4 obs

○ 2017-11-28 23:39:08
● 2026-06-10 04:32:20
○ 2026-07-09 22:58:30
○ 2026-08-09 10:39:36

●A3.7.139.722026-07-09 → 2026-08-09 · 3 obs

○ 2026-06-10 04:32:20
● 2026-07-09 22:58:30
● 2026-08-09 10:39:36

○A45.79.203.572017-01-03 → 2017-11-28 · 4 obs

● 2017-01-03 20:08:34
● 2017-11-28 23:39:08
○ 2026-06-10 04:32:20
○ 2026-08-09 10:39:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
techmango.net	ns66.domaincontrol.com, ns65.domaincontrol.com	-

✅ Authoritative Response

Server:97.74.102.43

NS records: ns66.domaincontrol.com, ns65.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for techmango.net (unsigned zone)

⏱️ Timing

Total: 461ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.7.139.72`
NS	2	`ns65.domaincontrol.com, ns66.domaincontrol.com`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	9	`google-site-verification=z5tV8sTwFIPFS8O, google-site-verification=HCrDj02LaUPUkIi...`
SOA	1	`ns65.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

techmango.net has exactly one IP address — 3.7.139.72.

Other host names share IP numbers with techmango.net; ec2-3-7-139-72.ap-south-1.compute.amazonaws.com is one such example.

Name Servers

techmango.net is served by two delegated name servers, ns65.domaincontrol.com and ns66.domaincontrol.com.

The name server configuration of techmango.net is shared with other domains, for instance bebeautifullymade.com, lostnode.org, signatureseminar.com and two others.

Each of the two host names carries two IP addresses: ns65.domaincontrol.com points to 97.74.102.43 and 2603:5:2164::2b, and ns66.domaincontrol.com points to 173.201.70.43 and 2603:5:2264::2b.

Mail Servers

Five mail servers handle techmango.net: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

At least some of the mail servers used by techmango.net are shared with other domains: durhamdistillery.com, lasalle.edu.pa, ns500758.ns500758.ns500759.ns500698.ns500758.ns500735.ns500735.ns500736.ns500735.ns500708.ns500708.ns500708.ns500652.trackreceptor.com and two others among them.

These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx2.googlemail.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com maps to two IP addresses — 142.251.163.26 and 2607:f8b0:4004:c23::1a.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.

These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 192.178.234.27 IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.26 IP addresses.