nloop.com.mx - robtex.com
nloop.com.mx
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=1791103658 | ||||||
Same first word
nloop.co.jp |
nloop.com.mx |
nloop.cc |
nloop.com |
nloop.de |
nloop.net |
nloop.co |
nloop.io |
nloop.ai |
nloop.ru |
nloop.store |
nloop.cloud |
nloop.com.br |
nloop.click |
nloop.jp |
Similar names
Previous names
Next names
DNS History
9 records (9 active, 0 former)
●NSdns1.registrar-servers.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●NSdns2.registrar-servers.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●MXalt1.aspmx.l.google.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●MXalt2.aspmx.l.google.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●MXaspmx.l.google.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●MXaspmx2.googlemail.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●MXaspmx3.googlemail.com2026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●A63.250.43.1282026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
●A63.250.43.1292026-06-15 → 2026-10-04 · 2 obs
● 2026-10-04 09:43:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | 12 records |
| nloop.com.mx | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for nloop.com.mx (unsigned zone)
⏱️ Timing
Total: 611ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 63.250.43.128, 63.250.43.129 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:spf.easywp.com ~all, google-site-verification=DQK-jN0CoPdwnK9 |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx...)
Analysis
IP Addresses
nloop.com.mx resolves to the IP addresses 63.250.43.128 and 63.250.43.129
Among the host names that share IP numbers with nloop.com.mx are notre-expertise-a-votre-service-be0099.ingress-earth.ewp.live, shortest-ca-bam-bcded0.ingress-earth.ewp.live, karnataka-f79d83.ingress-earth.ewp.live and two others.
Name Servers
Two name servers handle the delegation for nloop.com.mx: dns1.registrar-servers.com and dns2.registrar-servers.com.
nloop.com.mx has the same name server delegation as a number of other domains, such as allisonumc.org, paiw1.homes, touchlinetaffytrot.website and two more.
There is an overlap in name servers between nloop.com.mx and other domains, for example techizr.com, markgunderson.org and codexenon.com
These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.registrar-servers.com and dns2.registrar-servers.com both carry two IP addresses. The A records for dns1.registrar-servers.com are 156.154.132.200 and 2610:a1:1024::200; the A records for dns2.registrar-servers.com are 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
nloop.com.mx is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
nloop.com.mx shares at least some of its mail servers with other domains — for example sidecar-consultancy.com, kanouse.net, cehbuilds.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to two addresses: 142.251.179.27 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c14::1a IP addresses.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 192.178.234.26 IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1b IP addresses.