StarNama
API Access
Website health report

Is yt2.com down?

yt2.com appears to be a general website. StarNama monitors yt2.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.

Printable report
65Technical health
Service issue
TLS_ERRORHTTP
74 msResponse
CGrade
Showing the latest stored report.
Last completed check: 5 minutes agoMeasured at: Check origin: StarNama server (single location)

HTTP status completes first. Website information and validated SSL are refreshed in the following analysis phase.

Availability samples92/100
Response speed95/100
Security signals0/100
Report completeness70/100

Scores describe the observed technical signals. Response speed is measured from our server; it is not a browser loading or Core Web Vitals score.

?

yt2.com: Service issue

HTTP TLS_ERROR · Response 74 ms

What the check found

No diagnostic result is available yet.

Check stage: tls

Server & domain information

TitleN/A
LanguageN/A
CMS / platformUnknown
CategoryGeneral Website
Server IP47.77.197.181
Meta descriptionN/A
Robots.txtNot detected
SitemapNot detected
Target server locationUnited States, Minkler
SSL statusPrevious 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.

Advanced analysis

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

yt2.com appears to be a general website. StarNama monitors yt2.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: 0 detected words. Last analysis: 2026-10-12 12:32:03

Detected technologies

Server: Tengine

Security headers

strict-transport-securityNot detected
content-security-policyNot detected
x-frame-optionsNot detected
x-content-type-optionsNot detected
referrer-policyNot detected

Detected technology and header values are public observations, not a security audit or malware verdict.

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: 70/100. This measures the evidence collected for this report.

Measured observations

yt2.com monitoring observations

The latest stored observation for yt2.com was recorded at 2026-10-13 22:20:03 UTC. Its observed status is DEGRADED, with HTTP result TLS_ERROR and response time 74 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 91 retained historical checks. Of the 91 checks with a known availability result, 84 returned a successful HTTP response. The proportion of successful checks is 92.31 percent. This percentage describes collected samples; gaps between checks are not assumed to be monitored uptime.

Measured responses in the retained history average 349.71 ms across 91 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 "N/A". The stored page description is N/A. Detected technologies include Server: Tengine. 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: 92.31%

Samples: 91

Average response: 350 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 atStatusHTTPResponse
2026-10-13 22:20:03DEGRADEDTLS_ERROR74 ms
2026-10-13 05:06:30UP20044 ms
2026-10-12 15:14:38UP20042 ms
2026-10-12 02:45:02UP20049 ms
2026-10-11 09:46:04UP20046 ms
2026-10-10 02:11:04UP20049 ms
2026-10-09 14:11:49UP20044 ms
2026-10-09 09:55:02UP20054 ms
2026-10-08 12:51:06UP20090 ms
2026-10-07 08:51:08UP20055 ms
2026-10-07 04:50:11UP20049 ms
2026-10-06 11:01:04UP20059 ms
2026-10-05 11:31:53UP20043 ms
2026-10-05 06:56:01UP20055 ms
2026-10-03 23:20:03UP20062 ms
2026-10-03 17:20:02UP20045 ms
2026-10-03 14:32:49UP20044 ms
2026-10-03 13:16:00UP20055 ms
2026-10-03 11:33:47UP20044 ms
2026-10-03 09:10:05UP20052 ms

Website change history

  • 2026-09-26 18:11:25 ip: yt2.com → 47.77.197.181
  • 2026-09-26 08:56:02 status: DOWN → UP code: cURL error 6: Could not resolve host: yt2.com → 200
  • 2026-09-25 12:50:02 ip: 103.233.255.49 → yt2.com title: 您正在访问的域名 yt2.com 可以转让! → N/A
  • 2026-09-24 11:32:37 status: UP → DOWN code: 200 → cURL error 6: Could not resolve host: yt2.com
  • 2026-09-16 21:57:14 title: 502 Bad Gateway → 您正在访问的域名 yt2.com 可以转让!
  • 2026-09-15 20:58:30 title: 您正在访问的域名 yt2.com 可以转让! → 502 Bad Gateway
  • 2026-09-03 16:50:05 code: 502 → 200
  • 2026-09-02 16:41:34 code: 200 → 502

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.

yt2.com observed status badge

Open SVG badge · Open HTML badge

Public API URL

Public API returns the latest stored observation.

SVG badge
HTML badge
Live JS widget
Mini JS widget

Widget preview

Loading widget preview…

Open widget script

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
  1. Try a hard refresh or a private browser window.
  2. Check another device and network to separate a local connection issue.
  3. Check DNS resolution and whether your device clock is correct for TLS.
  4. 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.