보안 보고서로 이동
도메인 보안 및 위협 인텔리전스
royalbankatlas.com favicon

royalbankatlas.com

“406 Not Acceptable”

등록기관
Dynadot
Resolved IP
198.251.81.188
Registered
2026년 9월 7일
PhishDestroy assessment 심각
가용성 마지막으로 알려진 활성 최근에 저장된 도달 가능성 관찰 관측됨 · HTTP probe
VirusTotal 탐지: 13/91 URLQuery threat systems: 2 alerts 사기 유형: Impersonation
OTX: 4 refs 2026년 9월 16일 1 Report Sent
API
이 도메인은 악성 도메인으로 표시되었습니다.
탐지를 보고하는 보안 엔진: 13. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
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; 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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260915-E8873E
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
보고서 요약

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 분석은 영어로 유지됩니다.

Source evidenceVirusTotal 13 / 91 · OTX 4 references 7 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

네트워크 보안 인텔리전스
Threat Detection Systems 2 alerts
Detection System Indicator Verdict Alert
OpenDNS royalbankatlas.com phishing Phishing Block
DNS4EU royalbankatlas.com malicious Sinkholed

Analysis

심각
VirusTotal
13 / 91
OTX
4 community refs
Page captures
4

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

저장된 캡처 · 4 captures

Domain details

도메인
URLScan verdict 악성 score 100 Phishing report ↗
IP 평판 abuse score 1/100 2 reports PhishingBad Web Bot checked 2026년 10월 16일
OTX tags 2026-09activeall-domainsblocklistcontentcrypto도메인drainerfraudlivemonthlyphishdestroyphishingscam
등록기관 Dynadot (Unknown)
악용 신고 연락처abuse@dynadot.com
ICANN 레지스트리ICANN Lookup (RDAP) →
등록 정보생성됨 2026년 9월 7일 (41d · New) — Expires 2027년 9월 7일
HTTP 상태200
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 16일
DOM Analysisanalyzed 2026년 9월 16일score 98/1001 brand signal
Submitted URLhttps://royalbankatlas.com/
Favicon Hash
사건 ID
Observed page title
406 Not Acceptable
Automated brand references
Google
TLS 인증서
발급자 Let's Encrypt / YR2 · stored validity ends in 48 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
198.251.81.188
Network ASN
AS53667
Organization
FranTech Solutions
Observed location
Staten Island, US
Server header
LiteSpeed

네임서버 2

  • ns17.my-control-panel.com
  • ns18.my-control-panel.com

Mail routing 1 MX record

  • royalbankatlas.compriority 0

Location describes the IP network.

TLS 인증서

Issuer
Let's Encrypt / YR2
Valid from
2026-09-07 23:06:03
Valid until
2026-12-06 23:06:02
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-16 01:02:09 UTC
Collection source
PhishDestroy collector
Certificate fingerprint00aa2842c44b4069f9c74e024e275db0ebd77a98ebaa06f017f619f37892f699
Certificate names · 1 SANs
  • www.account.royalbankatlas.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 10:26:31 UTC

Primary outcome 활성 콘텐츠 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation 활성 콘텐츠 Ordinary HTTP content served 90% 2026-10-19 10:26:31 UTC
RDAP registration 알 수 없음
Observed timeline last reachable: 2026-10-19 10:26:31 UTC last content: 2026-10-19 10:26:31 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.
Recorded subdomains1

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 record

The original observation time is not recorded for these hostnames.

기술 · 9 identified
Detected via Cloudflare Radar · Wappalyzer engine
이 도메인 신고하기 증거를 제출하고 다른 사람들을 보호하는 데 힘을 보태주세요

VirusTotal 분석

13 / 91 보안 공급업체가 이 도메인에 플래그를 지정했습니다.
View on VT
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SOCRadar
소포스
VIPRE
desenmascara.me

보관된 증거

Wayback Machine Snapshot
증거 검토를 위해 과거 스냅샷을 사용할 수 있습니다.
View Archive
사이트 성능 분석

Google PageSpeed Insights — mobile performance audit of royalbankatlas.com · checked Sep 16, 2026

64
Needs Work
Performance
FCP
2.74s
First Contentful Paint
LCP
9.16s
Largest Contentful Paint
CLS
0.007
Cumulative Layout Shift
TBT
61ms
Total Blocking Time
SI
7.22s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=Caddy

Browser
406 Not Acceptable
Crawler
royalbankatlas.com
royalbankatlas.com
저장된 결과
Keitaro TDS
Stored observation history19

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  2. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  3. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  4. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  5. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

Earlier observations 14
  1. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  2. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  3. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  4. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  5. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  6. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  7. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  8. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  9. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  10. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  11. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  12. Availability monitor · Recorded state

    알 수 없음→live_content

    content_served

  13. VirusTotal · Detection count

    6→7

  14. VirusTotal · Detection count

    4→6

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    13/91 engine detections

    View source
  4. Abuse report sent

    PD-20260915-E8873E

    abuse@dynadot.com
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    royalbankatlas.com

    View source

증거 및 외부 보고서

제출된 증거 스냅샷
Sent: Ledger records: 1 Case ID: PD-20260915-E8873E Recipient: abuse@dynadot.com
Page title stored with report: New Private Tab
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider
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
심층 분석
Help & reporting

이 사이트로 인해 영향을 받으셨나요?

7 evidence signal groups linked 1 stored notification records 마지막으로 알려진 활성
If credentials were compromised, report immediately. Do not engage with recovery scammers.

계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.

Official reporting routes

회복 사기꾼들을 조심하세요! 범죄자는 수사관, 변호사, 회복요원인 척 하면서 피해자에게 다시 연락할 수도 있습니다. 선불 비용을 지불하거나 자격 증명을 공유하지 마십시오. 회복 관련 사기에 대해 자세히 알아보기 →

지역 당국에 신고하십시오

공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.

97개국 디렉토리

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 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 royalbankatlas.com)
  • 커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름

비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.

이 사기 사건을 어디에 신고해야 할까요?

  • FBI IC3 — 인터넷 범죄 신고 센터 (미국 연방 신고 창구)
  • 유로폴 — 유럽 사이버 범죄 신고 (EU)
  • 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, 맞춤법, 도메인 등록 기간을 확인하세요.
  • "너무 좋아서 믿기 힘들다" = 사기 — 수익 보장, 유명인의 추천, 촉박한 마감 기한

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

최신 정보를 확인하고, 안전을 지키세요

실시간 위협을 모니터링하거나, 오탐이라고 판단될 경우 이 목록에 이의를 제기하십시오.

실시간 위협 정보 이 목록에 이의 제기하기
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

이 보고서 삽입하기

이 위협 정보를 귀하의 웹사이트나 블로그에 공유하세요

embed.html
<iframe
  src="https://phishdestroy.io/ko/embed/domain/royalbankatlas.com"
  title="PhishDestroy threat report for royalbankatlas.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>