remotecentral.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 55 days left27 years oldTranco #129914
80
remotecentral.com was registered on 31 Dec 1998 via NameSilo, LLC and the registry expiry is 31 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/remotecentral.com.
remotecentral.com publishes 2 nameservers. DNSSEC is not signed.
remotecentral.com has 2 IPv4 addresses (104.21.70.149, 172.67.136.192) and 2 IPv6 addresses (2606:4700:3032::ac43:88c0, 2606:4700:3034::6815:4695). The geolocation database places 104.21.70.149 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 55 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon Advertising, Cloudflare, Google Publisher Tag and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for remotecentral.com in the checks that ran.
Domain · RDAP/WHOIS
remotecentral.com was registered on 31 Dec 1998 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/remotecentral.com.
| Registered | since 31 Dec 1998 |
|---|---|
| Created | 31 December 1998 |
| Updated | 1 January 2026 |
| Expires | 31 December 2026 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | dara.ns.cloudflare.com, james.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/remotecentral.com |
remotecentral.com 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 dara.ns.cloudflare.com is published for remotecentral.com in the registration record from https://rdap.verisign.com/com/v1/domain/remotecentral.com.
Nameserver james.ns.cloudflare.com is published for remotecentral.com in the registration record from https://rdap.verisign.com/com/v1/domain/remotecentral.com.
DNS
remotecentral.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.70.149, 172.67.136.192 |
|---|---|
| AAAA | 2606:4700:3032::ac43:88c0, 2606:4700:3034::6815:4695 |
| NS | dara.ns.cloudflare.com, james.ns.cloudflare.com |
| MX | mx01.mail.icloud.com (10) Apple, mx02.mail.icloud.com (10) Apple |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at remotecentral.com is "v=spf1 a mx ip4:91.99.152.53 include:icloud.com ~all".
The DMARC text record at _dmarc.remotecentral.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.21.70.149 answers for remotecentral.com at resolver 1.1.1.1:53.
IPv4 address 172.67.136.192 answers for remotecentral.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:88c0 answers for remotecentral.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::6815:4695 answers for remotecentral.com at resolver 1.1.1.1:53.
Mail exchanger mx01.mail.icloud.com has preference 10. The host is recognised as Apple.
Mail exchanger mx02.mail.icloud.com has preference 10. The host is recognised as Apple.
Hosting and geo
remotecentral.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.70.149 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for remotecentral.com is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | remotecentral.com |
| Valid from | 26 September 2026 |
| Valid until | 25 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.remotecentral.com, remotecentral.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Amazon Advertising · Advertising
- Cloudflare · CDN
- Google Publisher Tag · Advertising
- HTTP/3 · Miscellaneous
Amazon Advertising is filed under Advertising.
Cloudflare is filed under CDN.
Google Publisher Tag is filed under Advertising.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 26 ms. The target title is 67 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 26 ms |
| Title length | 67 no |
| Quoted title | "Welcome to Remote Central: Universal Remote Control Reviews & More!" |
| Meta description | "Reviews of the latest universal remote controls, a file area, programming help, message forums and more!" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 155 |
| Images | 37 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for remotecentral.com 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 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is remotecentral.com 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 remotecentral.com?
remotecentral.com is placed in Toronto, Canada.
When does remotecentral.com expire?
remotecentral.com expires on 31 December 2026 according to https://rdap.verisign.com/com/v1/domain/remotecentral.com.
Who owns remotecentral.com?
The registry did not return a person or a company for remotecentral.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/remotecentral.com at 2026-10-30T14:11:43Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:11:43Z
- TLS source tls:443 at 2026-10-30T14:11:43Z
- HTTP source https://remotecentral.com/ at 2026-10-30T14:11:43Z
- Tech source wappalyzergo at 2026-10-30T14:11:43Z
- Geo source db-ip at 2026-10-30T14:11:43Z
- Safety source family DNS and local lists at 2026-10-30T14:11:43Z
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.