nissanconnect.com.mx - robtex.com
nissanconnect.com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| A | 54.172.71.199🇺🇸 Amazon54.172.0.0/15 EC2 IAD prefix | ||||||
| PTR | ec2-54-172-71-199.compute-1.amazonaws.com | ||||||
| NS | ns1.markmonitor.com ⭐ | ||||||
| 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 | ||||||
| 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 | ||||||
| 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 | ||||||
| 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 | ||||||
| NS | ns5.markmonitor.com | ||||||
| A | 2620:10a:80a8::2🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| A | 149.112.160.2🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada | ||||||
| TXT | _globalsign-domain-verification=eWKY83v0IIzDLY1pF5zppE2FymidaXJb0gJkllFOZy | ||||||
| SOA | ns1.markmonitor.comhostmaster@markmonitor.com 2021-10-25 #2 | ||||||
com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | m.mx-ns.mx ⭐ ⚠️ Not in parent delegation | ||||||
| NS | c.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | e.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | i.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | o.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | x.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1778345521 | ||||||
Subdomains
www.nissanconnect.com.mx |
Same first word
DNS History
10 records (6 active, 4 former)
○NSns1.ipmirror.com2015-08-03 → 2017-04-06 · 4 obs
● 2017-04-06 19:01:46
○ 2026-03-04 01:30:00
○ 2026-05-09 17:00:46
●NSns1.markmonitor.com2026-03-04 → 2026-05-09 · 3 obs
● 2026-03-04 01:30:00
● 2026-05-09 17:00:46
○NSns2.ipmirror.com2015-08-03 → 2017-04-06 · 4 obs
● 2017-04-06 19:01:46
○ 2026-03-04 01:30:00
○ 2026-05-09 17:00:46
●NSns2.markmonitor.com2026-03-04 → 2026-05-09 · 3 obs
● 2026-03-04 01:30:00
● 2026-05-09 17:00:46
○NSns3.ipmirror.com2015-08-03 → 2017-04-06 · 4 obs
● 2017-04-06 19:01:46
○ 2026-03-04 01:30:00
○ 2026-05-09 17:00:46
●NSns3.markmonitor.com2026-03-04 → 2026-05-09 · 3 obs
● 2026-03-04 01:30:00
● 2026-05-09 17:00:46
●NSns4.markmonitor.com2026-03-04 → 2026-05-09 · 3 obs
● 2026-03-04 01:30:00
● 2026-05-09 17:00:46
●NSns5.markmonitor.com2026-03-04 → 2026-05-09 · 3 obs
● 2026-03-04 01:30:00
● 2026-05-09 17:00:46
○A174.129.25.1702015-08-03 → 2017-04-06 · 4 obs
● 2017-04-06 19:01:46
○ 2026-03-04 01:30:00
○ 2026-05-09 17:00:46
●A54.172.71.1992026-03-04 → 2026-05-09 · 3 obs
● 2026-03-04 01:30:00
● 2026-05-09 17:00:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| nissanconnect.com.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, ns5.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for nissanconnect.com.mx (unsigned zone)
⏱️ Timing
Total: 536ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.172.71.199 |
| NS | 5 | ns4.markmonitor.com, ns5.markmonitor.com... |
| TXT | 1 | _globalsign-domain-verification=eWKY83v0 |
| SOA | 1 | ns1.markmonitor.com hostmaster.markmonit |
Analysis
Hierarchy
www.nissanconnect.com.mx is a child of nissanconnect.com.mx.
IP Addresses
nissanconnect.com.mx resolves to one IP number: 54.172.71.199.
Other host names, for instance ec2-54-172-71-199.compute-1.amazonaws.com, nissanjamaica.com, nissan.com.ar, nissan.cw and nissan.com.py share IP numbers with nissanconnect.com.mx.
Name Servers
nissanconnect.com.mx is delegated to five name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com and ns5.markmonitor.com.
nissanconnect.com.mx at least partially shares name servers with other domains, including taylormadegolf.at, fegli04.com, powerthattravels.com, vistaptrint.com and arnoldparts.fr.
These name servers are often used with ns6.markmonitor.com and ns7.markmonitor.com.
Host names with two IP numbers:
ns1.markmonitor.com points to: 2620:10a:80a8::1 and 149.112.160.1.
ns2.markmonitor.com points to: 2001:67c:10b8::1 and 176.97.158.1.
ns3.markmonitor.com points to: 2620:10a:80a9::1 and 149.112.161.1.
ns4.markmonitor.com points to: 2001:67c:1bc::1 and 192.174.68.1.
ns5.markmonitor.com points to: 2620:10a:80a8::2 and 149.112.160.2.