VirusTotal
checked — no detections recorded
Báo cáoEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
oop-sheets.living — Chưa được xác minh. Tóm tắt bằng chứng: VirusTotal 0/92; URLScan capture; PhishDestroy score 25/100. Nhà đăng ký: Spaceship.
The evidence summary below uses retained observations. Each source keeps its own collection date.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
checked — no detections recorded
Báo cáoEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Report stored; detailed verdict not recorded
Alerts refer to the preserved scan. They do not describe the current state of the site.
3 community references
Báo cáoCommunity publication references, not a vendor verdict or evidence of a common operator.
báo cáo được lưu trữ
View stored capture ↗ Báo cáoA preserved page image documents what the collector received; a capture is not a safety verdict.
Report stored; verdict not recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
Báo cáoA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
Chi tiếtA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.
PhishDestroy first observed oop-sheets.living on Oct 16, 2026. Current evidence score: 25/100 (medium).
On Oct 16, 2026 at 23:25 UTC, VirusTotal recorded 0 detections among 92 engines; AlienVault OTX listed 3 community pulse references (not vendor detections). URLScan captured the page on Oct 16, 2026 at 22:55 UTC.
The collector marked the hostname reachable on Oct 16, 2026 at 22:55 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 16, 2026 at 20:55 UTC. Registration records for the domain list Spaceship, Inc. as the registrar and Oct 15, 2026 as the creation date. Registration and first observation occurred on the same UTC date. At collection time, the hostname resolved to 52.37.165.222. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance.
15 · datasets with records / 16 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Spaceship, Inc. · 52.37.165.222 · DNS, TLS and retained responses
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
launch1.spaceship.netlaunch2.spaceship.netLocation describes the IP network.
Google PageSpeed Insights — mobile performance audit of oop-sheets.living · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://oop-sheets.living/https://oop-sheets.living/Cache-Control: public, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-86ae576d9863640bb556feaaaf83db2832b34b56d14b479361bfb075b35dae7dapublic, max-age=0, must-revalidategzip1121text/html; charset=utf-8Fri, 16 Oct 2026 22:55:06 GMT"e571d2b3c1a50475bbdefa9fca5bf55e"Accept-EncodingValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Các dữ liệu quan sát đã lưu trữ về sự so sánh giữa trình thu thập dữ liệu và trình duyệt đối với máy chủ này, cùng với việc kiểm tra dấu vân tay thời gian thực dành cho các hệ thống phân phối lưu lượng theo phong cách Keitaro.
Local đã lưu trữ2026-10-16 22:55:07UTCChưa có kết quả kiểm tra trực tiếp được lưu.
Collection history, report status and investigation channels
52.37.165.222.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Không rõ
probe_inconclusive
Có thể truy cập
6 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
oop-sheets.living)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
Báo cáo này trình bày bằng chứng được lưu trữ mới nhất có sẵn cho PhishDestroy. Dấu thời gian nguồn được hiển thị nếu có; tính khả dụng và phán quyết của nhà cung cấp có thể thay đổi sau khi thu thập.
PhishDestroy liệt kê oop-sheets.living là đáng ngờ. Nó đã được kiểm tra bởi các công cụ bảo mật 92; phán quyết tự động có thể thay đổi. Việc giám sát vẫn tiếp tục. Đã quan sát thấy: 2026-10-16 23:25:25 UTC
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
Nếu bạn cho rằng danh sách này không chính xác, nộp đơn kháng cáo. Để tìm hiểu về phương pháp của chúng tôi, hãy truy cập Trang câu hỏi thường gặp.