탐지를 보고하는 보안 엔진: 6. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 13 days 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.
oglocker.pro is an impersonation phishing site that copies the look and feel of a trusted service so visitors believe they are on the real thing. PhishDestroy first flagged it on 2026-10-06. When last checked on 2026-10-19, the server was still responding, but the domain's DNS was inactive. The page carries only the generic title "Loading" with no brand name, while our classification is based on the impersonation behaviour behind it.
How the scam works
Impersonation pages like this usually open with a neutral holding screen such as "Loading". The real content then presents a convincing copy of a login, verification or account-recovery form. Anything typed there goes straight to the operators: usernames, passwords, one-time 2FA codes and, on crypto-themed clones, seed phrases or private keys. With those in hand, the attackers log in as the victim or sweep the wallet, and the theft is effectively irreversible.
Evidence
On 2026-10-10, 6 of 92 VirusTotal engines marked the domain as malicious. The vendors were alphaMountain.ai, Bfore.Ai PreCrime, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That count is modest, but it comes from several unrelated vendors, including predictive services that score new domains before they are widely abused. Spamhaus separately lists the domain in its DBL as spam, and it appears on the PhishDestroy blocklist.
Infrastructure
The domain was registered through Dynadot Inc on 2026-08-29, about five weeks before PhishDestroy caught it. That short gap fits a throwaway domain bought for a single campaign. The site is hosted at 46.29.26.38, an address located in Finland and announced by a network registered to M/S Robi Traders in Bangladesh. Its free Let's Encrypt certificate gives the page a padlock in the browser, which says nothing about whether the operator can be trusted.
What to do
If you entered a password on this site, change it immediately on the genuine service and on any account that reuses it. Then sign out of all active sessions. Treat any 2FA code you submitted as compromised, and switch to an authenticator app or hardware key where possible. If you typed a seed phrase or private key, assume the wallet is lost and move any remaining funds to a newly created wallet at once. Defenders should block oglocker.pro and the 46.29.26.38 address at DNS and proxy level, and search logs for earlier visits.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-19 10:08:06 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-09 10:12:57 UTClast content: 2026-10-09 10:12:57 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:12:57 UTC → 2026-10-09 20:20:42 UTC · 10.13hmidpoint estimate ≈ 2026-10-09 15:16:49 UTC · precision medium · basis bounded
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.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 oglocker.pro)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
About this reportSources, observation dates and corrections
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.
(US)
