coolremote.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 63 days left14 years old
35
coolremote.me was registered on 30 Sep 2012 via NameCheap, Inc. and the registry expiry is 30 Sep 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/coolremote.me.
coolremote.me publishes 2 nameservers. DNSSEC is signed.
coolremote.me has 1 IPv4 address (3.227.171.236). The geolocation database places 3.227.171.236 in Ashburn, United States.
The TLS certificate from YR2 is not valid (TLS 1.2).
No safety warning was recorded for coolremote.me in the checks that ran.
Domain · RDAP/WHOIS
coolremote.me was registered on 30 Sep 2012 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/coolremote.me.
| Registered | since 30 Sep 2012 |
|---|---|
| Created | 30 September 2012 |
| Updated | 5 September 2026 |
| Expires | 30 September 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | roxy.ns.cloudflare.com, clark.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.identitydigital.services/rdap/domain/coolremote.me |
coolremote.me carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver roxy.ns.cloudflare.com is published for coolremote.me in the registration record from https://rdap.identitydigital.services/rdap/domain/coolremote.me.
Nameserver clark.ns.cloudflare.com is published for coolremote.me in the registration record from https://rdap.identitydigital.services/rdap/domain/coolremote.me.
DNS
coolremote.me has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 3.227.171.236 |
|---|---|
| AAAA | — |
| NS | clark.ns.cloudflare.com, roxy.ns.cloudflare.com |
| MX | coolremote.me (0) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 3.227.171.236 answers for coolremote.me at resolver 1.1.1.1:53.
Mail exchanger coolremote.me has preference 0.
Hosting and geo
coolremote.me is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 3.227.171.236 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for coolremote.me is not valid, with 63 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | app.coolremote.net |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 63 |
| SAN count | 1 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: app.coolremote.net.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://coolremote.me/": tls: failed to verify certificate: x509: certificate is valid for app.coolremote.net, not coolremote.me
Security
Family DNS for coolremote.me is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from 2012-09-30T16:22:18Z to 2012-09-30T16:22:18.671Z.
- October 2026: rdap dnssec changed from unknown to yes.
- October 2026: rdap expires changed from 2027-09-30T16:22:18Z to 2027-09-30T16:22:18.671Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-09-05T06:56:57Z to 2026-09-05T06:56:57.637Z.
- October 2026: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is coolremote.me safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts coolremote.me?
coolremote.me is placed in Ashburn, United States.
When does coolremote.me expire?
coolremote.me expires on 30 September 2027 according to https://rdap.identitydigital.services/rdap/domain/coolremote.me.
Who owns coolremote.me?
The registry did not return a person or a company for coolremote.me. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/coolremote.me at 2026-10-30T14:43:44Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:43:44Z
- TLS source tls:443 at 2026-10-30T14:43:44Z
- HTTP source https://coolremote.me/ at 2026-10-30T14:43:44Z
- Tech source not available at 2026-10-30T14:43:44Z
- Geo source db-ip at 2026-10-30T14:43:44Z
- Safety source family DNS and local lists at 2026-10-30T14:43:44Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.