telecomsquare.us - robtex.com
Search for stuff
telecomsquare.us
us
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.cctld.us ⭐ 🔒 | ||||||
| NS | b.cctld.us 🔒 | ||||||
| NS | f.cctld.us 🔒 | ||||||
| NS | k.cctld.us 🔒 | ||||||
| NS | m.cctld.us 🔒 | ||||||
| NS | n.cctld.us 🔒 | ||||||
| NS | w.cctld.us 🔒 | ||||||
| NS | x.cctld.us 🔒 | ||||||
| NS | y.cctld.us 🔒 | ||||||
| SOA | a.cctld.usadmin@tldns.godaddy serial=1771291699 | ||||||
Up
blog.telecomsquare.us |
Same first word
telecomsquare.co.jp |
telecomsquare.hk |
telecomsquare.tw |
telecomsquare.us |
Similar names
DNS History
10 records (7 active, 3 former)
●NS01.dnsv.jp2026-02-16 → 2026-02-18 · 3 obs
● 2026-02-16 08:35:18
● 2026-02-18 20:05:34
●NS02.dnsv.jp2026-02-16 → 2026-02-18 · 3 obs
● 2026-02-16 08:35:18
● 2026-02-18 20:05:34
●NS03.dnsv.jp2026-02-16 → 2026-02-18 · 3 obs
● 2026-02-16 08:35:18
● 2026-02-18 20:05:34
●NS04.dnsv.jp2026-02-16 → 2026-02-18 · 3 obs
● 2026-02-16 08:35:18
● 2026-02-18 20:05:34
○NSns1.netfirms.com2015-06-01 → 2016-12-22 · 4 obs
● 2016-12-22 16:50:06
○ 2026-02-16 08:35:18
○ 2026-02-18 20:05:34
○NSns2.netfirms.com2015-06-01 → 2016-12-22 · 4 obs
● 2016-12-22 16:50:06
○ 2026-02-16 08:35:18
○ 2026-02-18 20:05:34
●MXin1-smtp.messagingengine.com2015-06-01 → 2026-02-18 · 2 obs
● 2026-02-18 20:05:34
●MXin2-smtp.messagingengine.com2016-04-04 → 2026-02-18 · 3 obs
● 2016-04-04 19:20:26
● 2026-02-18 20:05:34
●A104.207.250.542016-04-04 → 2026-02-18 · 3 obs
● 2016-04-04 19:20:26
● 2026-02-18 20:05:34
○A192.240.176.2012015-06-01 → 2016-01-03 · 4 obs
● 2016-01-03 14:49:10
○ 2016-04-04 19:20:26
○ 2026-02-18 20:05:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| telecomsquare.us | 03.dnsv.jp, 01.dnsv.jp, 02.dnsv.jp, 04.dnsv.jp | - |
✅ Authoritative Response
Server: 157.7.34.53
NS records: 03.dnsv.jp, 01.dnsv.jp, 02.dnsv.jp, 04.dnsv.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telecomsquare.us (unsigned zone)
⏱️ Timing
Total: 487ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 104.207.250.54 |
| NS | 4 | 01.dnsv.jp, 02.dnsv.jp... |
| MX | 2 | in1-smtp.messagingengine.com (pri: 10), in2-smtp.messagingengine.com (pri: 20) |
| TXT | 1 | v=spf1 ip4:66.96.128.0/18 ?all |
| SOA | 1 | 01.dnsv.jp hostmaster.dnsv.jp |
AI analysis
telecomsquare.us is parent of blog.telecomsquare.us.
telecomsquare.us points to a single IP: 104.207.250.54.
telecomsquare.us is delegated to four name servers: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp and 04.dnsv.jp.
telecomsquare.us at least partially shares its name servers with other domains, for instance benry.com, ction.co.jp, cyokodog.net, skludtu.com and nbdw.jp.
Two IPs per host:
01.dnsv.jp points to 2400:8500:3300::53 and 157.7.32.53.
03.dnsv.jp points to 2400:8500:3000::53 and 157.7.34.53.
04.dnsv.jp points to 2400:8500:3fff::53 and 157.7.35.53.
One IP per host:
02.dnsv.jp points to 157.7.33.53.
Two mail servers in1-smtp.messagingengine.com and in2-smtp.messagingengine.com handle telecomsquare.us.
telecomsquare.us uses the same mail server setup as other domains such as webkit.net, holmerin.net, yzemail.com, st-c.info and artemaeon.com.
telecomsquare.us shares mail servers with other domains at least in part, for instance carolina-core.swiftnode.net, realms.org and gandhsoutheast.co.uk.
Eight IP numbers for the first set:
The host name in1-smtp.messagingengine.com points to 103.168.172.216, 103.168.172.217, 103.168.172.218, 103.168.172.219, 103.168.172.220, 103.168.172.221, 103.168.172.222 and 103.168.172.223.
Four IP numbers for the second set:
The host name in2-smtp.messagingengine.com points to 202.12.124.216, 202.12.124.217, 202.12.124.218 and 202.12.124.219.