`attainable.tech`

DNSSEC	⚠️ Not signed
A	100.31.31.136^{🇺🇸 Amazon100.24.0.0/13 EC2 IAD prefix}
		PTR	`ec2-100-31-31-136.compute-1.amazonaws.com`
NS	`ns47.domaincontrol.com` ⭐
		A	2603:5:2172::18^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns47.domaincontrol.com`
		A	97.74.103.24^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns47.domaincontrol.com`
NS	`ns48.domaincontrol.com`
		A	2603:5:2272::18^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns48.domaincontrol.com`
		A	173.201.71.24^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns48.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c06::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dz-in-f27.1e100.net`
		A	142.251.2.26^{🇺🇸 Google142.251.2.0/24}
			PTR	`dl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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:4013:c1e::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f27.1e100.net`
		A	192.178.213.27^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-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	2607:f8b0:4003:c4a::1b^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f27.1e100.net`
		A	142.251.96.26^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f26.1e100.net`
TXT	`google-site-verification=q6T78Ik6tzmbFXltl9F_PT9psjr4CtdF7zlkbQNbTgo`
TXT	`v=spf1 include:dc-aa8e722993._spfm.attainable.tech ~all`
SOA	`ns47.domaincontrol.com`dns@jomax.net 2026-03-01 #0

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

⚠️ On DNS blocklist: tif

Same first word

attainable.ca

attainable.net

attainable.de

attainable.com

attainable.tech

DNS History

8 records (8 active, 0 former)

●NSns47.domaincontrol.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●NSns48.domaincontrol.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●MXalt1.aspmx.l.google.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●MXalt2.aspmx.l.google.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●MXalt3.aspmx.l.google.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●MXalt4.aspmx.l.google.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●MXaspmx.l.google.com2026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

●A100.31.31.1362026-03-19 → 2026-03-27 · 2 obs

● 2026-03-19 10:48:06
● 2026-03-27 03:19:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
attainable.tech	ns48.domaincontrol.com, ns47.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.71.24

NS records: ns48.domaincontrol.com, ns47.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for attainable.tech (unsigned zone)

⏱️ Timing

Total: 380ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`100.31.31.136`
NS	2	`ns47.domaincontrol.com, ns48.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=q6T78Ik6tzmbFXl, v=spf1 include:dc-aa8e722993._spfm.attai`
SOA	1	`ns47.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

attainable.tech points to an IP address: 100.31.31.136.

Name Servers

Two name servers ns47.domaincontrol.com and ns48.domaincontrol.com handle the delegation for attainable.tech.

attainable.tech shares the same name server setup as other domains, for instance orientalink.net, ddarzi.com, thiss.co, mp3-muensterland.com and wpk9.net.