192-168-8-1.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
192-168-8-1.com was registered on 1 Aug 2019 via NameCheap, Inc. and the registry expiry is 1 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/192-168-8-1.com.
192-168-8-1.com publishes 2 nameservers. DNSSEC is not signed.
192-168-8-1.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 53 days left (TLS 1.3).
Tech detection named Cloudflare, HTTP/3, LiteSpeed, LiteSpeed Cache and Litespeed Cache. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for 192-168-8-1.com in the checks that ran.
192-168-8-1.com was registered on 1 Aug 2019 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/192-168-8-1.com.
| Registered | since 1 Aug 2019 |
|---|---|
| Created | 1 August 2019 |
| Updated | 2 August 2026 |
| Expires | 1 August 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | fay.ns.cloudflare.com, mitch.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/192-168-8-1.com |
192-168-8-1.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 fay.ns.cloudflare.com is published for 192-168-8-1.com in the registration record from https://rdap.verisign.com/com/v1/domain/192-168-8-1.com.
Nameserver mitch.ns.cloudflare.com is published for 192-168-8-1.com in the registration record from https://rdap.verisign.com/com/v1/domain/192-168-8-1.com.
192-168-8-1.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | fay.ns.cloudflare.com, mitch.ns.cloudflare.com |
| MX | mx1-hosting.jellyfish.systems (5), mx2-hosting.jellyfish.systems (10), mx3-hosting.jellyfish.systems (20) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at 192-168-8-1.com is "v=spf1 +a +mx +ip4:162.0.215.159 include:spf.web-hosting.com ~all".
IPv4 address 188.114.96.3 answers for 192-168-8-1.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for 192-168-8-1.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for 192-168-8-1.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for 192-168-8-1.com at resolver 1.1.1.1:53.
Mail exchanger mx1-hosting.jellyfish.systems has preference 5.
Mail exchanger mx2-hosting.jellyfish.systems has preference 10.
Mail exchanger mx3-hosting.jellyfish.systems has preference 20.
192-168-8-1.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for 192-168-8-1.com is valid, with 53 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | 192-168-8-1.com |
| Valid from | 24 September 2026 |
| Valid until | 23 December 2026 |
| Days left | 53 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.192-168-8-1.com, 192-168-8-1.com.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
The homepage returned HTTP 503 in 863 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 503 |
|---|---|
| TTFB | 863 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for 192-168-8-1.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.
Availability 10 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 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
192-168-8-1.com is placed in Toronto, Canada.
192-168-8-1.com expires on 1 August 2027 according to https://rdap.verisign.com/com/v1/domain/192-168-8-1.com.
The registry did not return a person or a company for 192-168-8-1.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.