VirusTotal
18 / 91 engine detections
보고서 열기“oortstorages.com”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
oortstorages.com — 마지막으로 알려진 활성 (HTTP 200). 사기 유형: Impersonation. 증거 요약: VirusTotal 18/91 (Abusix, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); URLQuery 5 alerts; Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 100/100. 등록기관: GoDaddy.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
18 / 91 engine detections
보고서 열기5 threat-system alerts
보고서 열기악성
보고서 열기DBL_PHISH
4 community references
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | oortstorages.com |
malicious | Sinkholed |
| DNS4EU | oortstorages.com |
malicious | Sinkholed |
| Quad9 DNS | oortstorages.com |
malicious | Sinkholed |
| OpenDNS | oortstorages.com |
phishing | Phishing Block |
| DigiCert UltraDNS | oortstorages.com |
malicious | Sinkholed |
AI-assisted evidence review
oortstorages.com returned HTTP 200 on 2026-10-01, a dated response recorded during an HTTP check. The domain was first observed on 2026-09-18, and its registration date is listed as 2025-03-11.
OTX recorded 4 pulses for oortstorages.com on 2026-09-19. VirusTotal reported 18 detections across 91 scanners on 2026-09-29. The PhishDestroy internal listing included the domain, and its SSL certificate was issued by GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1, scanned on 2026-09-19. The registrar is recorded as GoDaddy.com, LLC.
The OTX, VirusTotal, and PhishDestroy records were collected on separate dates, so each reflects only its own snapshot. Because the HTTP check, SSL scan, and detection counts come from different days, direct comparison across them is limited to what each dated source states. The registration and certificate details add context without indicating any particular activity.
Retain all dated records for oortstorages.com so later observations can be compared against them. When reviewing subsequent reports, note the collection date of each source before drawing comparisons. Avoid submitting sensitive information to oortstorages.com while the review is in progress.
ns05.domaincontrol.comns06.domaincontrol.comLocation describes the IP network.
db807e4dbaa7ac02843a42fbd36ba5631e1607ae3feaf3e86d4f5afe25758e47www.oortstorages.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.oortstorages.comDomain recordThe original observation time is not recorded for these hostnames.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
oortstorages.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
No threat flag
View source18/91 engine detections
View source4 community references
View sourcePD-20260918-C5B00D
Page captured
View sourceoortstorages.com
View sourcePD-20260918-C5B00D Recipient: abuse@godaddy.com 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
oortstorages.com)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.