Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
gstionubii247-production.up.railway.app favicon

gstionubii247-production.up.railway.app

In short

PhishDestroy records the captured Ubii-branded login page at gstionubii247-production.up.railway.app, showing its sign-in form and page layout.

“Ubii - Inicia sesión”

Review the evidence
Registrar
Railway
Resolved IP
United States69.46.46.42Railway
Registered
Aug 1, 2019
First observed
Oct 31, 2026
PhishDestroy assessment Critical
85/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 5/92 Stored blocklist matches: 2
VirusTotal
5 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
engine verdict · score 99
Cloudflare Radar
Phishing
Page captures
4
open gallery
Domain age
2,648 days
registered 2019-08-01 according to RDAP · source data differ
Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the captured Ubii-branded login page at gstionubii247-production.up.railway.app, showing its sign-in form and page layout.

Critical
Status
Last known active
VirusTotal
5 / 92
Blocklist matches
2
Hosting
United States69.46.46.42Railway
Registrar
Railway
Registered
Aug 1, 2019
Page captures
4
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page presents a dark-themed sign-in screen branded with the Ubii logo and the Spanish heading "Inicia sesión." It offers two fields, one for a username or email and one for a password, followed by a blue "Ingresar" button; a password-recovery link sits below the fields, while a "Registrarme" button and a contact link appear near the bottom of the page.

The stored VirusTotal domain result reports 5 detections out of 92 engines. VIPRE reported "malware"; Kaspersky reported "phishing".

Source evidenceVirusTotal 5 / 92 8 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
5
Suspicious
0
Undetected
34

Vendor labels

VIPRE
malware
Kaspersky
phishing
LevelBlue
phishing
ChainPatrol
malicious
alphaMountain.ai
malicious

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Information Technology, Malicious (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    60
    Type
    A
    Value
    69.46.46.42

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041dba951fb796b4b956c9799ba19149e94a

Certificate

Subject alternative names
  • *.up.railway.app
  • up.railway.app
Issuer
Let's Encrypt / YE2
Serial
618edc56941aa1165ddb080bf9f799eb7c1
SHA-256
fb370ca26842da2b2ff8e3182e0e8cfc6fb8eac32cdb5718f45a4b39b9e140af
Subject
*.up.railway.app
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 5,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "VIPRE": "malware",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "ChainPatrol": "malicious",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Information Technology, Malicious (alphaMountain.ai)"
}
First seen
2026-10-31T09:50:44Z
DNS records
[
    {
        "ttl": 60,
        "type": "A",
        "value": "69.46.46.42"
    }
]
Dns at
2026-10-31T09:57:37Z
Jarm
27d40d40d00040d00042d43d00041dba951fb796b4b956c9799ba19149e94a
Certificate
{
    "san": [
        "*.up.railway.app",
        "up.railway.app"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "618edc56941aa1165ddb080bf9f799eb7c1",
    "sha256": "fb370ca26842da2b2ff8e3182e0e8cfc6fb8eac32cdb5718f45a4b39b9e140af",
    "subject": "*.up.railway.app",
    "valid_to": "2026-12-26T03:01:42Z",
    "valid_from": "2026-09-27T03:01:43Z"
}
Separate source record · 5 malicious + 0 suspicious / 92 · 2026-10-31 09:09:59 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-31T09:09:59Z
fetched_at
2026-10-31T22:35:11Z
stats
{"timeout":0,"harmless":53,"malicious":5,"suspicious":0,"undetected":34}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

84c80816-bde5-4bd6-9912-9006b1fed8f0

Final URL

https://gstionubii247-production.up.railway.app/

HTTP response

200

Navigation history

  • URL
    https://gstionubii247-production.up.railway.app/
    Status
    200

DOM structure hash

705b33d52a097abbd6bbea87ec55ced28152a03907e0c80559ed59f7b5a50694

Document hash

9c83764a861ca6ce881a37940300eebef44df3c0909e4184f0cb16ccb4849324

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    gstionubii247-production.up.railway.app
    Type
    A
    Value
    69.46.46.42

DNSSEC valid

No

IP address

127.0.1.4

127.0.1.4 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing
Original source fields · JSON
Uuid
84c80816-bde5-4bd6-9912-9006b1fed8f0
Final url
https://gstionubii247-production.up.railway.app/
Status
200
History
[
    {
        "url": "https://gstionubii247-production.up.railway.app/",
        "status": 200
    }
]
DOM structure hash
705b33d52a097abbd6bbea87ec55ced28152a03907e0c80559ed59f7b5a50694
Document hash
9c83764a861ca6ce881a37940300eebef44df3c0909e4184f0cb16ccb4849324
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "gstionubii247-production.up.railway.app",
        "type": "A",
        "value": "69.46.46.42"
    }
]
Dnssec valid
false
Ip
127.0.1.4

