fetchingcommunications.com - dns.ninja

`fetchingcommunications.com`

DNSSEC	⚠️ Not signed
A	159.135.1.18^{🇺🇸 LiquidWeb-AZ159.135.0.0/19 Liquidweb Inc}
NS	`dns1.stabletransit.com` ⭐
		A	69.20.95.4^{🇺🇸 RACKSPACE-DFW69.20.95.0/24 Rackspace, 5000 Walzem Road, San Antonio, TX 78218}
			PTR	`ns.rackspace.com`
NS	`dns2.stabletransit.com`
		A	65.61.188.4^{🇺🇸 RACKSPACE-LON65.61.188.0/24 Rackspace, 5000 Walzem Road, San Antonio, TX 78218}
			PTR	`ns2.rackspace.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-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::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.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.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 a mx ptr ?all`
TXT	`google-site-verification=2qQdL2U-mXRcg5nx9xi5wIM0cbCuJF1wFetR5rpFzmU`
SOA	`dns1.stabletransit.com`ipadmin@stabletransit.com serial=1493817585

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

Subdomains

www.fetchingcommunications.com

Same first word

fetchingcommunications.com

DNS History

18 records (8 active, 10 former)

●NSdns1.stabletransit.com2026-03-22 → 2026-08-14 · 3 obs

○ 2016-11-28 05:59:26
● 2026-03-22 07:26:58
● 2026-08-14 18:19:24

●NSdns2.stabletransit.com2026-03-22 → 2026-08-14 · 3 obs

○ 2016-11-28 05:59:26
● 2026-03-22 07:26:58
● 2026-08-14 18:19:24

○NSns1.bluehost.com2015-05-11 → 2016-11-28 · 5 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2016-11-28 05:59:26
○ 2026-03-22 07:26:58
○ 2026-08-14 18:19:24

○NSns1.esnet.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 00:24:34
○ 2015-05-11 13:41:04
○ 2026-08-14 18:19:24

○NSns2.bluehost.com2015-05-11 → 2016-11-28 · 5 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2016-11-28 05:59:26
○ 2026-03-22 07:26:58
○ 2026-08-14 18:19:24

○NSns2.esnet.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 00:24:34
○ 2015-05-11 13:41:04
○ 2026-08-14 18:19:24

○NSns3.esnet.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 00:24:34
○ 2015-05-11 13:41:04
○ 2026-08-14 18:19:24

○NSns4.esnet.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 00:24:34
○ 2015-05-11 13:41:04
○ 2026-08-14 18:19:24

●MXalt1.aspmx.l.google.com2015-05-11 → 2026-08-14 · 3 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2026-08-14 18:19:24

●MXalt2.aspmx.l.google.com2015-05-11 → 2026-08-14 · 3 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2026-08-14 18:19:24

●MXalt3.aspmx.l.google.com2015-05-11 → 2026-08-14 · 3 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2026-08-14 18:19:24

●MXalt4.aspmx.l.google.com2015-05-11 → 2026-08-14 · 3 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2026-08-14 18:19:24

●MXaspmx.l.google.com2015-05-11 → 2026-08-14 · 3 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2026-08-14 18:19:24

○MXmx.esnet.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 00:24:34
○ 2015-05-11 13:41:04
○ 2026-08-14 18:19:24

○A108.179.230.1462016-03-19 → 2016-11-28 · 5 obs

○ 2015-12-20 11:50:10
● 2016-03-19 12:33:52
● 2016-11-28 05:59:26
○ 2026-03-22 07:26:58
○ 2026-08-14 18:19:24

●A159.135.1.182026-03-22 → 2026-08-14 · 3 obs

○ 2016-11-28 05:59:26
● 2026-03-22 07:26:58
● 2026-08-14 18:19:24

○A208.38.140.912008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 00:24:34
○ 2015-05-11 13:41:04
○ 2026-08-14 18:19:24

○A50.87.218.1212015-05-11 → 2015-12-20 · 5 obs

○ 2008-03-20 00:24:34
● 2015-05-11 13:41:04
● 2015-12-20 11:50:10
○ 2016-03-19 12:33:52
○ 2026-08-14 18:19:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
fetchingcommunications.com	dns1.stabletransit.com, dns2.stabletransit.com	2 records

✅ Authoritative Response

Server:65.61.188.4

NS records: dns1.stabletransit.com, dns2.stabletransit.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fetchingcommunications.com (unsigned zone)

⏱️ Timing

Total: 344ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`159.135.1.18`
NS	2	`dns1.stabletransit.com, dns2.stabletransit.com`
MX	5	`aspmx.l.google.com (pri: 1), alt4.aspmx.l.google.com (pri: 10)...`
TXT	2	`v=spf1 a mx ptr ?all, google-site-verification=2qQdL2U-mXRcg5n`
SOA	1	`dns1.stabletransit.com ipadmin.stabletra`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns1.stabletransit.com, dns2.stabletransit.com)

Analysis

Hierarchy

www.fetchingcommunications.com is a subdomain of fetchingcommunications.com.

IP Addresses

fetchingcommunications.com directs to one IP number, which is 159.135.1.18.

There are other host names — www.fetchingcommunications.com among them — that share IP numbers with fetchingcommunications.com.

Name Servers

DNS delegation for fetchingcommunications.com points to two name servers: dns1.stabletransit.com and dns2.stabletransit.com.

fetchingcommunications.com has the same name server delegation as a number of other domains, such as gotlocations.com, rcda.co, mustbeonline.com and two more.

The name servers of fetchingcommunications.com overlap at least partially with those of other domains — among them suremelt.net, beansbistro.com, necs.biz and two more.

These name servers are routinely co-deployed with the name servers ns.rackspace.com, ns2.rackspace.com, dns.stabletransit.com and two others.

Both dns1.stabletransit.com and dns2.stabletransit.com have a single IP address each — dns1.stabletransit.com resolves to 69.20.95.4 while dns2.stabletransit.com resolves to 65.61.188.4.

Mail Servers

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

fetchingcommunications.com shares at least some of its mail servers with other domains — for example ns500734.ns500734.ns500699.ns500699.ns500693.ns500734.ns500588.ns500588.ns500588.ns500699.ns500699.ns500588.ns500632.ns500632.ns500632.ns500110.dtrkdll.com, ns500731.ns500754.ns500754.ns500742.ns500671.ns500731.ns500742.ns500704.ns500678.ns500688.ns500671.ns500688.ns500688.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500759.ns500759.ns500759.ns500758.ns500736.ns500735.ns500736.ns500735.ns500735.ns500708.ns500576.ns500576.ns500619.ns500576.trackreceptor.com and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com has two IP addresses: 142.251.167.26 and 2607:f8b0:4004:c25::1b.

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

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com has two IP addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.

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