ridecommand.com - dns.ninja
ridecommand.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 217.19.248.132🇬🇧 SAFENAMES-AS217.19.248.0/24 Safenames Datacentre | ||||||
| PTR | redirect.idp365.net | ||||||
| NS | dns1.idp365.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1b83🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.131Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | dns1.idp365.net | ||||||
| NS | dns2.idp365.net | ||||||
| A | 2400:cb00:2049:1::a29f:3003🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.48.3Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | dns2.idp365.net | ||||||
| NS | dns3.idp365.net | ||||||
| A | 2400:cb00:2049:1::a29f:31fe🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.49.254Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | dns3.idp365.net | ||||||
| TXT | have-i-been-pwned-verification=dweb_0knirjdod420nfgzxaargzya | ||||||
| TXT | v=spf1 include:_u.ridecommand.com._spf.smart.ondmarc.com ~all | ||||||
| SOA | dns1.idp365.nethostmaster@idp365.net 2024-08-29 #3 | ||||||
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=1782851596 | ||||||
Same first word
ridecommand.com |
Similar names
DNS History
18 records (4 active, 14 former)
●NSdns1.idp365.net2026-05-06 → 2026-06-30 · 3 obs
● 2026-05-06 12:23:56
● 2026-06-30 20:57:46
○NSdns1.registrar-servers.com2016-07-23 → 2017-03-24 · 5 obs
● 2016-07-23 17:41:44
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
●NSdns2.idp365.net2026-05-06 → 2026-06-30 · 3 obs
● 2026-05-06 12:23:56
● 2026-06-30 20:57:46
○NSdns2.registrar-servers.com2016-07-23 → 2017-03-24 · 5 obs
● 2016-07-23 17:41:44
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
●NSdns3.idp365.net2026-05-06 → 2026-06-30 · 3 obs
● 2026-05-06 12:23:56
● 2026-06-30 20:57:46
○NSns1.bluehost.com2015-08-18 → 2016-04-01 · 4 obs
● 2016-04-01 08:01:06
○ 2016-07-23 17:41:44
○ 2026-06-30 20:57:46
○NSns2.bluehost.com2015-08-18 → 2016-04-01 · 4 obs
● 2016-04-01 08:01:06
○ 2016-07-23 17:41:44
○ 2026-06-30 20:57:46
○NSns43.domaincontrol.com2020-01-16 → 2020-01-16 · 4 obs
● 2020-01-16 07:13:48
○ 2026-05-06 12:23:56
○ 2026-06-30 20:57:46
○NSns44.domaincontrol.com2020-01-16 → 2020-01-16 · 4 obs
● 2020-01-16 07:13:48
○ 2026-05-06 12:23:56
○ 2026-06-30 20:57:46
○MXalt1.aspmx.l.google.com2015-08-18 → 2017-03-24 · 4 obs
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○MXalt2.aspmx.l.google.com2015-08-18 → 2017-03-24 · 4 obs
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○MXaspmx.l.google.com2015-08-18 → 2017-03-24 · 4 obs
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○MXaspmx2.googlemail.com2015-08-18 → 2017-03-24 · 4 obs
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○MXaspmx3.googlemail.com2015-08-18 → 2017-03-24 · 4 obs
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○A162.255.119.2492016-07-23 → 2017-03-24 · 5 obs
● 2016-07-23 17:41:44
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○A168.62.177.82015-08-18 → 2017-03-24 · 4 obs
● 2017-03-24 09:55:46
○ 2020-01-16 07:13:48
○ 2026-06-30 20:57:46
○A198.71.233.512020-01-16 → 2020-01-16 · 4 obs
● 2020-01-16 07:13:48
○ 2026-05-06 12:23:56
○ 2026-06-30 20:57:46
●A217.19.248.1322026-05-06 → 2026-06-30 · 3 obs
● 2026-05-06 12:23:56
● 2026-06-30 20:57:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ridecommand.com | dns1.idp365.net, dns2.idp365.net, dns3.idp365.net | - |
✅ Authoritative Response
Server:162.159.49.254
NS records: dns1.idp365.net, dns2.idp365.net, dns3.idp365.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ridecommand.com (unsigned zone)
⏱️ Timing
Total: 364ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 217.19.248.132 |
| NS | 3 | dns3.idp365.net, dns2.idp365.net... |
| TXT | 2 | have-i-been-pwned-verification=dweb_0kni, v=spf1 include:_u.ridecommand.com._spf.s |
| SOA | 1 | dns1.idp365.net hostmaster.idp365.net |
Analysis
IP Addresses
ridecommand.com has exactly one IP address — 217.19.248.132.
turktraktorpazari.com, xn--qma216l.com, udemy-coupons.com plus two other host names have IP numbers in common with ridecommand.com.
Name Servers
ridecommand.com is delegated to three name servers: dns1.idp365.net, dns2.idp365.net and dns3.idp365.net.
At least some of ridecommand.com's name servers are shared with other domains, for example instincts.org, dernoncourt.com, bertsbesbaby.com and two more.
dns1.idp365.net, dns2.idp365.net and dns3.idp365.net each resolve to two IP addresses: dns1.idp365.net resolves to 162.159.27.131 and 2400:cb00:2049:1::a29f:1b83; dns2.idp365.net resolves to 162.159.48.3 and 2400:cb00:2049:1::a29f:3003; dns3.idp365.net resolves to 162.159.49.254 and 2400:cb00:2049:1::a29f:31fe.