techwarn.com - dns.ninja

`techwarn.com`

DNSSEC	⚠️ Not signed
A	104.199.252.102^{🇹🇼 Google104.199.248.0/21}
		PTR	`102.252.199.104.bc.googleusercontent.com`
NS	`ns-124.awsdns-15.com` ⭐
		A	2600:9000:5300:7c00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-124.awsdns-15.com`
		A	205.251.192.124^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-124.awsdns-15.com`
NS	`ns-1110.awsdns-10.org`
		A	2600:9000:5304:5600::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1110.awsdns-10.org`
		A	205.251.196.86^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1110.awsdns-10.org`
NS	`ns-1835.awsdns-37.co.uk`
		A	2600:9000:5307:2b00::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1835.awsdns-37.co.uk`
		A	205.251.199.43^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1835.awsdns-37.co.uk`
NS	`ns-646.awsdns-16.net`
		A	2600:9000:5302:8600::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-646.awsdns-16.net`
		A	205.251.194.134^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-646.awsdns-16.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	172.253.139.26^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 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::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.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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`1password-site-verification=GT473H7MJFCCBHJSEF2O4LBMQU`
TXT	`v=spf1 include:_spf.google.com ~allatlassian-domain-verification=T3BqFGW0jDDa...`
SOA	`ns-124.awsdns-15.com`awsdns-hostmaster@amazon.com serial=1

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

Previously MX for

techwarn.com

www.techwarn.com

Subdomains

www.techwarn.com

Same first word

techwarn.com

Similar names

DNS History

17 records (10 active, 7 former)

○NSbs21.hostwindsdns.com2015-07-09 → 2016-04-19 · 4 obs

● 2015-07-09 14:16:34
● 2016-04-19 09:26:36
○ 2016-11-06 09:36:22
○ 2026-08-07 10:30:20

○NSbs22.hostwindsdns.com2015-07-09 → 2016-04-19 · 4 obs

● 2015-07-09 14:16:34
● 2016-04-19 09:26:36
○ 2016-11-06 09:36:22
○ 2026-08-07 10:30:20

●NSns-1110.awsdns-10.org2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●NSns-124.awsdns-15.com2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●NSns-1835.awsdns-37.co.uk2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●NSns-646.awsdns-16.net2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

○NSns.inmotionhosting.com2016-11-06 → 2016-11-06 · 4 obs

○ 2016-04-19 09:26:36
● 2016-11-06 09:36:22
○ 2026-03-14 07:56:52
○ 2026-08-07 10:30:20

○NSns2.inmotionhosting.com2016-11-06 → 2016-11-06 · 4 obs

○ 2016-04-19 09:26:36
● 2016-11-06 09:36:22
○ 2026-03-14 07:56:52
○ 2026-08-07 10:30:20

●MXalt1.aspmx.l.google.com2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●MXalt2.aspmx.l.google.com2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●MXalt3.aspmx.l.google.com2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●MXalt4.aspmx.l.google.com2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

●MXaspmx.l.google.com2026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

○MXtechwarn.com2015-07-09 → 2016-11-06 · 4 obs

● 2015-07-09 14:16:34
● 2016-11-06 09:36:22
○ 2026-03-14 07:56:52
○ 2026-08-07 10:30:20

●A104.199.252.1022026-03-14 → 2026-08-07 · 3 obs

○ 2016-11-06 09:36:22
● 2026-03-14 07:56:52
● 2026-08-07 10:30:20

○A23.238.18.2412015-07-09 → 2016-04-19 · 4 obs

● 2015-07-09 14:16:34
● 2016-04-19 09:26:36
○ 2016-11-06 09:36:22
○ 2026-08-07 10:30:20

○A70.39.234.2542016-11-06 → 2016-11-06 · 4 obs

○ 2016-04-19 09:26:36
● 2016-11-06 09:36:22
○ 2026-03-14 07:56:52
○ 2026-08-07 10:30:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, a.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net...	-
techwarn.com	ns-124.awsdns-15.com, ns-646.awsdns-16.net, ns-1110.awsdns-10.org, ns-1835.awsdns-37.co.uk	2 records

✅ Authoritative Response

Server:205.251.192.124

NS records: ns-124.awsdns-15.com, ns-646.awsdns-16.net, ns-1110.awsdns-10.org, ns-1835.awsdns-37.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for techwarn.com (unsigned zone)

⏱️ Timing

Total: 739ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.199.252.102`
NS	4	`ns-1110.awsdns-10.org, ns-124.awsdns-15.com...`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`1password-site-verification=GT473H7MJFCC, v=spf1 include:_spf.google.com ~allatlas`
SOA	1	`ns-124.awsdns-15.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-124.awsdns-15.com, ns-124.awsdns-15.com)

Analysis

Hierarchy

www.techwarn.com is delegated beneath techwarn.com.

IP Addresses

techwarn.com resolves to just one IP address, 104.199.252.102.

Two other host names, along with indago.com.au, with-inc.com and koib.jp, also share IP numbers with techwarn.com.

Name Servers

The NS records for techwarn.com point to four name servers: ns-124.awsdns-15.com, ns-646.awsdns-16.net, ns-1110.awsdns-10.org and ns-1835.awsdns-37.co.uk.

There is at least partial name server overlap between techwarn.com and other domains — ikincet.com, free2flea.com, revolve.io and two more among them.

These name servers frequently co-occur with the name servers ns-543.awsdns-03.net and ns-1216.awsdns-24.org.

All four hostnames — ns-124.awsdns-15.com, ns-646.awsdns-16.net, ns-1110.awsdns-10.org and ns-1835.awsdns-37.co.uk — resolve to two IP numbers apiece: ns-124.awsdns-15.com to 205.251.192.124 and 2600:9000:5300:7c00::1; ns-646.awsdns-16.net to 205.251.194.134 and 2600:9000:5302:8600::1; ns-1110.awsdns-10.org to 205.251.196.86 and 2600:9000:5304:5600::1; ns-1835.awsdns-37.co.uk to 205.251.199.43 and 2600:9000:5307:2b00::1.

Mail Servers

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

There is at least a partial MX overlap between techwarn.com and other domains, including xbrl.io, ns500698.ns500758.ns500759.ns500759.ns500735.ns500735.ns500736.ns500735.ns500736.ns500708.ns500698.ns500698.ns500619.ns500652.ns500576.trackreceptor.com, eigeragency.com and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com resolves to 172.253.139.26 and 2607:f8b0:4004:c25::1b.

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

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

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.26 and 2a00:1450:400c:c23::1b.