rply.to - dns.ninja
rply.to
| DNSSEC | ⚠️ Not signed | ||||||
| A | 18.215.238.134🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix | ||||||
| PTR | ec2-18-215-238-134.compute-1.amazonaws.com | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@rply.to serial=0 | ||||||
to
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1781132718 | ||||||
Same first word
Similar names
DNS History
11 records (4 active, 7 former)
○NSdns1.registrar-servers.com2026-02-19 → 2026-02-19 · 4 obs
● 2026-02-19 22:47:12
○ 2026-03-30 19:44:48
○ 2026-06-10 23:08:20
○NSdns2.registrar-servers.com2026-02-19 → 2026-02-19 · 4 obs
● 2026-02-19 22:47:12
○ 2026-03-30 19:44:48
○ 2026-06-10 23:08:20
●NSns1.digitalocean.com2026-03-30 → 2026-06-10 · 3 obs
● 2026-03-30 19:44:48
● 2026-06-10 23:08:20
○NSns1.ns-serve.net2015-05-22 → 2017-03-25 · 4 obs
● 2017-03-25 18:49:44
○ 2026-02-19 22:47:12
○ 2026-06-10 23:08:20
●NSns2.digitalocean.com2026-03-30 → 2026-06-10 · 3 obs
● 2026-03-30 19:44:48
● 2026-06-10 23:08:20
○NSns2.ns-serve.net2015-05-22 → 2017-03-25 · 4 obs
● 2017-03-25 18:49:44
○ 2026-02-19 22:47:12
○ 2026-06-10 23:08:20
●NSns3.digitalocean.com2026-03-30 → 2026-06-10 · 3 obs
● 2026-03-30 19:44:48
● 2026-06-10 23:08:20
○MXmail.rply.to2015-05-22 → 2017-03-25 · 4 obs
● 2017-03-25 18:49:44
○ 2026-02-19 22:47:12
○ 2026-06-10 23:08:20
○A18.206.203.2162026-03-30 → 2026-04-09 · 5 obs
● 2026-03-30 19:44:48
● 2026-04-09 05:15:52
○ 2026-06-09 17:43:24
○ 2026-06-10 23:08:20
●A18.215.238.1342026-06-09 → 2026-06-10 · 3 obs
● 2026-06-09 17:43:24
● 2026-06-10 23:08:20
○A195.225.104.372015-05-22 → 2017-03-25 · 4 obs
● 2017-03-25 18:49:44
○ 2026-02-19 22:47:12
○ 2026-06-10 23:08:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| to | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | 8 records |
| rply.to | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.49.209
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for to (unsigned zone)
⏱️ Timing
Total: 419ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 18.215.238.134 |
| NS | 3 | ns1.digitalocean.com, ns2.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.rply.to |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)
Analysis
IP Addresses
rply.to has exactly one IP address — 18.215.238.134.
Name Servers
rply.to is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
rply.to partially shares its NS delegation with several other domains, including carlink.ru, 71.198.143.in-addr.arpa, newsqfnud.info and two others.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each resolve to two IP addresses: ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1.