connect.am - robtex.com
connect.am
| DNSSEC | ⚠️ Not signed | ||||||
| NS | cp1.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:80:11::1🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41 | ||||||
| A | 158.106.136.90🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX | ||||||
| NS | cp2.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:509:731::a🇺🇸 PRIVATESYSTEMS2600:4c00:500::/40 IPv6 subnet at SEF003 | ||||||
| A | 108.160.157.7🇺🇸 PRIVATESYSTEMS108.160.156.0/22 PrivateSystems Networks WA | ||||||
| NS | cp3.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:80:9::1🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41 | ||||||
| A | 158.106.136.36🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX | ||||||
| NS | cp4.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:80:11::1🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41 | ||||||
| A | 158.106.136.90🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX | ||||||
am
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-pri.nic.am ⭐ | ||||||
| NS | fork.sth.dnsnode.net | ||||||
| NS | ns-cdn.amnic.net | ||||||
| NS | ns-pch.amnic.net | ||||||
| TXT | processed at 2026-06-26 00:20:00 UTC (1782433200) | ||||||
| SOA | ns-pri.nic.amdns@amnic.net serial=1782433200 | ||||||
Previously MX for
connect.am |
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
●NScp1.privatesystems.net2026-06-24 → 2026-06-26 · 3 obs
● 2026-06-24 10:42:02
● 2026-06-26 00:54:04
●NScp2.privatesystems.net2026-06-24 → 2026-06-26 · 3 obs
● 2026-06-24 10:42:02
● 2026-06-26 00:54:04
●NScp3.privatesystems.net2026-06-24 → 2026-06-26 · 3 obs
● 2026-06-24 10:42:02
● 2026-06-26 00:54:04
●NScp4.privatesystems.net2026-06-24 → 2026-06-26 · 3 obs
● 2026-06-24 10:42:02
● 2026-06-26 00:54:04
○NSns1.abcinsight.com2015-08-14 → 2016-12-24 · 4 obs
● 2016-12-24 22:35:20
○ 2026-06-24 10:42:02
○ 2026-06-26 00:54:04
○NSns2.abcinsight.com2015-08-14 → 2016-12-24 · 4 obs
● 2016-12-24 22:35:20
○ 2026-06-24 10:42:02
○ 2026-06-26 00:54:04
○MXconnect.am2015-08-14 → 2016-12-24 · 4 obs
● 2016-12-24 22:35:20
○ 2026-06-24 10:42:02
○ 2026-06-26 00:54:04
○A192.185.93.2532015-08-14 → 2016-12-24 · 4 obs
● 2016-12-24 22:35:20
○ 2026-06-24 10:42:02
○ 2026-06-26 00:54:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| am | fork.sth.dnsnode.net, ns-cdn.amnic.net, ns-pch.amnic.net, ns-pri.nic.am | - |
| connect.am | cp4.privatesystems.net, cp3.privatesystems.net, cp1.privatesystems.net, cp2.privatesystems.net | - |
✅ Authoritative Response
Server:108.160.157.7
NS records: cp4.privatesystems.net, cp3.privatesystems.net, cp1.privatesystems.net, cp2.privatesystems.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for connect.am (unsigned zone)
⏱️ Timing
Total: 3399ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The NS records for connect.am point to four name servers: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net.
There is at least partial name server overlap between connect.am and other domains — 24-hr.com, sotoasty.com, kopaonik.org.rs and two more among them.
These four hostnames each have two IP addresses. cp1.privatesystems.net → 158.106.136.90 and 2600:4c00:80:11::1. cp2.privatesystems.net → 108.160.157.7 and 2600:4c00:509:731::a. cp3.privatesystems.net → 158.106.136.36 and 2600:4c00:80:9::1. cp4.privatesystems.net → 158.106.136.90 and 2600:4c00:80:11::1. cp1.privatesystems.net and cp4.privatesystems.net point to identical addresses.
Both cp1.privatesystems.net and cp4.privatesystems.net resolve to 2600:4c00:80:11::1 IP addresses each.
Both cp1.privatesystems.net and cp4.privatesystems.net resolve to 158.106.136.90 IP addresses each.