VirusTotal
13 / 91 engine detections
보고서 열기“406 Not Acceptable”
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; 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.
royalbankatlas.com — 마지막으로 알려진 활성 (HTTP 200). 사기 유형: Impersonation. 증거 요약: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLQuery 2 alerts; URLScan malicious verdict; PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
13 / 91 engine detections
보고서 열기2 threat-system alerts
보고서 열기악성
보고서 열기4 community references
보고서 열기provider verdict: clean
보고서 열기80/100
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
royalbankatlas.com is a banking impersonation phishing site. Its name borrows "Royal Bank" wording to look like a legitimate bank's online portal, and urlscan.io matched its content to a generic banking brand. It targets people who bank online and might trust a familiar-sounding name. PhishDestroy first flagged it on 2026-09-16, and it was still online with live content on 2026-10-19.
Sites like this copy the look of a bank's sign-in page so that anyone arriving from a text, email or search ad types in their username, password and often one-time codes or card details. Those credentials go straight to the operators, who can then log into the real account, move money, or use the personal data for further fraud. When last checked, the page title read "406 Not Acceptable", a server error message, while our classification is impersonation phishing based on the detections below.
Thirteen of 91 VirusTotal engines flagged the domain as of 2026-09-29. They include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF and Gridinsoft. That count is moderate, but it comes from several independent vendors rather than one outlier. urlscan.io returned a malicious verdict, the domain sits on the PhishDestroy blocklist, and it appears in four AlienVault OTX threat pulses, which means other researchers have tracked it too.
The domain was registered through Dynadot Inc on 2026-09-07, only nine days before PhishDestroy detected it. Short-lived, freshly registered domains are typical of phishing runs. It is hosted at 198.251.81.188 on the FranTech Solutions network in the United States. The site carries a free Let's Encrypt certificate, so the browser padlock says nothing about whether the bank behind it is real.
If you entered a username or password here, change it right away through your bank's official app or the number on your card, and turn on or reset two-factor authentication. If you typed card numbers, one-time codes or answers to security questions, call your bank's fraud line, ask them to block the card, and review recent transactions. Treat any follow-up calls or messages claiming to be your bank with suspicion. Defenders should block the domain and its hosting IP at DNS and proxy level, and search mail and web logs for users who visited it.
ns17.my-control-panel.comns18.my-control-panel.comroyalbankatlas.compriority 0Location describes the IP network.
00aa2842c44b4069f9c74e024e275db0ebd77a98ebaa06f017f619f37892f699www.account.royalbankatlas.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.account.royalbankatlas.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of royalbankatlas.com · checked Sep 16, 2026
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.
alive_content: raw=ok; http=200; via=https_proxy; server=Caddy
royalbankatlas.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
알 수 없음→live_content
content_served
6→7
4→6
4 community references
View sourceNo threat flag
View source13/91 engine detections
View sourcePD-20260915-E8873E
Page captured
View sourceroyalbankatlas.com
View sourcePD-20260915-E8873E Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
royalbankatlas.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.