tmcommunicationsllc.com - robtex.com
tmcommunicationsllc.com
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.netnstld@verisign-grs.com serial=1784307527 | ||||||
Same first word
tmcommunicationsllc.com |
DNS History
11 records (11 active, 0 former)
●NSns19.domaincontrol.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●NSns20.domaincontrol.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●MXalt1.aspmx.l.google.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●MXalt2.aspmx.l.google.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●MXaspmx.l.google.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●MXaspmx2.googlemail.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●MXaspmx3.googlemail.com2026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●A216.239.32.212026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●A216.239.34.212026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●A216.239.36.212026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
●A216.239.38.212026-03-15 → 2026-07-17 · 2 obs
● 2026-07-17 17:03:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net, e.gtld-servers.net... | - |
| tmcommunicationsllc.com | ns19.domaincontrol.com, ns20.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.109.10
NS records: ns19.domaincontrol.com, ns20.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tmcommunicationsllc.com (unsigned zone)
⏱️ Timing
Total: 202ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 216.239.32.21, 216.239.34.21... |
| NS | 2 | ns19.domaincontrol.com, ns20.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=YR06d6np3g4ebT_, v=spf1 include:_spf.google.com ?all |
| SOA | 1 | ns19.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns19.domaincontrol.com, ns19.domaincontrol.com, ns20.domaincontrol.com...)
Analysis
IP Addresses
tmcommunicationsllc.com resolves to four IP addresses: 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.
Two other host names, along with kniberry.org, dennisnola.com and pryen.org, also share IP numbers with tmcommunicationsllc.com.
Name Servers
tmcommunicationsllc.com uses two name servers for its delegation: ns19.domaincontrol.com and ns20.domaincontrol.com.
tmcommunicationsllc.com shares its NS records with other domains, for example infusion-sys.com, snailps.com, pararrayosqueretaro.com and two others.
The two host names ns19.domaincontrol.com and ns20.domaincontrol.com each have a pair of IP addresses: ns19.domaincontrol.com has 97.74.109.10 and 2603:5:21d0::a, and ns20.domaincontrol.com has 173.201.77.10 and 2603:5:22d0::a.
Mail Servers
tmcommunicationsllc.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between tmcommunicationsllc.com and other domains, including ns500821.ns500841.ns500795.ns500821.ns500794.ns500795.ns500821.ns500795.ns500794.ns500794.ns500795.ns500790.ns500795.lustypartnersfinder.com, cohenlawoffice.com, sicadi.com.br and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.115.26 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.