team.im - robtex.com
team.im
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.c01.tmdcloud.london ⚠️ Not in zone NS records | ||||||
| A | 13.248.158.180🇺🇸 Amazon13.248.144.0/20 | ||||||
| PTR | a79764cc55c0ac9c0.awsglobalaccelerator.com | ||||||
| NS | ns2.c01.tmdcloud.london ⚠️ Not in zone NS records | ||||||
| A | 13.248.158.180🇺🇸 Amazon13.248.144.0/20 | ||||||
| PTR | a79764cc55c0ac9c0.awsglobalaccelerator.com | ||||||
im
| DNSSEC | ⚠️ Not signed | ||||||
| NS | pebbles.iom.com ⭐ | ||||||
| NS | barney.advsys.co.uk | ||||||
| NS | hoppy.iom.com | ||||||
| NS | ns4.ja.net | ||||||
| SOA | pebbles.iom.comdnsadmin@advsys.co.uk serial=1780582502 | ||||||
Same first word
Similar names
DNS History
12 records (2 active, 10 former)
●NSns1.c01.tmdcloud.london2026-06-02 → 2026-06-04 · 3 obs
● 2026-06-02 05:02:48
● 2026-06-04 14:43:48
○NSns1.dnsfarm.org2016-09-30 → 2017-08-11 · 5 obs
● 2016-09-30 08:41:10
● 2017-08-11 00:31:32
○ 2026-06-02 05:02:48
○ 2026-06-04 14:43:48
○NSns1.domainmonster.com2015-08-12 → 2016-07-17 · 4 obs
● 2016-07-17 00:48:36
○ 2016-09-30 08:41:10
○ 2026-06-04 14:43:48
●NSns2.c01.tmdcloud.london2026-06-02 → 2026-06-04 · 3 obs
● 2026-06-02 05:02:48
● 2026-06-04 14:43:48
○NSns2.dnsfarm.org2016-09-30 → 2017-08-11 · 5 obs
● 2016-09-30 08:41:10
● 2017-08-11 00:31:32
○ 2026-06-02 05:02:48
○ 2026-06-04 14:43:48
○NSns2.domainmonster.com2015-08-12 → 2016-07-17 · 4 obs
● 2016-07-17 00:48:36
○ 2016-09-30 08:41:10
○ 2026-06-04 14:43:48
○NSns3.dnsfarm.org2016-09-30 → 2017-08-11 · 5 obs
● 2016-09-30 08:41:10
● 2017-08-11 00:31:32
○ 2026-06-02 05:02:48
○ 2026-06-04 14:43:48
○NSns3.domainmonster.com2015-08-12 → 2016-07-17 · 4 obs
● 2016-07-17 00:48:36
○ 2016-09-30 08:41:10
○ 2026-06-04 14:43:48
○MXmx.emailconfig.com2015-08-12 → 2016-07-17 · 4 obs
● 2016-07-17 00:48:36
○ 2016-09-30 08:41:10
○ 2026-06-04 14:43:48
○A104.131.249.2342016-09-30 → 2016-10-13 · 5 obs
● 2016-09-30 08:41:10
● 2016-10-13 14:50:48
○ 2016-12-15 13:20:46
○ 2026-06-04 14:43:48
○A109.68.33.182015-08-12 → 2016-07-17 · 4 obs
● 2016-07-17 00:48:36
○ 2016-09-30 08:41:10
○ 2026-06-04 14:43:48
○A192.241.143.812016-12-15 → 2017-08-11 · 5 obs
● 2016-12-15 13:20:46
● 2017-08-11 00:31:32
○ 2026-06-02 05:02:48
○ 2026-06-04 14:43:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| im | ns4.ja.net, hoppy.iom.com, barney.advsys.co.uk, pebbles.iom.com | 5 records |
| team.im | ns2.c01.tmdcloud.london, ns1.c01.tmdcloud.london | - |
✅ Authoritative Response
Server:13.248.158.180
NS records: ns2.c01.tmdcloud.london, ns1.c01.tmdcloud.london
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for im (unsigned zone)
⏱️ Timing
Total: 497ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 5
Out-of-bailiwick: 5 (ns4.ja.net, hoppy.iom.com, barney.advsys.co.uk...)
Analysis
Name Servers
The NS records for team.im delegate to ns1.c01.tmdcloud.london and ns2.c01.tmdcloud.london.
team.im shares the same name server setup with other domains, for instance thextasy.com and eskylinegroup.com.
team.im and other domains like almufaddalelectrical.com share at least a portion of their name servers.
It is common to see these name servers used together with name servers ns1.c11.tmdcloud.london and ns2.c11.tmdcloud.london.
Each of ns1.c01.tmdcloud.london and ns2.c01.tmdcloud.london points to exactly one IP address: 13.248.158.180.
ns1.c01.tmdcloud.london and ns2.c01.tmdcloud.london each have 13.248.158.180 IP addresses.