titledesktop.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe16 years oldTranco #209868
30
titledesktop.com was registered on 12 May 2010 via Register.com - Network Solutions, LLC and the registry expiry is 12 May 2029. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/titledesktop.com.
titledesktop.com publishes 5 nameservers. DNSSEC is not signed.
titledesktop.com has 1 IPv4 address (34.198.182.201). The geolocation database places 34.198.182.201 in Ashburn, United States.
No safety warning was recorded for titledesktop.com in the checks that ran.
Domain · RDAP/WHOIS
titledesktop.com was registered on 12 May 2010 via Register.com - Network Solutions, LLC. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/titledesktop.com.
| Registered | since 12 May 2010 |
|---|---|
| Created | 12 May 2010 |
| Updated | 11 April 2026 |
| Expires | 12 May 2029 |
| Registrar | Register.com - Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/titledesktop.com |
titledesktop.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 ns1.no-ip.com is published for titledesktop.com in the registration record from https://rdap.verisign.com/com/v1/domain/titledesktop.com.
Nameserver ns2.no-ip.com is published for titledesktop.com in the registration record from https://rdap.verisign.com/com/v1/domain/titledesktop.com.
Nameserver ns3.no-ip.com is published for titledesktop.com in the registration record from https://rdap.verisign.com/com/v1/domain/titledesktop.com.
Nameserver ns4.no-ip.com is published for titledesktop.com in the registration record from https://rdap.verisign.com/com/v1/domain/titledesktop.com.
DNS
titledesktop.com has 1 address record, 1 mail exchanger and 5 nameservers, measured at 1.1.1.1:53.
| A | 34.198.182.201 |
|---|---|
| AAAA | — |
| NS | ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com |
| MX | titledesktop-com.mail.protection.outlook.com (5) Microsoft 365 |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 34.198.182.201 answers for titledesktop.com at resolver 1.1.1.1:53.
Mail exchanger titledesktop-com.mail.protection.outlook.com has preference 5. The host is recognised as Microsoft 365.
Hosting and geo
titledesktop.com is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 34.198.182.201 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for titledesktop.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 34.198.182.201:443: connect: connection refused
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://titledesktop.com/": dial tcp 34.198.182.201:443: connect: connection refused
Security
Family DNS for titledesktop.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 0 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
- October 2026: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is titledesktop.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 titledesktop.com?
titledesktop.com is placed in Ashburn, United States.
When does titledesktop.com expire?
titledesktop.com expires on 12 May 2029 according to https://rdap.verisign.com/com/v1/domain/titledesktop.com.
Who owns titledesktop.com?
The registry did not return a person or a company for titledesktop.com. RDAP often redacts the registrant. The registrar on file is Register.com - Network Solutions, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/titledesktop.com at 2026-10-30T14:17:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:17:10Z
- TLS source tls:443 at 2026-10-30T14:17:10Z
- HTTP source https://titledesktop.com/ at 2026-10-30T14:17:10Z
- Tech source not available at 2026-10-30T14:17:10Z
- Geo source db-ip at 2026-10-30T14:17:10Z
- Safety source family DNS and local lists at 2026-10-30T14:17:10Z
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.