`pittsburgh-colocation.com`

DNSSEC	⚠️ Not signed
A	204.16.243.9^{🇺🇸 TERASWITCH204.16.243.0/24 BLK4}
		PTR	`www3.pit.tblive.com`
NS	`ns1.tblive.com` ⭐
		A	74.118.138.119^{🇺🇸 TERASWITCH74.118.138.0/24 PIT1}
NS	`ns2.tblive.com`
		A	74.118.138.183^{🇺🇸 TERASWITCH74.118.138.0/24 PIT1}
NS	`ns3.tblive.com` ⚠️ Not in parent delegation
		A	204.16.243.13^{🇺🇸 TERASWITCH204.16.243.0/24 BLK4}
MX	`pittsburgh-colocation.com` ⭐
		A	204.16.243.9^{🇺🇸 TERASWITCH204.16.243.0/24 BLK4}
			PTR	`www3.pit.tblive.com`
TXT	`v=spf1 ip4:204.16.243.9 ip4:74.118.138.32 ip4:18.221.0.20 ip4:204.16.241.8 ip...`
SOA	`ns1.tblive.com`sales@tblive.com 2026-04-22 #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=1777055112

MX for

pittsburgh-colocation.com

Same first word

pittsburgh-colocation.com

DNS History

7 records (5 active, 2 former)

●NSns1.tblive.com2015-08-14 → 2026-04-24 · 2 obs

● 2015-08-14 02:50:02
● 2026-04-24 18:31:18

●NSns2.tblive.com2015-08-14 → 2026-04-24 · 2 obs

● 2015-08-14 02:50:02
● 2026-04-24 18:31:18

●NSns3.tblive.com2015-08-14 → 2026-04-24 · 2 obs

● 2015-08-14 02:50:02
● 2026-04-24 18:31:18

●MXpittsburgh-colocation.com2015-08-14 → 2026-04-24 · 2 obs

● 2015-08-14 02:50:02
● 2026-04-24 18:31:18

○A204.16.241.132015-08-14 → 2017-03-27 · 4 obs

● 2015-08-14 02:50:02
● 2017-03-27 19:31:28
○ 2020-03-27 04:09:52
○ 2026-04-24 18:31:18

○A204.16.241.72020-03-27 → 2020-03-27 · 4 obs

○ 2017-03-27 19:31:28
● 2020-03-27 04:09:52
○ 2026-04-07 00:27:38
○ 2026-04-24 18:31:18

●A204.16.243.92026-04-07 → 2026-04-24 · 3 obs

○ 2020-03-27 04:09:52
● 2026-04-07 00:27:38
● 2026-04-24 18:31:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
pittsburgh-colocation.com	ns2.tblive.com, ns1.tblive.com	2 records

✅ Authoritative Response

Server:74.118.138.119

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pittsburgh-colocation.com (unsigned zone)

⏱️ Timing

Total: 251ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`204.16.243.9`
NS	3	`ns2.tblive.com, ns3.tblive.com...`
MX	1	`pittsburgh-colocation.com (pri: 0)`
TXT	1	`v=spf1 ip4:204.16.243.9 ip4:74.118.138.3`
SOA	1	`ns1.tblive.com sales.tblive.com`

📌 Glue Records Collected

Total: 2

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

Analysis

Mail Server Role

pittsburgh-colocation.com serves as the mail server for pittsburgh-colocation.com.

IP Addresses

pittsburgh-colocation.com resolves to one IP number: 204.16.243.9.

Other host names, for instance mail.burdelskilaw.com, specialtycleaningservicesllc.com, eliteva.biz, www.tblive.com and elitevirtualassistance.net share IP numbers with pittsburgh-colocation.com.

Name Servers

pittsburgh-colocation.com is delegated to three name servers: ns1.tblive.com, ns2.tblive.com and ns3.tblive.com.

pittsburgh-colocation.com at least partially shares name servers with other domains, including elitevirtualassistance.org, instanttutorets.com, www3.pit.tblive.com, pittsburghcolo.com and accomods.com.

Host names with a single IP:

ns1.tblive.com points to 74.118.138.119; ns2.tblive.com points to 74.118.138.183; ns3.tblive.com points to 204.16.243.13.

Mail Servers

pittsburgh-colocation.com is handled by a single mail server, pittsburgh-colocation.com.

Host name pittsburgh-colocation.com resolves to a single IP: 204.16.243.9.

pittsburgh-colocation.com - robtex.com