teams-meet.cloud - robtex.com
teams-meet.cloud
cloud
| 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.comtrs-ops@tucows.com serial=1785414029 | ||||||
Same first word
teams-meet.cc |
teams-meet.live |
teams-meet.cloud |
teams-meet.us |
teams-meet.store |
teams-meet.team |
teams-meet.online |
teams-meet.in |
teams-meet.co |
teams-meet.com.co |
teams-meet.xyz |
teams-meet.site |
teams-meet.us.com |
DNS History
9 records (9 active, 0 former)
●NSdns1.namecheaphosting.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●NSdns1.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●NSdns2.namecheaphosting.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●NSdns2.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●MXeforward1.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●MXeforward2.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●MXeforward3.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●MXeforward4.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
●MXeforward5.registrar-servers.com2026-07-28 → 2026-07-30 · 2 obs
● 2026-07-30 12:23:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.net, ns01.trs-dns.com, ns10.trs-dns.info, ns10.trs-dns.org | - |
| teams-meet.cloud | dns1.namecheaphosting.com, dns2.namecheaphosting.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.namecheaphosting.com, dns2.namecheaphosting.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for teams-meet.cloud (unsigned zone)
⏱️ Timing
Total: 672ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 1 | v=spf1 include:spf.efwd.registrar-server |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
Name Servers
Four name servers handle the delegation for teams-meet.cloud: dns1.namecheaphosting.com, dns2.namecheaphosting.com, dns1.registrar-servers.com and dns2.registrar-servers.com.
teams-meet.cloud shares at least some of its name servers with other domains, including boba.me, rubiz.net, imageinks.ca and two others.
These name servers are frequently paired with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.namecheaphosting.com and dns1.registrar-servers.com both point to 156.154.132.200 and 2610:a1:1024::200; dns2.namecheaphosting.com and dns2.registrar-servers.com both point to 156.154.133.200 and 2610:a1:1025::200 — all four hostnames (dns1.namecheaphosting.com, dns2.namecheaphosting.com, dns1.registrar-servers.com and dns2.registrar-servers.com) resolve to exactly two IP addresses.
dns1.namecheaphosting.com along with dns1.registrar-servers.com each resolve to 2610:a1:1024::200 IP addresses.
dns1.namecheaphosting.com along with dns1.registrar-servers.com each resolve to 156.154.132.200 IP addresses.
dns2.namecheaphosting.com along with dns2.registrar-servers.com each resolve to 2610:a1:1025::200 IP addresses.
dns2.namecheaphosting.com along with dns2.registrar-servers.com each resolve to 156.154.133.200 IP addresses.
Mail Servers
Mail for teams-meet.cloud is handled by five mail servers, namely eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
At least some of the mail servers used by teams-meet.cloud are shared with other domains: 4blueskys.ai, nlgapple.com, drat-process.com and two others among them.
These mail servers often appear in conjunction with the mail servers eforward4.registrar-servers.com, eforward5.registrar-servers.com, eforward6.registrar-servers.com and eforward7.registrar-servers.com.
Host names resolving to a single IP address:
The hostname eforward1.registrar-servers.com resolves to 162.255.118.51.
The hostname eforward2.registrar-servers.com resolves to 162.255.118.52.
The hostname eforward3.registrar-servers.com resolves to 162.255.118.51.
The hostname eforward4.registrar-servers.com resolves to 162.255.118.52.
The hostname eforward5.registrar-servers.com resolves to 162.255.118.51.
Three host names point to 162.255.118.51: eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com.
eforward2.registrar-servers.com along with eforward4.registrar-servers.com each resolve to 162.255.118.52 IP addresses.