Is tika.com down?
Contact appears to be a general website. StarNama monitors tika.com for live uptime, response time, SSL status, server location, technology signals, and user reports so visitors can quickly understand whether the website is available or having access problems.
HTTP status completes first. Website information and validated SSL are refreshed in the following analysis phase.
Scores describe the observed technical signals. Response speed is measured from our server; it is not a browser loading or Core Web Vitals score.
tika.com: Service issue
HTTP TLS_ERROR · Response 83 ms
What the check found
No diagnostic result is available yet.
Check stage: tls
Server & domain information
| Title | Contact |
|---|---|
| Language | en |
| CMS / platform | Unknown |
| Category | General Website |
| Server IP | 34.149.91.73 |
| Meta description | N/A |
| Robots.txt | Not detected |
| Sitemap | Not detected |
| Target server location | United States, Kansas City |
| SSL status | Previous result: No SSL detected (awaiting validation) · Expires: N/A |
IP location can describe a CDN edge. It does not identify the check origin or prove where the website owner is based.
AD
Performance & screenshot
Run a browser performance analysis or request a screenshot when you need it. Existing results are reused while fresh.
Not requested.
Not requested.
Website intelligence
Contact appears to be a general website. StarNama monitors tika.com for live uptime, response time, SSL status, server location, technology signals, and user reports so visitors can quickly understand whether the website is available or having access problems.
Visible homepage content: 1 detected words. Last analysis: 2026-10-11 23:36:57
Detected technologies
Security headers
| strict-transport-security | Not detected |
|---|---|
| content-security-policy | Not detected |
| x-frame-options | Not detected |
| x-content-type-options | Not detected |
| referrer-policy | Not detected |
Detected technology and header values are public observations, not a security audit or malware verdict.
AD
Technical signals & recommendations
Positive signals
- More completed checks are needed.
Recommended next steps
- Review the check stage, sample coverage and SSL details before drawing conclusions.
Report completeness: 80/100. This measures the evidence collected for this report.
Measured observations
tika.com monitoring observations
The latest stored observation for tika.com was recorded at 2026-11-05 22:50:02 UTC. Its observed status is DEGRADED, with HTTP result TLS_ERROR and response time 83 ms. This is the result of the most recent probe from StarNama, rather than a guarantee that every visitor can access the website.
This report contains 201 retained historical checks. Of the 201 checks with a known availability result, 110 returned a successful HTTP response. The proportion of successful checks is 54.73 percent. This percentage describes collected samples; gaps between checks are not assumed to be monitored uptime.
Measured responses in the retained history average 351.67 ms across 201 samples. These server response measurements describe HTTP probe latency. Browser loading performance, rendering and Core Web Vitals require the separate performance analysis.
The observed website title is "Contact". The stored page description is N/A. Detected technologies include Server: cloudflare. Robots.txt was Not detected; the sitemap was Not detected. These observations can change when the target returns a maintenance page, redirects or restricts automated access.
Stored observations stay available while a requested refresh is waiting or running. An unavailable measurement does not mean that the website is offline. Access restrictions, DNS errors, TLS failures and server errors are reported separately when detected. Compare the check time, historical samples and diagnostic details with your own connection when investigating an access problem.
Historical checks
Successful checks: 54.73%
Samples: 201
Average response: 352 ms
The percentage is a share of successful observations, not guaranteed time-based uptime.
Recent samples, oldest to newest. Green: online · Red: offline · Amber: restricted / service issue · Gray: unknown.
Recent check details
| Checked at | Status | HTTP | Response |
|---|---|---|---|
| 2026-11-05 22:50:02 | DEGRADED | TLS_ERROR | 83 ms |
| 2026-11-05 19:02:48 | DEGRADED | TLS_ERROR | 42 ms |
| 2026-11-05 15:21:52 | DEGRADED | TLS_ERROR | 41 ms |
| 2026-11-05 10:35:09 | DEGRADED | TLS_ERROR | 41 ms |
| 2026-11-05 05:10:01 | DEGRADED | TLS_ERROR | 48 ms |
| 2026-11-05 00:15:02 | DEGRADED | TLS_ERROR | 99 ms |
| 2026-11-04 19:25:15 | DEGRADED | TLS_ERROR | 50 ms |
| 2026-11-04 14:25:10 | DEGRADED | TLS_ERROR | 53 ms |
| 2026-11-04 09:20:12 | UP | 200 | 1021 ms |
| 2026-11-04 04:19:19 | DEGRADED | TLS_ERROR | 40 ms |
| 2026-11-03 23:35:10 | DEGRADED | TLS_ERROR | 44 ms |
| 2026-11-03 19:05:16 | DEGRADED | TLS_ERROR | 46 ms |
| 2026-11-03 14:30:13 | DEGRADED | TLS_ERROR | 46 ms |
| 2026-11-03 10:29:49 | DEGRADED | TLS_ERROR | 41 ms |
| 2026-11-03 05:10:03 | UP | 200 | 366 ms |
| 2026-11-02 23:20:02 | DEGRADED | TLS_ERROR | 45 ms |
| 2026-11-02 18:15:04 | UP | 200 | 1406 ms |
| 2026-11-02 13:20:05 | UP | 200 | 845 ms |
| 2026-11-02 07:40:02 | DEGRADED | TLS_ERROR | 88 ms |
| 2026-11-02 02:25:12 | DEGRADED | TLS_ERROR | 82 ms |
Website change history
- 2026-07-10 16:25:17 status: DOWN → UP code: cURL error 35: Recv failure: Connection reset by peer → 405
- 2026-06-04 09:55:33 code: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443 → cURL error 35: Recv failure: Connection reset by peer
- 2026-06-04 09:25:10 code: cURL error 35: Recv failure: Connection reset by peer → cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443
- 2026-06-04 09:20:16 code: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443 → cURL error 35: Recv failure: Connection reset by peer
- 2026-06-03 23:40:04 code: cURL error 35: Recv failure: Connection reset by peer → cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443
- 2026-06-03 23:35:04 code: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443 → cURL error 35: Recv failure: Connection reset by peer
- 2026-06-03 02:55:08 code: cURL error 35: Recv failure: Connection reset by peer → cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443
- 2026-06-03 02:50:09 code: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to tika.com:443 → cURL error 35: Recv failure: Connection reset by peer
Community reports
0 issue reports today (UTC).
0 working · 0 not working
Community observations complement server checks. Repeated submissions are limited.
Public API & website badges
Embed the latest observed status, response time and technical health score.
Open SVG badge · Open HTML badge
The public API is disabled in StarNama settings. Status badges and widgets are available separately.
Claim this website
Prove domain control to add an official description. Verification supports a homepage meta tag, a verification file or DNS TXT record.
Compare & explore
Monitoring alerts
The StarNama Telegram bot supports status-change alerts for monitored domains.
Understand the evidence
One observation describes one moment from one monitoring location. More independent samples improve confidence.
When the site does not work for you
Compare the server check with your own connection. An online observation does not rule out regional, DNS, account or payment problems.
Local troubleshooting steps
- Try a hard refresh or a private browser window.
- Check another device and network to separate a local connection issue.
- Check DNS resolution and whether your device clock is correct for TLS.
- Report the specific problem above, including login or payment failures when the homepage still loads.
Windows DNS cache: ipconfig /flushdns. macOS DNS cache: sudo killall -HUP mDNSResponder.
FAQ
Is this site down now? Latest observation: Service issue.
Does it have a valid SSL certificate? Previous result: No SSL detected (awaiting validation) · Expires: N/A
How do I check again? Use Check again; the stored report stays visible while the next check runs.