goconnect.mx - dns.ninja
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 | ||||||
| PTR | ns2.markmonitor.com | ||||||
| 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 | ||||||
| PTR | ns1.markmonitor.com | ||||||
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=1784359655 | ||||||
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-18 · 2 obs
● 2026-07-18 07:31:28
●NSns2.markmonitor.com2026-06-22 → 2026-07-18 · 2 obs
● 2026-07-18 07:31:28
●NSns3.markmonitor.com2026-06-22 → 2026-07-18 · 2 obs
● 2026-07-18 07:31:28
●NSns4.markmonitor.com2026-06-22 → 2026-07-18 · 2 obs
● 2026-07-18 07:31:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx... | - |
| goconnect.mx | ns3.markmonitor.com, ns4.markmonitor.com, ns1.markmonitor.com, ns2.markmonitor.com | - |
✅ Authoritative Response
Server:149.112.161.1
NS records: ns3.markmonitor.com, ns4.markmonitor.com, ns1.markmonitor.com, ns2.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for goconnect.mx (unsigned zone)
⏱️ Timing
Total: 884ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The domain goconnect.mx is delegated to these four name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com.
goconnect.mx partially shares its NS delegation with several other domains, including keyventurepartners.net, regeneronfoundation.net, amazonsooq.com and two others.
These name servers regularly co-occur 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 each carry two IP addresses. ns1.markmonitor.com has 149.112.160.1 and 2620:10a:80a8::1; ns2.markmonitor.com has 176.97.158.1 and 2001:67c:10b8::1; ns3.markmonitor.com has 149.112.161.1 and 2620:10a:80a9::1; ns4.markmonitor.com has 192.174.68.1 and 2001:67c:1bc::1.