response.to - robtex.com
Search for stuff
response.to
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=1770645919 | ||||||
Same first word
Similar names
🔍 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 |
| response.to | a.dns.park.io, b.dns.park.io | - |
✅ Authoritative Response
Server: 23.23.95.213
NS records: a.dns.park.io, b.dns.park.io
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for to (unsigned zone)
⏱️ Timing
Total: 340ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | park.io |
| SOA | 1 | a.dns.park.io 2014070706 |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)
AI analysis
response.to resolves to two IPs: 34.228.48.12 and 44.208.172.211.
other host names for instance central.to, park.io, ec2-34-228-48-12.compute-1.amazonaws.com, ec2-44-208-172-211.compute-1.amazonaws.com and app.park.io share IP numbers with response.to.
response.to is delegated to four name servers: ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk.
response.to at least partially shares name servers with other domains, for instance hoshiuta.net, nl.bda.innogy.com, mimimail16.com, saleyard.co and botbird.net.
these name servers are commonly used with ns-354.awsdns-44.com, ns-703.awsdns-23.net, ns-1852.awsdns-39.co.uk, ns-257.awsdns-32.com, ns-1472.awsdns-56.org and ns-691.awsdns-22.net.
Host names with two IP numbers:
Host name ns-441.awsdns-55.com points to: 2600:9000:5301:b900::1 and 205.251.193.185.
Host name ns-672.awsdns-20.net points to: 2600:9000:5302:a000::1 and 205.251.194.160.
Host name ns-1348.awsdns-40.org points to: 2600:9000:5305:4400::1 and 205.251.197.68.
Host name ns-1624.awsdns-11.co.uk points to: 2600:9000:5306:5800::1 and 205.251.198.88.
response.to is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
response.to shares mail servers with other domains at least partially, including ns500759.ns500759.ns500736.ns500736.ns500735.ns500735.ns500576.ns500708.ns500619.ns500576.ns500619.ns500619.trackreceptor.com, ns500698.ns500758.ns500759.ns500758.ns500698.ns500736.ns500698.ns500735.ns500736.ns500698.ns500708.ns500708.ns500576.ns500686.ns500619.trackreceptor.com, btlmedical.com.hk, dansdemiester.com and homeintheharbor.com.
these mail servers are often used with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Hosts with two IP numbers:
aspmx2.googlemail.com points to 2800:3f0:4003:c0f::1b and 108.177.123.26.
aspmx3.googlemail.com points to 2a00:1450:400b:c02::1a and 172.253.116.27.
aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 66.102.1.27.
alt1.aspmx.l.google.com points to 2a00:1450:4025:402::1a and 142.250.102.27.
alt2.aspmx.l.google.com points to 2a00:1450:4013:c1e::1b and 192.178.213.27.