mapasydatos.com - dns.ninja
mapasydatos.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=1782652520 | ||||||
Subdomains
imap.mapasydatos.com |
Same first word
mapasydatos.com |
mapasydatos.com.ar |
DNS History
13 records (8 active, 5 former)
○NSdns02.mapasydatos.com2007-10-24 → 2007-10-24 · 3 obs
○ 2015-07-12 14:16:58
○ 2026-06-28 13:28:10
○NSdns3.mapaslatinos.com2007-10-24 → 2007-10-24 · 3 obs
○ 2015-07-12 14:16:58
○ 2026-06-28 13:28:10
●NSns67.domaincontrol.com2015-07-12 → 2026-06-28 · 3 obs
● 2015-07-12 14:16:58
● 2026-06-28 13:28:10
●NSns68.domaincontrol.com2015-07-12 → 2026-06-28 · 3 obs
● 2015-07-12 14:16:58
● 2026-06-28 13:28:10
●MXalt1.aspmx.l.google.com2007-10-24 → 2026-06-28 · 2 obs
● 2026-06-28 13:28:10
●MXalt2.aspmx.l.google.com2007-10-24 → 2026-06-28 · 2 obs
● 2026-06-28 13:28:10
●MXaspmx.l.google.com2007-10-24 → 2026-06-28 · 2 obs
● 2026-06-28 13:28:10
●MXaspmx2.googlemail.com2007-10-24 → 2026-06-28 · 2 obs
● 2026-06-28 13:28:10
●MXaspmx3.googlemail.com2007-10-24 → 2026-06-28 · 2 obs
● 2026-06-28 13:28:10
○MXaspmx4.googlemail.com2007-10-24 → 2007-10-24 · 3 obs
○ 2015-07-12 14:16:58
○ 2026-06-28 13:28:10
○MXaspmx5.googlemail.com2007-10-24 → 2007-10-24 · 3 obs
○ 2015-07-12 14:16:58
○ 2026-06-28 13:28:10
●A192.30.252.1532026-02-27 → 2026-06-28 · 3 obs
● 2026-02-27 02:28:18
● 2026-06-28 13:28:10
○A23.235.46.1332015-07-12 → 2017-02-13 · 5 obs
● 2015-07-12 14:16:58
● 2017-02-13 17:16:52
○ 2026-02-27 02:28:18
○ 2026-06-28 13:28:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| mapasydatos.com | ns67.domaincontrol.com, ns68.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.71.44
NS records: ns67.domaincontrol.com, ns68.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mapasydatos.com (unsigned zone)
⏱️ Timing
Total: 338ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.30.252.153 |
| NS | 2 | ns67.domaincontrol.com, ns68.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| SOA | 1 | ns67.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns67.domaincontrol.com, ns67.domaincontrol.com, ns68.domaincontrol.com...)
Analysis
Hierarchy
mapasydatos.com serves as the parent of imap.mapasydatos.com.
IP Addresses
mapasydatos.com resolves to just one IP address, 192.30.252.153.
Two other host names, along with westrup.se, gargantor.stevelorek.com and pentrix.com, also share IP numbers with mapasydatos.com.
Name Servers
mapasydatos.com uses two name servers for its delegation: ns67.domaincontrol.com and ns68.domaincontrol.com.
mapasydatos.com shares its NS records with other domains, for example finerio.mx, hannahschiro.com, integrativemedicinecenters.com and two others.
The two host names ns67.domaincontrol.com and ns68.domaincontrol.com each have a pair of IP addresses: ns67.domaincontrol.com has 97.74.103.44 and 2603:5:2174::2c, and ns68.domaincontrol.com has 173.201.71.44 and 2603:5:2274::2c.
Mail Servers
mapasydatos.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between mapasydatos.com and other domains, including ns500765.ns500765.ns500734.ns500699.ns500734.ns500699.ns500693.ns500699.ns500728.ns500588.ns500588.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com, ns500758.ns500758.ns500758.ns500698.ns500698.ns500698.ns500698.ns500736.ns500735.ns500698.ns500576.ns500698.ns500686.ns500652.ns500619.trackreceptor.com, ns500758.ns500698.ns500758.ns500759.ns500698.ns500698.ns500698.ns500735.ns500736.ns500735.ns500576.ns500708.ns500708.ns500698.ns500619.ns500652.ns500576.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 192.178.155.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.