Gridinsoft
51/100
royalholdingsbk.ltd displays a simulated financial dashboard for Royal Holdings with account overview features. Verify credentials before providing information.
Page title: “Home | Royal Holdings”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
URLScan capture · 2026-11-21 12:06 UTC · SHA-256 025b8406…9916f5e
PhishDestroy analysis, reviewed version
The webpage for royalholdingsbk.ltd displays a polished digital banking interface using the brand name "Royal Holdings Modern banking". The left column features a prominent headline reading "Everyday banking with clarity, control and confidence." and describes a financial workspace for desktop and mobile offering transfers, cards, savings, investing, loans, and account support. Below the text, two primary buttons read "Open an account" and "Explore services", alongside small indicator icons for secure account access, clear transaction records, and responsive design. On the right, a graphical dashboard shows a mock banking interface with an available balance of "$24,860.40" and quick action buttons for transfer, cards, savings, and invest. Additional navigation links across the top include "Home", "About", "Services", "FAQ", "Contact", "Login", and an "Open account" button.
95 other reported domains resolve to the same IP address, including sites such as richaxisholdings.com, bestvalueinves.com and mint-firm.org which present various financial and investment services like "Rich Axis Holdings" and "Best Values Investment | Bitcoin & Cryptocurrency trading Dashboard". Furthermore, its IP address has 15 abuse reports on AbuseIPDB (phishing and bad web bots), pointing to associated operational activity on the host. The domain was registered on 17 Oct 2026 through Sav.com, LLC and it still answered requests on 21 Nov 2026 at 13:07 UTC.
When encountering financial platforms like royalholdingsbk.ltd, users should exercise caution and verify whether the service holds legitimate regulatory licenses in their jurisdiction. Always cross-check the web address against official corporate registries or known contact points provided by established financial institutions. Anyone who has already submitted personal credentials or financial details through this portal should immediately contact their bank, monitor their accounts for unauthorized activity, and change passwords linked to similar accounts.
51/100
Scan report
Open report65/100
Trust score, lower = worse
Open reportPage capture
SHA-256 a87c961c…d3680ee
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
10 / 100 · heuristic score · 1 brand reference · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | MX: royalholdingsbk.ltd; Spf: v=spf1 ip4:159.100.6.5 +a +mx include:relay.mailchannels.net ~all; Dkim: default; Dkim bits: 2048; Spf lookups: 3 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-11-21T12:09:43Z; First: 2026-10-18T00:52:22Z; Changes: 1; Days archived: 2; Scans per day: 0.03; Avg page bytes: 18534 |
| Page title and metadata | Title: One moment, please... |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 23; Download: 0; Response ms: 65 |
| Carbon | Bytes: 12162; Co2 grams: 0.0004; Cleaner than: 68 |
| DNS server | NS: (IP: 51.38.114.43; Host: ns2.ultahost.com), (IP: 149.28.254.81; Host: ns4.ultahost.com), (IP: 167.71.73.238; Host: ns1.ultahost.com), (IP: 94.130.75.18; Host: ns3.ultahost.com); Zone: royalholdingsbk.ltd |
| Quality | Cls: 0; Seo: 100; Si s: 1.66; Fcp s: 1.66; Lcp s: 3.34; Tbt ms: 0; Performance: 91; Accessibility: 90; Best practices: 100 |
| Location | IP: 159.100.6.5; ASN: 214036; Org: Ultahost, Inc.; City: Frankfurt am Main; Country: DE |
| DNS records | A: 159.100.6.5; MX: Exchange: royalholdingsbk.ltd; Priority: 0; NS: ns3.ultahost.com, ns4.ultahost.com, ns1.ultahost.com, ns2.ultahost.com; Soa: Nsname: ns1.ultahost.com; Hostmaster: hosting-notify.ultahost.com; Serial: 2026112102; Refresh: 3600; Retry: 1800; Expire: 1209600; Minttl: 86400; Txt: v=spf1 ip4:159.100.6.5 +a +mx include:relay.mailchannels.net ~all |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: SAMEORIGIN; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: script-src 'nonce-Go8F+LD1JoauiHzUAvLeCA=='; style-src 'nonce-Go8F+LD1JoauiHzUAvLeCA=='; frame-ancestors 'self'; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 159.100.6.5; Family: 4 |
| Redirects | Chain: https://royalholdingsbk.ltd |
| Txt records | Records: v=spf1 ip4:159.100.6.5 +a +mx include:relay.mailchannels.net ~all |
| Subdomains | Count: 9; Subdomains: autoconfig.royalholdingsbk.ltd, autodiscover.royalholdingsbk.ltd, cpanel.royalholdingsbk.ltd, cpcalendars.royalholdingsbk.ltd, cpcontacts.royalholdingsbk.ltd, mail.royalholdingsbk.ltd, webdisk.royalholdingsbk.ltd, webmail.royalholdingsbk.ltd, www.royalholdingsbk.ltd |
| HTTP headers | Headers: Server: openresty/1.31.1.1; Content type: text/html; Content security policy: script-src 'nonce-7/6q91iTridTZrTl5lrsVw=='; style-src 'nonce-7/6q91iTridTZrTl5lrsVw=='; frame-ancestors 'self'; X frame options: SAMEORIGIN; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin |
025b8406…9916f5e SHA-256 of the prepared copy given to the model: e4d57802…326c70d 025b84062d559fd7d3b39ad510b9f9bb9c84717dddd91025884230aad9916f5e · 145191 bytes a4c1dc8b266789c9b14e56b4d0deaa41f29fc56200d9b36f17292a7609cfccd2 · 141296 bytes a4c1dc8b266789c9b14e56b4d0deaa41f29fc56200d9b36f17292a7609cfccd2 · 141296 bytes 46e138db8b61f5f9e6aaa36437b153912e4729da95db5f8780a90b36f59e685a · 34879 bytes For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
ns1.ultahost.comns2.ultahost.comns3.ultahost.comns4.ultahost.comnsname: ns1.ultahost.comhostmaster: hosting-notify.ultahost.comserial: 2026112102refresh: 3600retry: 1800expire: 1209600minttl: 86400royalholdingsbk.ltdpriority 0Location describes the IP network.
5564ece7536377d2614ced3c5d2ff098f683aac5621f9695fc381086a2c59f2dautoconfig.royalholdingsbk.ltdautodiscover.royalholdingsbk.ltdcpanel.royalholdingsbk.ltdcpcalendars.royalholdingsbk.ltdcpcontacts.royalholdingsbk.ltdmail.royalholdingsbk.ltdroyalholdingsbk.ltdwebdisk.royalholdingsbk.ltdwebmail.royalholdingsbk.ltdwww.royalholdingsbk.ltdSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
autoconfig.royalholdingsbk.ltdDomain recordautodiscover.royalholdingsbk.ltdDomain recordcpanel.royalholdingsbk.ltdDomain recordcpcalendars.royalholdingsbk.ltdDomain recordcpcontacts.royalholdingsbk.ltdDomain recordmail.royalholdingsbk.ltdDomain recordwebdisk.royalholdingsbk.ltdDomain recordwebmail.royalholdingsbk.ltdDomain recordwww.royalholdingsbk.ltdDomain recordGoogle PageSpeed Insights — mobile performance audit of royalholdingsbk.ltd ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://royalholdingsbk.ltd/Server: openresty/1.31.1.1Content-Type: text/htmlCache-Control: private, no-cache, no-store, must-revalidate, max-age=0private, no-cache, no-store, must-revalidate, max-age=0no-cachekeep-alive12117script-src 'nonce-yTz3e/+6WtvRpEMrk3MEfA=='; style-src 'nonce-yTz3e/+6WtvRpEMrk3MEfA=='; frame-ancestors 'self'text/htmlSat, 21 Nov 2026 12:08:08 GMTstrict-origin-when-cross-originopenresty/1.31.1.1nosniffSAMEORIGINValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 10 SHA-256 hashes: 10 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-21 12:08 UTC.
Open this scan on URLScan 01a1fe00-5866-753d-8783-ab6bce2dc2f4 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Serving page content
page content returned
Reachable
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 34 d 20 h after registration
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
royalholdingsbk.ltd PD-F0288722792E42E2B8B7 Recipient: abuse-trusted.savcom@in.wixanswers.com Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose 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 ↗
royalholdingsbk.ltd)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.