mipdocconnect.com - robtex.com
mipdocconnect.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1783988697 | ||||||
Same first word
mipdocconnect.com |
DNS History
9 records (6 active, 3 former)
●NSns1.netnames.net2015-06-01 → 2026-07-14 · 2 obs
● 2026-07-14 00:52:56
●NSns2.netnames.net2015-06-01 → 2026-07-14 · 2 obs
● 2026-07-14 00:52:56
●NSns5.netnames.net2015-06-01 → 2026-07-14 · 2 obs
● 2026-07-14 00:52:56
●NSns6.netnames.net2015-06-01 → 2026-07-14 · 2 obs
● 2026-07-14 00:52:56
○MXrelay1.netnames.net2015-06-01 → 2017-04-10 · 4 obs
● 2017-04-10 21:40:48
○ 2026-04-08 23:09:22
○ 2026-07-14 00:52:56
○MXrelay2.netnames.net2015-06-01 → 2017-04-10 · 4 obs
● 2017-04-10 21:40:48
○ 2026-04-08 23:09:22
○ 2026-07-14 00:52:56
○A185.26.230.1292015-06-01 → 2017-04-10 · 4 obs
● 2017-04-10 21:40:48
○ 2026-04-08 23:09:22
○ 2026-07-14 00:52:56
●A54.217.224.1342026-04-08 → 2026-07-14 · 3 obs
● 2026-04-08 23:09:22
● 2026-07-14 00:52:56
●A54.228.228.2102026-04-08 → 2026-07-14 · 3 obs
● 2026-04-08 23:09:22
● 2026-07-14 00:52:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| mipdocconnect.com | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | - |
✅ Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mipdocconnect.com (unsigned zone)
⏱️ Timing
Total: 950ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 54.228.228.210, 54.217.224.134 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
Analysis
IP Addresses
mipdocconnect.com resolves to the IP addresses 54.217.224.134 and 54.228.228.210
ice-x.com, mipcontent360.com, ec2-54-228-228-210.eu-west-1.compute.amazonaws.com and two other host names share IP numbers with mipdocconnect.com.
Name Servers
The authoritative name servers for mipdocconnect.com are ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
mipdocconnect.com partially shares its NS delegation with several other domains, including ninjakitchen.com.ru, kashnkarry.com, speakouthannaford.org and two others.
These name servers are regularly seen alongside ns7.netnames.net and ns8.netnames.net as name servers.
ns1.netnames.net and ns5.netnames.net both point to 156.154.130.100 and 2610:a1:1022::100; ns2.netnames.net and ns6.netnames.net both point to 156.154.131.100 and 2610:a1:1023::100 — all four hostnames (ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net) resolve to exactly two IP addresses.
ns1.netnames.net along with ns5.netnames.net each resolve to 2610:a1:1022::100 IP addresses.
ns1.netnames.net along with ns5.netnames.net each resolve to 156.154.130.100 IP addresses.
ns2.netnames.net along with ns6.netnames.net each resolve to 2610:a1:1023::100 IP addresses.
ns2.netnames.net along with ns6.netnames.net each resolve to 156.154.131.100 IP addresses.