yesreply.com - dns.ninja
yesreply.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=1783757237 | ||||||
Same first word
Similar names
DNS History
10 records (7 active, 3 former)
●NSns-cloud-e1.googledomains.com2026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
●NSns-cloud-e2.googledomains.com2026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
●NSns-cloud-e3.googledomains.com2026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
●NSns-cloud-e4.googledomains.com2026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
○NSns63.domaincontrol.com2015-06-16 → 2020-02-10 · 3 obs
● 2020-02-10 10:12:34
○ 2026-07-11 08:14:16
○NSns64.domaincontrol.com2015-06-16 → 2020-02-10 · 3 obs
● 2020-02-10 10:12:34
○ 2026-07-11 08:14:16
●MXmailstore1.secureserver.net2015-06-16 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
●MXsmtp.secureserver.net2015-06-16 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
○A184.168.221.432015-06-16 → 2020-02-10 · 3 obs
● 2020-02-10 10:12:34
○ 2026-07-11 08:14:16
●A34.102.136.1802026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 08:14:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, j.gtld-servers.net... | - |
| yesreply.com | ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.36.110
NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 483ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.102.136.180 |
| NS | 4 | ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com... |
| MX | 2 | mailstore1.secureserver.net (pri: 10), smtp.secureserver.net (pri: 0) |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)
Analysis
IP Addresses
yesreply.com resolves to just one IP address, 34.102.136.180.
Two other host names, along with jcurci.com, kramermedia.com and ncihomecare.com, also share IP numbers with yesreply.com.
Name Servers
The NS records for yesreply.com point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
yesreply.com has at least partial name server overlap with other domains, such as sprylog.com, mooreco.com, agiu.org and two others.
ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.
Mail Servers
yesreply.com is served by two mail servers, mailstore1.secureserver.net and smtp.secureserver.net.
Among the domains sharing a mail server setup with yesreply.com are stepable.org, universalwindowquote.com, richmondcapitalsecurities.com and two others.
yesreply.com shares mail servers with at least some other domains, such as apparound.com, uhrrjb.com and agenturkuno.de.
mailstore1.secureserver.net directs to 92.204.80.19 and smtp.secureserver.net directs to 92.204.80.20; each host name points to exactly one IP number.