bathcrestofdenver.com - robtex.com
bathcrestofdenver.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 104.238.68.196🇺🇸 AS398787104.238.68.0/22 GoDaddy.com, LLC | ||||||
| PTR | 196.68.238.104.host.secureserver.net | ||||||
| NS | dns103.register.com ⭐ | ||||||
| A | 162.159.24.117Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ip-162-159-24-117.defastlink.net | ||||||
| NS | dns104.register.com | ||||||
| A | 162.159.25.158Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ip-162-159-25-158.defastlink.net | ||||||
| TXT | 7b5ii8bu4kvp8ca4vtidqifrr2 | ||||||
| TXT | google-site-verification=xBcDp98H2SgzAZhoH9UwEwkO-QxuiGfbb9KTzQpR0EM | ||||||
| SOA | DNS103.REGISTER.comroot@REGISTER.com serial=121080618 | ||||||
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=1771291435 | ||||||
Same first word
bathcrestofdenver.com |
DNS History
27 records (3 active, 24 former)
○NSclay.ns.cloudflare.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-28 10:14:44
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
○NSdns01.gpn.register.com2016-08-12 → 2017-03-28 · 5 obs
○ 2016-03-27 20:51:16
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
○NSdns02.gpn.register.com2016-08-12 → 2017-03-28 · 5 obs
○ 2016-03-27 20:51:16
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
○NSdns03.gpn.register.com2016-08-12 → 2017-03-28 · 5 obs
○ 2016-03-27 20:51:16
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
○NSdns04.gpn.register.com2016-08-12 → 2017-03-28 · 5 obs
○ 2016-03-27 20:51:16
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
○NSdns05.gpn.register.com2016-08-12 → 2017-03-28 · 5 obs
○ 2016-03-27 20:51:16
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
● 2016-08-12 02:39:10
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
○NSdns082.d.register.com2016-03-27 → 2016-03-27 · 4 obs
○ 2015-12-31 10:22:24
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
○NSdns102.b.register.com2016-03-27 → 2016-03-27 · 4 obs
○ 2015-12-31 10:22:24
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
●NSdns103.register.com2026-02-23 → 2026-03-23 · 3 obs
○ 2020-02-02 02:24:10
● 2026-02-23 12:31:40
● 2026-03-23 00:47:04
● 2026-02-23 12:31:40
● 2026-03-23 00:47:04
●NSdns104.register.com2026-02-23 → 2026-03-23 · 3 obs
○ 2020-02-02 02:24:10
● 2026-02-23 12:31:40
● 2026-03-23 00:47:04
● 2026-02-23 12:31:40
● 2026-03-23 00:47:04
○NSdns204.a.register.com2016-03-27 → 2016-03-27 · 4 obs
○ 2015-12-31 10:22:24
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
○NSdns241.c.register.com2016-03-27 → 2016-03-27 · 4 obs
○ 2015-12-31 10:22:24
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
○NSns1.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○NSns2.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○NSns3.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○NSns4.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○NSulla.ns.cloudflare.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-28 10:14:44
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
○MXmx1c25.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○MXmx2c25.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○MXmx3c25.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○MXmx4c25.carrierzone.com2015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
○A100.24.208.972020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-28 10:14:44
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
○A104.209.136.2332016-03-27 → 2016-03-27 · 4 obs
○ 2015-12-31 10:22:24
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
● 2016-03-27 20:51:16
○ 2016-08-12 02:39:10
○ 2026-03-23 00:47:04
●A104.238.68.1962026-02-23 → 2026-03-23 · 3 obs
○ 2020-02-02 02:24:10
● 2026-02-23 12:31:40
● 2026-03-23 00:47:04
● 2026-02-23 12:31:40
● 2026-03-23 00:47:04
○A191.239.58.432016-03-27 → 2017-03-28 · 5 obs
○ 2015-12-31 10:22:24
● 2016-03-27 20:51:16
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
● 2016-03-27 20:51:16
● 2017-03-28 10:14:44
○ 2020-02-02 02:24:10
○ 2026-03-23 00:47:04
○A35.172.94.12020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-28 10:14:44
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
● 2020-02-02 02:24:10
○ 2026-02-23 12:31:40
○ 2026-03-23 00:47:04
○A64.29.145.92015-05-25 → 2015-12-31 · 4 obs
● 2015-05-25 15:43:26
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
● 2015-12-31 10:22:24
○ 2016-03-27 20:51:16
○ 2026-03-23 00:47:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net... | - |
| bathcrestofdenver.com | dns103.register.com, dns104.register.com | 2 records |
✅ Authoritative Response
Server:162.159.24.117
NS records: dns103.register.com, dns104.register.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bathcrestofdenver.com (unsigned zone)
⏱️ Timing
Total: 194ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 104.238.68.196 |
| NS | 2 | dns103.register.com, dns104.register.com |
| TXT | 2 | 7b5ii8bu4kvp8ca4vtidqifrr2, google-site-verification=xBcDp98H2SgzAZh |
| SOA | 1 | DNS103.REGISTER.com root.REGISTER.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns103.register.com, dns104.register.com)
Analysis
IP Addresses
bathcrestofdenver.com points to a single IP: 104.238.68.196.
Other host names, for instance thefutureofelections.com, rotaryseniorliving.com, cathycunningham.us, monarchevent.com and a1aatlantic.com share IP numbers with bathcrestofdenver.com.
Name Servers
Two name servers dns103.register.com and dns104.register.com handle delegation for bathcrestofdenver.com.
bathcrestofdenver.com uses the same name server setup as other domains, for example montanadakotabeef.com, greenlawnholdings.com, dennisfoley.com, ncrwebeoc.com and vanicci.com.
bathcrestofdenver.com shares name servers with other domains at least partially, for instance oneoceanfleet.com, pots101.com, robotaco.com and maliburvpark.com.
These name servers are often used with the name servers dns101.register.com and dns102.register.com.
Host names with one IP number: The host name dns103.register.com points to 162.159.24.117 and the host name dns104.register.com points to 162.159.25.158.