The domain rainbow-kataifi-98620f.netlify.app returned an HTTP 503 status when checked on 2026-10-03, indicating a service issue at that time. Google Safe Browsing also flagged this domain for social engineering on 2026-09-27.
Recorded Evidence
Google Safe Browsing identified rainbow-kataifi-98620f.netlify.app for social engineering on 2026-09-27. VirusTotal, as of 2026-09-21, reported 22 detections out of 89 scanners. The domain appeared in the PhishDestroy internal listing. The HTTP status was 503 on 2026-10-03. The SSL certificate was issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1, as recorded on 2026-09-13. A PageSpeed test on 2026-09-13 gave a performance score of 60.
Interpretation
The records from Google Safe Browsing, VirusTotal, and PhishDestroy show that several sources have noted security-related findings for this domain. The HTTP 503 status indicates the site was not serving standard content on the date checked. Technical details such as the SSL certificate and PageSpeed score provide additional context about the domain's configuration at the time of observation.
Recommended Actions
Review the Google Safe Browsing, VirusTotal, and PhishDestroy records for rainbow-kataifi-98620f.netlify.app to inform any next steps. Preserve the dated HTTP status and performance results for future comparison. Continue monitoring these sources for updates relevant to the domain.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rainbow-kataifi-98620f.netlify.app', port=80): Max retries exceeded with url: / (Caused by
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478Certificate names · 1 SANs
netlify.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 10:15:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 01:49:46 UTClast content: 2026-10-11 01:49:46 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 2 identified
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
Google PageSpeed Insights — mobile performance audit of rainbow-kataifi-98620f.netlify.app· checked Sep 13, 2026
60
Needs Work
Performance
FCP
3.75s
First Contentful Paint
LCP
4.8s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
523ms
Total Blocking Time
SI
3.94s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Status Check2026-09-13 05:34:46 UTC
Telemetry event observed.
Threat First Observed2026-09-13 05:34:25 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 35.157.26.135.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(US)
