mappingparty.com.br - robtex.com
mappingparty.com.br
com.br
| DNSSEC | ⚠️ Not signed | ||||||
| NS | a.dns.br ⭐ ⚠️ Not in parent delegation | ||||||
| NS | b.dns.br ⚠️ Not in parent delegation | ||||||
| NS | c.dns.br ⚠️ Not in parent delegation | ||||||
| NS | d.dns.br ⚠️ Not in parent delegation | ||||||
| NS | e.dns.br ⚠️ Not in parent delegation | ||||||
| NS | f.dns.br ⚠️ Not in parent delegation | ||||||
| SOA | a.dns.brhostmaster@registro.br serial=2026207546 | ||||||
rank #3676 in the tld
WOT: SAFE (69/100)
Same first word
mappingparty.com.br |
DNS History
13 records (8 active, 5 former)
○NSe.sec.dns.br2017-06-22 → 2017-06-22 · 4 obs
● 2017-06-22 13:06:24
○ 2026-07-16 22:47:30
○ 2026-07-26 23:04:42
●NSelijah.ns.cloudflare.com2026-07-16 → 2026-07-26 · 3 obs
● 2026-07-16 22:47:30
● 2026-07-26 23:04:42
○NSf.sec.dns.br2017-06-22 → 2017-06-22 · 4 obs
● 2017-06-22 13:06:24
○ 2026-07-16 22:47:30
○ 2026-07-26 23:04:42
●NSnancy.ns.cloudflare.com2026-07-16 → 2026-07-26 · 3 obs
● 2026-07-16 22:47:30
● 2026-07-26 23:04:42
○NSns1.mappingparty.com.br2015-08-02 → 2016-04-18 · 4 obs
● 2016-04-18 15:20:40
○ 2017-06-22 13:06:24
○ 2026-07-26 23:04:42
○NSns2.mappingparty.com.br2015-08-02 → 2016-04-18 · 4 obs
● 2016-04-18 15:20:40
○ 2017-06-22 13:06:24
○ 2026-07-26 23:04:42
●MXalt1.aspmx.l.google.com2015-08-02 → 2026-07-26 · 2 obs
● 2026-07-26 23:04:42
●MXalt2.aspmx.l.google.com2015-08-02 → 2026-07-26 · 2 obs
● 2026-07-26 23:04:42
●MXaspmx.l.google.com2015-08-02 → 2026-07-26 · 2 obs
● 2026-07-26 23:04:42
●MXaspmx2.googlemail.com2015-08-02 → 2026-07-26 · 2 obs
● 2026-07-26 23:04:42
●MXaspmx3.googlemail.com2015-08-02 → 2026-07-26 · 2 obs
● 2026-07-26 23:04:42
○A186.202.119.1822015-08-02 → 2016-04-18 · 4 obs
● 2016-04-18 15:20:40
○ 2017-06-22 13:06:24
○ 2026-07-26 23:04:42
●A23.236.62.1472017-06-22 → 2026-07-26 · 3 obs
● 2017-06-22 13:06:24
● 2026-07-26 23:04:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| br | e.dns.br, d.dns.br, a.dns.br, c.dns.br... | - |
| mappingparty.com.br | elijah.ns.cloudflare.com, nancy.ns.cloudflare.com | - |
✅ Authoritative Response
Server:108.162.194.84
NS records: elijah.ns.cloudflare.com, nancy.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mappingparty.com.br (unsigned zone)
⏱️ Timing
Total: 633ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.236.62.147 |
| NS | 2 | elijah.ns.cloudflare.com, nancy.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 0), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | elijah.ns.cloudflare.com dns.cloudflare. |
Analysis
IP Addresses
mappingparty.com.br has exactly one IP address — 23.236.62.147.
ing-berchtold.ch, accelium.com, laclivet.com.mx plus two other host names have IP numbers in common with mappingparty.com.br.
Name Servers
Two name servers handle the delegation for mappingparty.com.br: elijah.ns.cloudflare.com and nancy.ns.cloudflare.com.
The name server configuration of mappingparty.com.br is shared with other domains, for instance serrasulshopping.com.br, shoppingcenter3.com.br, shoppingjaragua.com.br and two others.
There is at least partial name server overlap between mappingparty.com.br and other domains — fartuszek.com.pl, getdailyinsights.com, motorgearx.com and two more among them.
These name servers frequently co-occur with the name servers rudy.ns.cloudflare.com and coco.ns.cloudflare.com.
Hosts with 6 IP addresses each:
elijah.ns.cloudflare.com resolves to 108.162.195.253, 162.159.44.253 and 172.64.35.253 among others, with 3 other IP addresses in total.
nancy.ns.cloudflare.com resolves to 108.162.194.84, 162.159.38.84 and 172.64.34.84 among others, with 3 other IP addresses in total.
Mail Servers
Five mail servers handle mappingparty.com.br: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by mappingparty.com.br are shared with other domains: ns500794.ns500841.ns500794.ns500821.ns500794.ns500794.ns500795.ns500795.ns500790.ns500795.lustypartnersfinder.com, docstation.co, amdconstruct.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to two addresses: 64.233.180.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c0f::1a IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1a IP addresses.