セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
royalscreditcapital.com favicon

royalscreditcapital.com

“Bot Verification”

レジストラ
Hostinger
Resolved IP
198.251.84.200
Registered
2025年10月16日
PhishDestroy assessment クリティカル
First observed Oct 1, 2026 00:19 UTC · PhishDestroy
VirusTotal 検出数: 10/91 Spamhaus DBL: DBL_SPAM 詐欺タイプ: Impersonation
OTX: 2 refs 2026年10月1日 1 Report Sent
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 10。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
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-tracker@hostinger.com. The latest stored availability evidence still shows the domain reachable; 19 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.

Elapsed since first report
19 days
Reports sent
1
Latest case ID
PD-20261001-0648E9
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
レポート概要

フィッシング: royalscreditcapital.com — 未検証. 証拠の概要: VirusTotal 10/91 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, ESET, Forcepoint ThreatSeeker); URLQuery 2…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 10 / 91 · OTX 2 references 7 sources

Spamhaus DBL

DBL_SPAM

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

Analysis

クリティカル
VirusTotal
10 / 91
OTX
2 community refs
Page captures
3

PhishDestroy threat report

Overview

royalscreditcapital.com is an impersonation phishing site dressed up as a credit and capital provider. It targets people looking for loans, credit lines or banking services. urlscan.io matched its content to a generic banking brand. PhishDestroy first flagged it on 2026-10-01. As of 2026-10-19 the domain still responded, but its DNS was no longer serving the phishing content.

How the scam works

Fake lenders and banking clones copy the look of a legitimate finance portal. They then ask visitors to log in, apply for credit or verify their identity. Anything typed into those forms goes straight to the operators: online banking credentials, card numbers, ID documents and contact details. Those details can be used for account takeover, fraudulent applications or follow-up advance-fee scams such as "processing" or "insurance" charges for a loan that never arrives. The page carried the title "Bot Verification", a generic challenge screen, while our classification is banking impersonation phishing.

Evidence

On 2026-10-02, 10 of 91 VirusTotal engines flagged the domain. The vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Lionic, alphaMountain.ai and Bfore.Ai PreCrime. That is a modest share of engines, but it spans established antivirus vendors and predictive scoring services. urlscan.io returned a malicious verdict and tied the page to banking imagery. Spamhaus lists the domain in its DBL as spam, and it appears in two AlienVault OTX threat pulses alongside the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2025-10-16 through HOSTINGER operations, UAB. That is almost a full year before it surfaced as phishing, so this was not a throwaway name spun up the same day. It is hosted on the FranTech Solutions network in Luxembourg. The registration lead time suggests the operators let the name age before putting the lure into use.

What to do

If you entered banking credentials on this site, change that password immediately from your bank's official app or website and turn on two-factor authentication. Call your bank's fraud line if you shared card details or saw unfamiliar activity. If you submitted ID documents or applied for a "loan", watch for identity misuse and refuse any request to pay fees up front for credit approval. Security teams should block the domain at DNS and proxy level and search mail logs for messages pointing to it. Report related lookalike lending domains to PhishDestroy.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

保存済みキャプチャ · 3 captures

Domain details

ドメイン
URLScan verdict 悪意あり score 100 Phishing report ↗
IPレピュテーション abuse score 16/100 3 reports Email SpamPort ScanBrute-Force checked 2026年10月1日
OTX tags activeblocklistcontentcryptodrainerfraudphishdestroyphishingscam
レジストラ Hostinger (Unknown)
不正利用連絡先abuse-tracker@hostinger.com
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2025年10月16日 — Expires 2026年10月16日
技術詳細Provenance & timestamps
初確認2026年10月1日
DOM Analysisanalyzed 2026年10月9日score 93/1003 brand signals
Submitted URLhttps://royalscreditcapital.com/
Favicon Hash
ケース ID
Observed page title
Bot Verification
Automated brand references
Across Google Revolut
TLS証明書
発行者 Let's Encrypt / YR1 · stored validity ends in 65 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
198.251.84.200
Network ASN
AS53667
Organization
FranTech Solutions
Observed location
Luxembourg, LU
Server header
LiteSpeed

ネームサーバー 4

  • ns5.asurahosting.com
  • ns5.my-control-panel.com
  • ns6.asurahosting.com
  • ns6.my-control-panel.com

Mail routing 1 MX record

  • royalscreditcapital.compriority 0

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YR1
Valid from
2026-09-25 18:50:25
Valid until
2026-12-24 18:50:24
Validity
Within stored validity dates
Collection time
2026-10-20 07:02:24 UTC
Collection source
PhishDestroy collector
Certificate fingerprint15103431729cd98a650dc335c344ac8e875a1abb2e2a81fff6f6a5f3bca75c3c

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-20 08:21:37 UTC

Primary outcome DNS 非アクティブ reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 不明 Probe Inconclusive 20% 2026-10-20 10:06:45 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-09 10:08:14 UTC current episode first observed: 2026-10-09 20:20:42 UTC observed RIP window: 2026-10-09 10:08:14 UTC → 2026-10-09 20:20:42 UTC · 10.21h midpoint estimate ≈ 2026-10-09 15:14:28 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.royalscreditcapital.comDomain record

The original observation time is not recorded for these hostnames.

このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

10 / 91 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Lionic
ネットクラフト
ソフォス

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of royalscreditcapital.com · checked Oct 1, 2026

91
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.51s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
255ms
Total Blocking Time
SI
5.25s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
10.21
Estimate basis
Bounded by observations
Estimate precision
中

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

Stored observation history20

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

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

Earlier observations 15
  1. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    protected→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  8. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  9. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  10. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  11. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  12. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  13. VirusTotal · Detection count

    9→10

  14. Availability monitor · Recorded state

    不明→protected

    captcha · challenge

  15. Availability monitor · First collection record

    到達可能

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    2 community references

    View source
  3. VirusTotal

    10/91 engine detections

    View source
  4. Abuse report sent

    PD-20261001-0648E9

    abuse-tracker@hostinger.com
  5. Added to PhishDestroy

    royalscreditcapital.com

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

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

royalscreditcapital.com

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20261001-0648E9 Recipient: abuse-tracker@hostinger.com
Page title stored with report: Bot Verification
PDF notice generated
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

6 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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 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およびドメイン 詐欺師が使用した(以下を含む) royalscreditcapital.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やWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — 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/ja/embed/domain/royalscreditcapital.com"
  title="PhishDestroy threat report for royalscreditcapital.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>