idaltech.com - dns.ninja

`idaltech.com`

DNSSEC	⚠️ Not signed
A	3.144.36.173^{🇺🇸 Amazon3.144.0.0/13 EC2 CMH Prefix}
		PTR	`ec2-3-144-36-173.us-east-2.compute.amazonaws.com`
NS	`ns1.domain.com` ⭐
		A	172.64.52.73^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.domain.com`
		A	172.64.53.117^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.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.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.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`
MX	`mx.idaltech.com`⁽³⁰⁾
		A	66.96.140.182^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
			PTR	`182.140.96.66.static.eigbox.net`
		A	66.96.140.183^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
			PTR	`183.140.96.66.static.eigbox.net`
TXT	`google-site-verification=wzlWwGsQIGzCrSjOJAgr4XrWF0w_3yTWvxGNs54XY78`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`NS1.DOMAIN.com`dnsadmin@DOMAIN.com serial=125100713

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

Subdomains

mx.idaltech.com

Same first word

idaltech.com

Similar names

DNS History

10 records (9 active, 1 former)

●NSns1.domain.com2016-12-18 → 2026-06-23 · 2 obs

● 2016-12-18 20:43:04
● 2026-06-23 08:17:06

●NSns2.domain.com2016-12-18 → 2026-06-23 · 2 obs

● 2016-12-18 20:43:04
● 2026-06-23 08:17:06

●MXalt1.aspmx.l.google.com2026-03-24 → 2026-06-23 · 3 obs

○ 2016-12-18 20:43:04
● 2026-03-24 22:20:46
● 2026-06-23 08:17:06

●MXalt2.aspmx.l.google.com2026-03-24 → 2026-06-23 · 3 obs

○ 2016-12-18 20:43:04
● 2026-03-24 22:20:46
● 2026-06-23 08:17:06

●MXalt3.aspmx.l.google.com2026-03-24 → 2026-06-23 · 3 obs

○ 2016-12-18 20:43:04
● 2026-03-24 22:20:46
● 2026-06-23 08:17:06

●MXalt4.aspmx.l.google.com2026-03-24 → 2026-06-23 · 3 obs

○ 2016-12-18 20:43:04
● 2026-03-24 22:20:46
● 2026-06-23 08:17:06

●MXaspmx.l.google.com2026-03-24 → 2026-06-23 · 3 obs

○ 2016-12-18 20:43:04
● 2026-03-24 22:20:46
● 2026-06-23 08:17:06

●MXmx.idaltech.com2016-12-18 → 2026-06-23 · 2 obs

● 2016-12-18 20:43:04
● 2026-06-23 08:17:06

●A3.144.36.1732026-03-24 → 2026-06-23 · 3 obs

○ 2017-10-30 10:23:50
● 2026-03-24 22:20:46
● 2026-06-23 08:17:06

○A66.96.162.1442016-12-18 → 2017-10-30 · 4 obs

● 2016-12-18 20:43:04
● 2017-10-30 10:23:50
○ 2026-03-24 22:20:46
○ 2026-06-23 08:17:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net...	-
idaltech.com	ns2.domain.com, ns1.domain.com	2 records

✅ Authoritative Response

Server:172.64.52.73

NS records: ns2.domain.com, ns1.domain.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for idaltech.com (unsigned zone)

⏱️ Timing

Total: 239ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.144.36.173`
NS	2	`ns1.domain.com, ns2.domain.com`
MX	6	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=wzlWwGsQIGzCrSj, v=spf1 include:_spf.google.com ~all`
SOA	1	`NS1.DOMAIN.com dnsadmin.DOMAIN.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2.domain.com, ns1.domain.com)

Analysis

Hierarchy

idaltech.com is a parent domain of mx.idaltech.com.

IP Addresses

idaltech.com has exactly one IP address — 3.144.36.173.

Host names like ec2-3-144-36-173.us-east-2.compute.amazonaws.com are further examples that share IP numbers with idaltech.com.

Name Servers

Two name servers handle the delegation for idaltech.com: ns1.domain.com and ns2.domain.com.

The name server configuration of idaltech.com is shared with other domains, for instance circlebarmory.com, mind-patterns.com, sharongarman.com and two others.

idaltech.com shares at least some of its name servers with other domains, including theaphrodesianwoman.com, fbcspace.com, mindrumprecision.com and two others.

These name servers are frequently paired with the name servers ns1.yourhostingaccount.com, ns2.yourhostingaccount.com and ns3.domain.com.

ns1.domain.com and ns2.domain.com each resolve to one IP number: ns1.domain.com points to 172.64.52.73 and ns2.domain.com points to 172.64.53.117.

Mail Servers

idaltech.com is handled by 6 mail servers: mx.idaltech.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.

At least some of the mail servers used by idaltech.com are shared with other domains: amcapla.com, sath.com.tr, cityworks.lv and two others among them.

It is common to find these mail servers paired with the mail servers alt2.aspmx.l.google.com, alt4.aspmx.l.google.com and alt3.aspmx.l.google.com, as well as two others.

Host names pointing to two IP addresses:

mx.idaltech.com resolves to two addresses: 66.96.140.182 and 66.96.140.183.

aspmx.l.google.com resolves to two addresses: 142.251.163.27 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.

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

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

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