linkhot01.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 79 days left3 years old
50
linkhot01.com was registered on 30 May 2023 via Name.com, Inc. and the registry expiry is 30 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/linkhot01.com.
linkhot01.com publishes 2 nameservers. DNSSEC is not signed.
linkhot01.com has 2 IPv4 addresses (104.21.92.32, 172.67.185.205). The geolocation database places 104.21.92.32 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 79 days left (TLS 1.3).
No safety warning was recorded for linkhot01.com in the checks that ran.
Domain · RDAP/WHOIS
linkhot01.com was registered on 30 May 2023 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/linkhot01.com.
| Registered | since 30 May 2023 |
|---|---|
| Created | 30 May 2023 |
| Updated | 7 May 2026 |
| Expires | 30 May 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | kurt.ns.cloudflare.com, naya.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/linkhot01.com |
linkhot01.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 kurt.ns.cloudflare.com is published for linkhot01.com in the registration record from https://rdap.verisign.com/com/v1/domain/linkhot01.com.
Nameserver naya.ns.cloudflare.com is published for linkhot01.com in the registration record from https://rdap.verisign.com/com/v1/domain/linkhot01.com.
DNS
linkhot01.com has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.92.32, 172.67.185.205 |
|---|---|
| AAAA | — |
| NS | kurt.ns.cloudflare.com, naya.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.92.32 answers for linkhot01.com at resolver 1.1.1.1:53.
IPv4 address 172.67.185.205 answers for linkhot01.com at resolver 1.1.1.1:53.
A random label under linkhot01.com also resolved, which means wildcard DNS is on.
Hosting and geo
linkhot01.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.92.32 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for linkhot01.com is valid, with 79 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | linkhot01.com |
| Valid from | 20 October 2026 |
| Valid until | 18 January 2027 |
| Days left | 79 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.linkhot01.com, linkhot01.com.
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 |
|---|
context deadline exceeded
Security
Family DNS for linkhot01.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 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 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is linkhot01.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 linkhot01.com?
linkhot01.com is placed in Toronto, Canada.
When does linkhot01.com expire?
linkhot01.com expires on 30 May 2027 according to https://rdap.verisign.com/com/v1/domain/linkhot01.com.
Who owns linkhot01.com?
The registry did not return a person or a company for linkhot01.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/linkhot01.com at 2026-10-30T14:02:04Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:02:04Z
- TLS source tls:443 at 2026-10-30T14:02:04Z
- HTTP source https://linkhot01.com/ at 2026-10-30T14:02:04Z
- Tech source not available at 2026-10-30T14:02:04Z
- Geo source db-ip at 2026-10-30T14:02:04Z
- Safety source family DNS and local lists at 2026-10-30T14:02:04Z
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.