bouncing.to - robtex.com
bouncing.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=1771274419 | ||||||
Same first word
Similar names
DNS History
14 records (11 active, 3 former)
βNSajay.ns.cloudflare.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βNSkiki.ns.cloudflare.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βMXalt1.aspmx.l.google.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βMXalt2.aspmx.l.google.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βMXalt3.aspmx.l.google.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βMXalt4.aspmx.l.google.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βMXaspmx.l.google.com2026-02-24 β 2026-02-24 Β· 2 obs
β 2026-02-24 23:38:52
βA107.22.57.982026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
βA23.22.130.1732026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
βA3.209.172.722026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
βA34.241.115.672026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
βA54.228.42.1992026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
βA54.243.238.662026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
βA54.78.134.1112026-02-24 β 2026-02-24 Β· 3 obs
β 2026-02-24 23:38:48
β 2026-02-24 23:38:52
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| to | ns10.trs-dns.org, ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.info | 8 records |
| bouncing.to | ajay.ns.cloudflare.com, kiki.ns.cloudflare.com | - |
β Authoritative Response
Server: 173.245.59.56
NS records: ajay.ns.cloudflare.com, kiki.ns.cloudflare.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for to (unsigned zone)
β±οΈ Timing
Total: 649ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 54.83.6.65, 54.146.248.82... |
| NS | 2 | ajay.ns.cloudflare.com, kiki.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ajay.ns.cloudflare.com dns.cloudflare.co |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns10.trs-dns.org, ns10.trs-dns.org, ns01.trs-dns.com...)
AI analysis
bouncing.to points to four IP numbers: 3.209.172.72, 23.22.130.173, 54.243.238.66 and 107.22.57.98.
Other host names, for instance msecure-docker-parse.herokuapp.com, bltavares.viewdocs.io, adamplusamy.herokuapp.com, tailgate32.herokuapp.com and dev-lunch.herokuapp.com share IP numbers with bouncing.to.
Delegation for bouncing.to rests with two name servers, ajay.ns.cloudflare.com and kiki.ns.cloudflare.com.
bouncing.to shares the same name server setup as other domains, including berios.ca, documentportal.info, xn--80aaikjb9aks6bt.xn--p1ai, armoni.in.ua and tie.pub.
bouncing.to at least partially shares name servers with other domains, for instance siteconsent.net, sdsyjx.cn, cihanur.com.tr, 288q.com and antennacreative.com.
These name servers are commonly used with olivia.ns.cloudflare.com and peter.ns.cloudflare.com.
Host names with six IP numbers: ajay.ns.cloudflare.com points to: 2606:4700:58::adf5:3b38, 2803:f800:50::6ca2:c138, 2a06:98c1:50::ac40:2138, 108.162.193.56, 172.64.33.56 and 173.245.59.56. kiki.ns.cloudflare.com points to: 2606:4700:50::adf5:3ab4, 2803:f800:50::6ca2:c0b4, 2a06:98c1:50::ac40:20b4, 108.162.192.180, 172.64.32.180 and 173.245.58.180.
bouncing.to is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
bouncing.to shares mail servers with other domains at least in part, for instance benchung.net, redoot.net, ns500698.ns500759.ns500735.ns500736.ns500735.ns500736.ns500698.ns500735.ns500708.ns500708.ns500576.ns500708.ns500698.ns500619.ns500652.ns500576.trackreceptor.com, ns500699.ns500734.ns500734.ns500734.ns500734.ns500699.ns500693.ns500699.ns500699.ns500588.ns500588.ns500699.ns500588.ns500588.ns500632.ns500110.dtrkdll.com and ns500698.ns500759.ns500758.ns500758.ns500759.ns500758.ns500698.ns500735.ns500708.ns500576.ns500698.ns500708.ns500698.ns500698.ns500619.ns500619.ns500619.trackreceptor.com.
these mail servers are often used with aspmx3.googlemail.com and aspmx2.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26.
alt3.aspmx.l.google.com points to 2607:f8b0:4024:c0d::1b and 192.178.152.26.
alt4.aspmx.l.google.com points to 2607:f8b0:4023:403::1a and 142.250.96.27.