bikepanda.com - robtex.com
bikepanda.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.squadhelp.com ⭐ | ||||||
| A | 52.201.79.206🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix | ||||||
| PTR | ec2-52-201-79-206.compute-1.amazonaws.com | ||||||
| NS | ns2.squadhelp.com | ||||||
| A | 52.23.148.124🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-23-148-124.compute-1.amazonaws.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.squadhelp.comhostmaster@bikepanda.com 2025-11-10 #1 | ||||||
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=1777082726 | ||||||
Same first word
bikepanda.com |
Similar names
DNS History
20 records (3 active, 17 former)
○NSjm1.dns.com2020-01-14 → 2020-01-14 · 3 obs
○ 2017-03-17 19:49:56
● 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
○NSjm2.dns.com2020-01-14 → 2020-01-14 · 3 obs
○ 2017-03-17 19:49:56
● 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
○NSns07.domaincontrol.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○NSns08.domaincontrol.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○NSns1.alidns.com2016-06-29 → 2017-03-17 · 5 obs
○ 2016-03-10 05:29:46
● 2016-06-29 07:45:12
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2016-06-29 07:45:12
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
●NSns1.squadhelp.com2026-04-25 → 2026-04-25 · 2 obs
○ 2020-01-14 02:00:06
● 2026-04-25 02:27:16
● 2026-04-25 02:27:16
○NSns2.alidns.com2016-06-29 → 2017-03-17 · 5 obs
○ 2016-03-10 05:29:46
● 2016-06-29 07:45:12
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2016-06-29 07:45:12
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
●NSns2.squadhelp.com2026-04-25 → 2026-04-25 · 2 obs
○ 2020-01-14 02:00:06
● 2026-04-25 02:27:16
● 2026-04-25 02:27:16
○MXalt1.aspmx.l.google.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○MXalt2.aspmx.l.google.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○MXaspmx.l.google.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○MXaspmx2.googlemail.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○MXaspmx3.googlemail.com2015-08-13 → 2016-03-10 · 4 obs
● 2015-08-13 01:17:54
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
○A103.235.101.02016-06-29 → 2016-06-29 · 4 obs
○ 2016-03-10 05:29:46
● 2016-06-29 07:45:12
○ 2017-03-17 19:49:56
○ 2026-04-25 02:27:16
● 2016-06-29 07:45:12
○ 2017-03-17 19:49:56
○ 2026-04-25 02:27:16
○A166.88.49.1102020-01-14 → 2020-01-14 · 3 obs
○ 2017-03-17 19:49:56
● 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
○A43.228.242.2542017-03-17 → 2017-03-17 · 4 obs
○ 2016-06-29 07:45:12
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
○A50.63.202.222015-08-13 → 2015-12-02 · 4 obs
● 2015-08-13 01:17:54
● 2015-12-02 01:19:02
○ 2016-03-10 05:29:46
○ 2026-04-25 02:27:16
● 2015-12-02 01:19:02
○ 2016-03-10 05:29:46
○ 2026-04-25 02:27:16
○A50.63.202.922016-03-10 → 2016-03-10 · 4 obs
○ 2015-12-02 01:19:02
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
● 2016-03-10 05:29:46
○ 2016-06-29 07:45:12
○ 2026-04-25 02:27:16
●A52.20.84.622026-04-25 → 2026-04-25 · 2 obs
○ 2020-01-14 02:00:06
● 2026-04-25 02:27:16
● 2026-04-25 02:27:16
○CNAMEparking.sharknames.com2016-06-29 → 2017-03-17 · 4 obs
● 2016-06-29 07:45:12
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
● 2017-03-17 19:49:56
○ 2020-01-14 02:00:06
○ 2026-04-25 02:27:16
🔍 DNS Trace
Analysis
IP Addresses
bikepanda.com resolves to one IP number: 52.20.84.62.
Other host names, for instance midgt.com, chocolatechipmunk.com, goldgsm.com, boxew.com and getedison.com share IP numbers with bikepanda.com.
Name Servers
bikepanda.com's delegation uses two name servers: ns1.squadhelp.com and ns2.squadhelp.com.
bikepanda.com uses the same name server setup as other domains, such as dwfs.com, lottojunky.com, payuro.com, wixny.com and pricerebel.com.
bikepanda.com shares name servers with other domains at least partially, for example eggsparty.com, koolta.com and jdvu.com.
These name servers are often used with ns1.dan.com and ns2.dan.com.
Host names with a single IP address: ns1.squadhelp.com points to 52.201.79.206; ns2.squadhelp.com points to 52.23.148.124.