goconnect.mx - robtex.com
goconnect.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.markmonitor.com ⚠️ Not in zone NS records | ||||||
| A | 2620:10a:80a8::1🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.160.1🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| NS | ns2.markmonitor.com ⚠️ Not in zone NS records | ||||||
| A | 2001:67c:10b8::1🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net | ||||||
| PTR | ns2.markmonitor.com | ||||||
| A | 176.97.158.1🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net | ||||||
| NS | ns3.markmonitor.com ⚠️ Not in zone NS records | ||||||
| A | 2620:10a:80a9::1🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.161.1🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| NS | ns4.markmonitor.com ⚠️ Not in zone NS records | ||||||
| A | 2001:67c:1bc::1🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast | ||||||
| PTR | ns1.markmonitor.com | ||||||
| A | 192.174.68.1🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net | ||||||
mx
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | m.mx-ns.mx ⭐ | ||||||
| NS | c.mx-ns.mx | ||||||
| NS | e.mx-ns.mx | ||||||
| NS | i.mx-ns.mx | ||||||
| NS | o.mx-ns.mx | ||||||
| NS | x.mx-ns.mx | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1784001845 | ||||||
Same first word
Similar names
ogconnect.info |
concogent.nl |
connectgo.com |
congentco.com |
ogconnect.com |
connectgo.net |
ogconnect.nu |
ogconnect.net |
DNS History
4 records (4 active, 0 former)
●NSns1.markmonitor.com2026-06-22 → 2026-07-14 · 2 obs
● 2026-07-14 04:54:36
●NSns2.markmonitor.com2026-06-22 → 2026-07-14 · 2 obs
● 2026-07-14 04:54:36
●NSns3.markmonitor.com2026-06-22 → 2026-07-14 · 2 obs
● 2026-07-14 04:54:36
●NSns4.markmonitor.com2026-06-22 → 2026-07-14 · 2 obs
● 2026-07-14 04:54:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| goconnect.mx | ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com | - |
✅ Authoritative Response
Server:192.174.68.1
NS records: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for goconnect.mx (unsigned zone)
⏱️ Timing
Total: 995ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The authoritative name servers for goconnect.mx are ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com.
goconnect.mx has at least partial name server overlap with other domains, such as keyventurepartners.net, regeneronfoundation.net, amazonsooq.com and two others.
These name servers tend to appear together with the name servers ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.
ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com all point to exactly two IP numbers each: ns1.markmonitor.com → 149.112.160.1 and 2620:10a:80a8::1; ns2.markmonitor.com → 176.97.158.1 and 2001:67c:10b8::1; ns3.markmonitor.com → 149.112.161.1 and 2620:10a:80a9::1; ns4.markmonitor.com → 192.174.68.1 and 2001:67c:1bc::1.