mrespond.com - dns.ninja
mrespond.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=1786570839 | ||||||
Same first word
Similar names
sonderpm.com |
modernps.com |
opensdrm.com |
spmodern.com |
mdposner.com |
mendrops.com |
personmd.com |
modernsp.com |
psmodern.com |
dronemsp.com |
mendpros.com |
(0x706f726e)meds.com |
pedrosmn.com |
opensdrm.net |
DNS History
11 records (8 active, 3 former)
○NSns.mrespond.com2015-05-24 → 2016-11-26 · 4 obs
● 2016-11-26 04:31:04
○ 2017-05-22 16:46:12
○ 2026-08-12 22:05:06
●NSns1.dnsgroup.com2017-05-22 → 2026-08-12 · 3 obs
● 2017-05-22 16:46:12
● 2026-08-12 22:05:06
●NSns2.dnsgroup.com2017-05-22 → 2026-08-12 · 3 obs
● 2017-05-22 16:46:12
● 2026-08-12 22:05:06
●MXalt1.aspmx.l.google.com2026-03-09 → 2026-08-12 · 3 obs
● 2026-03-09 04:57:10
● 2026-08-12 22:05:06
●MXalt2.aspmx.l.google.com2026-03-09 → 2026-08-12 · 3 obs
● 2026-03-09 04:57:10
● 2026-08-12 22:05:06
●MXaspmx.l.google.com2026-03-09 → 2026-08-12 · 3 obs
● 2026-03-09 04:57:10
● 2026-08-12 22:05:06
●MXaspmx2.googlemail.com2026-03-09 → 2026-08-12 · 3 obs
● 2026-03-09 04:57:10
● 2026-08-12 22:05:06
●MXaspmx3.googlemail.com2026-03-09 → 2026-08-12 · 3 obs
● 2026-03-09 04:57:10
● 2026-08-12 22:05:06
○MXmail.mrespond.com2015-05-24 → 2017-05-22 · 4 obs
● 2017-05-22 16:46:12
○ 2026-03-09 04:57:10
○ 2026-08-12 22:05:06
●A185.230.63.1712026-03-09 → 2026-08-12 · 3 obs
● 2026-03-09 04:57:10
● 2026-08-12 22:05:06
○A199.167.148.2002015-05-24 → 2017-05-22 · 4 obs
● 2017-05-22 16:46:12
○ 2026-03-09 04:57:10
○ 2026-08-12 22:05:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net... | - |
| mrespond.com | ns1.dnsgroup.com, ns2.dnsgroup.com | 2 records |
✅ Authoritative Response
Server:199.167.148.202
NS records: ns1.dnsgroup.com, ns2.dnsgroup.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mrespond.com (unsigned zone)
⏱️ Timing
Total: 239ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.230.63.171 |
| NS | 2 | ns2.dnsgroup.com, ns1.dnsgroup.com |
| MX | 5 | ASPMX2.GOOGLEMAIL.COM (pri: 15), ASPMX.L.GOOGLE.COM (pri: 5)... |
| TXT | 2 | v=spf1 include:_spf.google.com -all, google-site-verification=Td63ejHQU8uUIU6 |
| SOA | 1 | ns1.dnsgroup.com wsylvest.gmail.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.dnsgroup.com, ns2.dnsgroup.com)
Analysis
IP Addresses
mrespond.com directs to one IP number, which is 185.230.63.171.
Among the host names that share IP numbers with mrespond.com are ogspanky.com, astridbreuer.de, mtcra.com and two others.
Name Servers
Two name servers handle the delegation for mrespond.com: ns1.dnsgroup.com and ns2.dnsgroup.com.
mrespond.com has the same name server delegation as a number of other domains, such as icestorm.org, deathstar.net, thegoldmanfamily.us and two more.
mrespond.com is at least partially co-delegated on name servers with other domains, such as mxrs.net.
These name servers frequently co-occur with the name servers ns1.mxrs.net and ns2.mxrs.net.
ns1.dnsgroup.com → 91.191.213.42 and ns2.dnsgroup.com → 199.167.148.199: one IP number per host name.
Mail Servers
Five mail servers handle mrespond.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
mrespond.com shares at least some of its mail servers with other domains — for example ns500742.ns500754.ns500754.ns500671.ns500671.ns500731.ns500704.ns500742.ns500742.ns500671.ns500671.ns500678.ns500649.ns500649.ns500291.ns500153.tenderladiesbz.com, ns500699.ns500765.ns500693.ns500693.ns500699.ns500693.ns500699.ns500693.ns500588.ns500683.ns500612.ns500588.ns500588.dtrkdll.com, ns500742.ns500731.ns500742.ns500754.ns500688.ns500705.ns500688.ns500291.ns500291.ns500666.ns500291.ns500291.ns500131.lustychickser.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: 142.250.102.26 and 2a00:1450:4025:402::1a.
aspmx3.googlemail.com resolves to two addresses: 192.178.213.27 and 2a00:1450:4013:c1e::1b.
aspmx.l.google.com resolves to two addresses: 142.251.167.27 and 2607:f8b0:4004:c0b::1a.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.