127.0.1.4 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}

URLScan

Malicious · engine verdict · score 99

SHA-256 9c83764a861ca6ce881a37940300eebef44df3c0909e4184f0cb16ccb4849324

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a19413-d63e-724f-a458-9e8bf847eea4

Final URL

https://gstionubii247-production.up.railway.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://gstionubii247-production.up.railway.app/
    From
    http://gstionubii247-production.up.railway.app/
    Status
    307

IP address

69.46.46.42

Contacted IP addresses

  • 69.46.46.42

Autonomous systems (ASN)

  • 400940

Server countries

  • US

Document hash

9c83764a861ca6ce881a37940300eebef44df3c0909e4184f0cb16ccb4849324

TLS session and certificate

Subject alternative names
  • *.up.railway.app
  • up.railway.app
Cipher
AES_128_GCM
Issuer
YE2
Subject
*.up.railway.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Differs from the registration date in RDAP (2019-08-01), which gives 2648 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

0

Differs from the registration date in RDAP (2019-08-01), which gives 2648 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

34

Certificate validity, days

89

Page requests

3

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
railway-hikari
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.4.27
Original source fields · JSON
Uuid
01a19413-d63e-724f-a458-9e8bf847eea4
Final url
https://gstionubii247-production.up.railway.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://gstionubii247-production.up.railway.app/",
        "from": "http://gstionubii247-production.up.railway.app/",
        "status": 307
    }
]
Ip
69.46.46.42
Contacted IP addresses
[
    "69.46.46.42"
]
Asns
[
    "400940"
]
Countries
[
    "US"
]
Document hash
9c83764a861ca6ce881a37940300eebef44df3c0909e4184f0cb16ccb4849324
Tls
{
    "san": [
        "*.up.railway.app",
        "up.railway.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "*.up.railway.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-26T03:01:42Z",
    "valid_from": "2026-09-27T03:01:43Z"
}
Domain age days
0

Differs from the registration date in RDAP (2019-08-01), which gives 2648 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
0

Differs from the registration date in RDAP (2019-08-01), which gives 2648 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
34
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "railway-hikari",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.4.27"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a19413-d63e-724f-a458-9e8bf847eea4
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-31T22:47:05Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-31T22:47:05Z
source_timestamp
2026-10-31 23:47:05
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
gstionubii247-production.up.railway.app Ubii login page capture
ai_description
PhishDestroy records the captured Ubii-branded login page at gstionubii247-production.up.railway.app, showing its sign-in form and page layout.
ai_summary
The captured page presents a dark-themed sign-in screen branded with the Ubii logo and the Spanish heading "Inicia sesión." It offers two fields, one for a username or email and one for a password, followed by a blue "Ingresar" button; a password-recovery link sits below the fields, while a "Registrarme" button and a contact link appear near the bottom of the page. The stored VirusTotal domain result reports 5 detections out of 92 engines. VIPRE reported "malware"; Kaspersky reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 23:37:51
revision
c5dfab391f82fd79e930cb1fc4d817df1fcc89c47673d32dffbe053667c14891
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 20 fields

CAA records

Count
11
Domain
railway.app
Allowed issuers
  • pki.goog; cansignhttpexchanges=yes
  • ssl.com
  • comodoca.com
  • digicert.com; cansignhttpexchanges=yes
  • letsencrypt.org
  • certainly.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
Ubii - Inicia sesión

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
137
TLS
20
Waiting
104
Connection
12
Download
0
Response time, ms
273

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
3658
CO₂, grams
0.0001
Cleaner than, %
94

DNS servers

Nameservers
  • IP address
    172.64.40.31
    Host
    blue.foundationdns.net
  • IP address
    108.162.198.61
    Host
    blue.foundationdns.org
  • IP address
    162.159.60.1
    Host
    blue.foundationdns.com
DNS zone
railway.app

Location

IP address
69.46.46.42
ASN
400940
Organization
Railway
City
Seattle
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
*.up.railway.app

DNS records

A
  • 69.46.46.42

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
69.46.46.42
IP version
4

Redirects

Redirect chain
  • https://gstionubii247-production.up.railway.app

Page links

Internal links
1

HTTP headers

Response headers
Server
railway-hikari
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.4.27
Original source fields · JSON
Caa records
{
    "count": 11,
    "domain": "railway.app",
    "issuers": [
        "pki.goog; cansignhttpexchanges=yes",
        "ssl.com",
        "comodoca.com",
        "digicert.com; cansignhttpexchanges=yes",
        "letsencrypt.org",
        "certainly.com"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "title": "Ubii - Inicia sesión"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 137,
        "tls": 20,
        "wait": 104,
        "connect": 12,
        "download": 0
    },
    "response_ms": 273
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 3658,
    "co2_grams": 0.0001,
    "cleaner_than": 94
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.40.31",
            "host": "blue.foundationdns.net"
        },
        {
            "ip": "108.162.198.61",
            "host": "blue.foundationdns.org"
        },
        {
            "ip": "162.159.60.1",
            "host": "blue.foundationdns.com"
        }
    ],
    "zone": "railway.app"
}
Location
{
    "ip": "69.46.46.42",
    "asn": "400940",
    "org": "Railway",
    "city": "Seattle",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "*.up.railway.app"
}
DNS records
{
    "A": [
        "69.46.46.42"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "69.46.46.42",
    "family": 4
}
Redirects
{
    "chain": [
        "https://gstionubii247-production.up.railway.app"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "railway-hikari",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "PHP/8.4.27"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about gstionubii247-production.up.railway.app

Is gstionubii247-production.up.railway.app legit?

PhishDestroy records the captured Ubii-branded login page at gstionubii247-production.up.railway.app, showing its sign-in form and page layout.

Is gstionubii247-production.up.railway.app safe to connect a wallet?

This report does not record which wallet requests gstionubii247-production.up.railway.app makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used gstionubii247-production.up.railway.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 4 captures

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: bed2ac363324e9dd0aa74e12d6101e111cb502d9df7e0e4e879097259a45824e SHA-256 of the prepared copy given to the model: 21186c7799b2882beb1f64ba913a2c225f09c1a4f9557842821a179151d61e95
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://gstionubii247-production.up.railway.app/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)
Observed page title
Ubii - Inicia sesión
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 55 days

Domain details

Domain
IP Reputation United States69.46.46.42 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar (base domain) Railway
Abuse contactabuse@railway.app
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for railway.app →
Hosting abuse contact abuse@railway.app Railway · AS400940
Registration (base domain)railway.app · Created Aug 1, 2019
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://gstionubii247-production.up.railway.app/
Favicon Hash
ICANN OVERSIGHT Registration: railway.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain railway.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States69.46.46.42
Network ASN
AS400940
Organization
Railway
Observed location
United StatesSeattle, US
Server header
railway-hikari

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-27 03:01:43
Valid until
2026-12-26 03:01:42
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintfb370ca26842da2b2ff8e3182e0e8cfc6fb8eac32cdb5718f45a4b39b9e140af
Certificate names · 2 SANs
  • *.up.railway.app
  • up.railway.app

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

viewdns.info · 69.46.46.42rapiddns.io
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
ChainPatrol
alphaMountain.ai
Kaspersky
LevelBlue
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of gstionubii247-production.up.railway.app · checked Oct 31, 2026

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

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 3 SHA-256 hashes: 3 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-10-31 22:34 UTC.

Open this scan on URLScan 01a19413-d63e-724f-a458-9e8bf847eea4 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:29:31.000000
    Evidence SHA-256
    5aa3bf7427627b70d3d50337ec4ff899fb3bd43aa42891ce8242df81c4f2543c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:29:31
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:29:31.000000
    Evidence SHA-256
    5aa3bf7427627b70d3d50337ec4ff899fb3bd43aa42891ce8242df81c4f2543c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:29:31
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    gstionubii247-production.up.railway.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 5/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Phishing, Security threats
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Added to PhishDestroy

    gstionubii247-production.up.railway.app

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    5/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

gstionubii247-production.up.railway.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including gstionubii247-production.up.railway.app)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/gstionubii247-production.up.railway.app"
  title="PhishDestroy threat report for gstionubii247-production.up.railway.app"
  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>