pershingmuseum.com - dns.ninja
pershingmuseum.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=1782576580 | ||||||
Same first word
pershingmuseum.com |
DNS History
13 records (11 active, 2 former)
●NSns73.domaincontrol.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
●NSns74.domaincontrol.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
●MXalt1.aspmx.l.google.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
●MXalt2.aspmx.l.google.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
●MXaspmx.l.google.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
●MXaspmx2.googlemail.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
●MXaspmx3.googlemail.com2015-07-22 → 2026-06-27 · 2 obs
● 2026-06-27 16:12:20
○A173.201.92.1282015-07-22 → 2015-11-27 · 4 obs
● 2015-11-27 04:16:10
○ 2016-03-12 00:50:18
○ 2026-06-27 16:12:20
○A184.168.221.622016-03-12 → 2016-03-12 · 4 obs
● 2016-03-12 00:50:18
○ 2016-09-07 15:06:16
○ 2026-06-27 16:12:20
●A216.239.32.212016-09-07 → 2026-06-27 · 3 obs
● 2016-09-07 15:06:16
● 2026-06-27 16:12:20
●A216.239.34.212016-09-07 → 2026-06-27 · 3 obs
● 2016-09-07 15:06:16
● 2026-06-27 16:12:20
●A216.239.36.212016-09-07 → 2026-06-27 · 3 obs
● 2016-09-07 15:06:16
● 2026-06-27 16:12:20
●A216.239.38.212016-09-07 → 2026-06-27 · 3 obs
● 2016-09-07 15:06:16
● 2026-06-27 16:12:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net... | - |
| pershingmuseum.com | ns73.domaincontrol.com, ns74.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.74.47
NS records: ns73.domaincontrol.com, ns74.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pershingmuseum.com (unsigned zone)
⏱️ Timing
Total: 162ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 216.239.34.21, 216.239.36.21... |
| NS | 2 | ns73.domaincontrol.com, ns74.domaincontrol.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 30), aspmx3.googlemail.com (pri: 50)... |
| SOA | 1 | ns73.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns73.domaincontrol.com, ns73.domaincontrol.com, ns74.domaincontrol.com...)
Analysis
IP Addresses
pershingmuseum.com directs to four IP numbers, which are 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.
ghostware.cz, excayo.com, gtm.prijsvrij.nl plus two other host names have IP numbers in common with pershingmuseum.com.
Name Servers
pershingmuseum.com has two authoritative name servers — ns73.domaincontrol.com and ns74.domaincontrol.com.
The name server configuration of pershingmuseum.com is shared with other domains, for instance haberozetle.com, albanyenv.com, d-heartcare.com and two others.
The name servers for pershingmuseum.com overlap at least partially with those of other domains — for example tamsui.org.
Both ns73.domaincontrol.com and ns74.domaincontrol.com have two IP addresses each. ns73.domaincontrol.com resolves to 97.74.106.47 and 2603:5:21a4::2f; ns74.domaincontrol.com resolves to 173.201.74.47 and 2603:5:22a4::2f.
Mail Servers
Five mail servers handle pershingmuseum.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by pershingmuseum.com are shared with other domains: gbbuilders.in, ns500731.ns500754.ns500731.ns500742.ns500742.ns500742.ns500742.ns500704.ns500671.ns500678.ns500671.ns500678.ns500705.ns500291.ns500671.ns500671.ns500666.tenderladiesbz.com, ns500724.ns500724.ns500724.ns500724.ns500737.ns500599.ns500737.ns500724.ns500724.ns500599.ns500599.ns500697.www.yummyflingsfinder.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 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to 192.178.155.27 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1b IP addresses.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 108.177.123.26 IP addresses.