Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
jrqwoukapy.1st-assylum.org favicon

jrqwoukapy.1st-assylum.org

In short

PhishDestroy records that jrqwoukapy.1st-assylum.org shows an access-denied message while claiming to verify permissions for a shared document.

“DOCUSIGN”

Review the evidence
Registrar
United StatesCloudflare
Resolved IP
Canada104.21.10.25Cloudflare, Inc. · CDN
Registered
Oct 3, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 15/92 Young domain: 28 days old
VirusTotal
15 / 92
engine detections ·
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
9
open gallery
Domain age
28 days
registered 2026-10-03 according to WHOIS
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that jrqwoukapy.1st-assylum.org shows an access-denied message while claiming to verify permissions for a shared document.

Critical
Status
Last known active
VirusTotal
15 / 92
Hosting
Canada104.21.10.25Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Registered
Oct 3, 2026
Page captures
9
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page on jrqwoukapy.1st-assylum.org presents a single centered card headed "Opening Shared Document" with the line "Verifying access permissions for your account..." beneath it. Below that, red text reads "Access denied. Please try again from a supported browser." The page offers no form or other control in this capture, so the only visible interaction is the blocked attempt to open the shared document it describes.

The stored VirusTotal domain result reports 15 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 15 / 92 7 sources

VirusTotal

15 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
12
Suspicious
3
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
URLQuery
suspicious
Kaspersky
phishing
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
suspicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Suspicious (alphaMountain.ai)

Registrar

Cloudflare, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.67.162.36
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::6815:a19
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.10.25
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::ac43:a224

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.1st-assylum.org
  • 1st-assylum.org
Issuer
Let's Encrypt / YE1
Serial
6d2432e29754ffa05f9ba48f0e980dc5a1b
SHA-256
242a9effd202f46624df796b7c3b41797e5396189ca209fea798e07c240be2ad
Subject
1st-assylum.org
Valid until
Valid from

Registration record

Registrar
Cloudflare, Inc.
Registrar IANA ID
1910
Registrar URL
http://www.cloudflare.com
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
Nameservers
  • josh.ns.cloudflare.com
  • nova.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 12,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "URLQuery": "suspicious",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "suspicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Suspicious (alphaMountain.ai)"
}
Registrar
Cloudflare, Inc.
Created
2026-10-03T14:42:11Z
Expires
2027-10-03T14:42:11Z
Updated
2026-10-03T14:42:12Z
First seen
2026-10-29T14:50:03Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.162.36"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:a19"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.10.25"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:a224"
    }
]
Dns at
2026-10-31T16:52:32Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.1st-assylum.org",
        "1st-assylum.org"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6d2432e29754ffa05f9ba48f0e980dc5a1b",
    "sha256": "242a9effd202f46624df796b7c3b41797e5396189ca209fea798e07c240be2ad",
    "subject": "1st-assylum.org",
    "valid_to": "2027-01-01T13:52:36Z",
    "valid_from": "2026-10-03T13:52:37Z"
}
Registration record
{
    "registrar": "Cloudflare, Inc.",
    "registrar_iana_id": "1910",
    "registrar_url": "http://www.cloudflare.com",
    "created": "2026-10-03T14:42:11Z",
    "updated": "2026-10-03T14:42:12Z",
    "expires": "2027-10-03T14:42:11Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "josh.ns.cloudflare.com",
        "nova.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 12 malicious + 3 suspicious / 92 · 2026-10-31 16:52:16 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-31T16:52:16Z
fetched_at
2026-10-31T21:58:27Z
stats
{"timeout":0,"harmless":45,"malicious":12,"suspicious":3,"undetected":32}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

07ab509a-2eee-4987-91ee-0db7a076302f

Final URL

https://jrqwoukapy.1st-assylum.org/

HTTP response

200

Navigation history

  • URL
    https://jrqwoukapy.1st-assylum.org/
    Status
    200

DOM structure hash

85d8fefd8498d5d5e5901ccfbcddfbbd66ebe383388ae46a3a8a9c2d1fae6994

Document hash

5529be4bdb7576cbeab84f80e7ee6a690d8521542b2c13504456d086813a5d0c

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    jrqwoukapy.1st-assylum.org
    Type
    A
    Value
    104.21.10.25
  • Name
    jrqwoukapy.1st-assylum.org
    Type
    A
    Value
    172.67.162.36
  • Name
    jrqwoukapy.1st-assylum.org
    Type
    AAAA
    Value
    2606:4700:3035::ac43:a224
  • Name
    jrqwoukapy.1st-assylum.org
    Type
    AAAA
    Value
    2606:4700:3037::6815:a19

DNSSEC valid

No

IP address

127.0.1.17

127.0.1.17 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

Registration record

Registrar
Cloudflare, Inc.
Registered
Updated
Expires
Nameservers
  • josh.ns.cloudflare.com
  • nova.ns.cloudflare.com
Original source fields · JSON
Uuid
07ab509a-2eee-4987-91ee-0db7a076302f
Final url
https://jrqwoukapy.1st-assylum.org/
Status
200
History
[
    {
        "url": "https://jrqwoukapy.1st-assylum.org/",
        "status": 200
    }
]
DOM structure hash
85d8fefd8498d5d5e5901ccfbcddfbbd66ebe383388ae46a3a8a9c2d1fae6994
Document hash
5529be4bdb7576cbeab84f80e7ee6a690d8521542b2c13504456d086813a5d0c
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "jrqwoukapy.1st-assylum.org",
        "type": "A",
        "value": "104.21.10.25"
    },
    {
        "name": "jrqwoukapy.1st-assylum.org",
        "type": "A",
        "value": "172.67.162.36"
    },
    {
        "name": "jrqwoukapy.1st-assylum.org",
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:a224"
    },
    {
        "name": "jrqwoukapy.1st-assylum.org",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:a19"
    }
]
Dnssec valid
false
Ip
127.0.1.17

127.0.1.17 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"
    ]
}
Registration record
{
    "registrar": "Cloudflare, Inc.",
    "created": "2026-10-03T14:42:11Z",
    "updated": "2026-10-08T14:42:26Z",
    "expires": "2027-10-03T14:42:11Z",
    "nameservers": [
        "josh.ns.cloudflare.com",
        "nova.ns.cloudflare.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious

SHA-256 a75e000219643af3aea532d84e1b5310cd0e21b7f53dc59c563fa7c8f8b7e036

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a190da-8721-702f-b4f2-4ed25be0c402

Final URL

https://jrqwoukapy.1st-assylum.org/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://jrqwoukapy.1st-assylum.org/
    From
    http://jrqwoukapy.1st-assylum.org/
    Status
    307

IP address

172.67.162.36

Contacted IP addresses

  • 172.67.162.36

Autonomous systems (ASN)

  • 13335

Document hash

a75e000219643af3aea532d84e1b5310cd0e21b7f53dc59c563fa7c8f8b7e036

JavaScript globals

  • boltCleanValue
  • boltReadIncomingValue
  • boltBuildRedirectUrl
  • boltRedirectUrl

Cookies

  • bolt_visitor_id
  • XSRF-TOKEN
  • laravel-session

TLS session and certificate

Subject alternative names
  • *.1st-assylum.org
  • 1st-assylum.org
Cipher
AES_128_GCM
Issuer
YE1
Subject
1st-assylum.org
Protocol
QUIC
Valid until
Valid from

Domain age, days

1

Registered domain age, days

27

Certificate age, days

27

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
84
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • onedrive
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • OneDrive
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a190da-8721-702f-b4f2-4ed25be0c402
Final url
https://jrqwoukapy.1st-assylum.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://jrqwoukapy.1st-assylum.org/",
        "from": "http://jrqwoukapy.1st-assylum.org/",
        "status": 307
    }
]
Ip
172.67.162.36
Contacted IP addresses
[
    "172.67.162.36"
]
Asns
[
    "13335"
]
Document hash
a75e000219643af3aea532d84e1b5310cd0e21b7f53dc59c563fa7c8f8b7e036
Globals
[
    "boltCleanValue",
    "boltReadIncomingValue",
    "boltBuildRedirectUrl",
    "boltRedirectUrl"
]
Cookies
[
    "bolt_visitor_id",
    "XSRF-TOKEN",
    "laravel-session"
]
Tls
{
    "san": [
        "*.1st-assylum.org",
        "1st-assylum.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "1st-assylum.org",
    "protocol": "QUIC",
    "valid_to": "2027-01-01T13:52:36Z",
    "valid_from": "2026-10-03T13:52:37Z"
}
Domain age days
1
Apex age days
27
Tls age days
27
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 84,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "onedrive"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "OneDrive"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
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
01a190da-8721-702f-b4f2-4ed25be0c402
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

PhishDestroy DOM

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

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

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:15:52Z
source_timestamp
2026-10-31 23:15:52
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
jrqwoukapy.1st-assylum.org access denied shared document page
ai_description
PhishDestroy records that jrqwoukapy.1st-assylum.org shows an access-denied message while claiming to verify permissions for a shared document.
ai_summary
The captured page on jrqwoukapy.1st-assylum.org presents a single centered card headed "Opening Shared Document" with the line "Verifying access permissions for your account..." beneath it. Below that, red text reads "Access denied. Please try again from a supported browser." The page offers no form or other control in this capture, so the only visible interaction is the blocked attempt to open the shared document it describes. The stored VirusTotal domain result reports 15 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 22:59:33
revision
e062f15608caa4416e6e0fb695759335caf8509a6a1763f1b67c9aeace708643
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: 24 fields

CAA records

Domain
jrqwoukapy.1st-assylum.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
4976

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
DOCUSIGN

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
13
Waiting
443
Connection
6
Download
0
Response time, ms
464

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
6760
CO₂, grams
0.0002
Cleaner than, %
80

DNS servers

Nameservers
  • IP address
    162.159.38.129
    Host
    nova.ns.cloudflare.com
  • IP address
    172.64.33.126
    Host
    josh.ns.cloudflare.com
DNS zone
1st-assylum.org

Cookies

Cookies
  • Name
    bolt_visitor_id
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    XSRF-TOKEN
    Secure
    Yes
    SameSite
    Lax
  • Name
    laravel-session
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax

Location

IP address
2606:4700:3035::ac43:a224
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
1st-assylum.org

DNS records

A
  • 104.21.10.25
  • 172.67.162.36
AAAA
  • 2606:4700:3035::ac43:a224
  • 2606:4700:3037::6815:a19

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3037::6815:a19
IP version
6

Redirects

Redirect chain
  • https://jrqwoukapy.1st-assylum.org

Registration record

Registrar
Cloudflare, Inc.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • josh.ns.cloudflare.com
  • nova.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Caa records
{
    "domain": "jrqwoukapy.1st-assylum.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T21:58:11Z",
    "first": "2026-10-31T21:58:11Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4976
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "DOCUSIGN"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 13,
        "wait": 443,
        "connect": 6,
        "download": 0
    },
    "response_ms": 464
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 6760,
    "co2_grams": 0.0002,
    "cleaner_than": 80
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.38.129",
            "host": "nova.ns.cloudflare.com"
        },
        {
            "ip": "172.64.33.126",
            "host": "josh.ns.cloudflare.com"
        }
    ],
    "zone": "1st-assylum.org"
}
Cookies
{
    "cookies": [
        {
            "name": "bolt_visitor_id",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "XSRF-TOKEN",
            "secure": true,
            "same_site": "Lax"
        },
        {
            "name": "laravel-session",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "2606:4700:3035::ac43:a224",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "1st-assylum.org"
}
DNS records
{
    "A": [
        "104.21.10.25",
        "172.67.162.36"
    ],
    "AAAA": [
        "2606:4700:3035::ac43:a224",
        "2606:4700:3037::6815:a19"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3037::6815:a19",
    "family": 6
}
Redirects
{
    "chain": [
        "https://jrqwoukapy.1st-assylum.org"
    ]
}
Registration record
{
    "registrar": "Cloudflare, Inc.",
    "created": "2026-10-03T14:42:11Z",
    "updated": "2026-10-08T14:42:26Z",
    "expires": "2027-10-03T14:42:11Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "josh.ns.cloudflare.com",
        "nova.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about jrqwoukapy.1st-assylum.org

Is jrqwoukapy.1st-assylum.org legit?

PhishDestroy records that jrqwoukapy.1st-assylum.org shows an access-denied message while claiming to verify permissions for a shared document.

Is jrqwoukapy.1st-assylum.org safe to connect a wallet?

This report does not record which wallet requests jrqwoukapy.1st-assylum.org 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 jrqwoukapy.1st-assylum.org?

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 matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 9 captures

Cloudflare Radar 1 / 9 Used in the analysis Source file SHA-256: bd1292f509bed4e443d4a8be21fa845a09288be8a420744a5e1a0d18c0c4e91a SHA-256 of the prepared copy given to the model: be368ee3bd06e9e6e89bba7a4219afb70e6fdbc9f3ba0b34662cbfb1690c6b85
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://jrqwoukapy.1st-assylum.org/
Position1 / 9
Open capture Source Report Wayback Download
All capture links and hashes (9)

Domain details

Domain
IP Context Canada104.21.10.25 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Cloudflare US(US)
Abuse contact["registry-abuse@cloudflare.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for 1st-assylum.org →
Hosting abuse contact registry-abuse@cloudflare.com Cloudflare, Inc. · AS13335
Registration (base domain)1st-assylum.org · Created Oct 3, 2026 (28d · Very New!) — Expires Oct 3, 2027
WHOIS statusclientTransferProhibited
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://jrqwoukapy.1st-assylum.org/ready-for-review-ibywuv
Observed page title
DOCUSIGN
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 61 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.21.10.25
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • josh.ns.cloudflare.com
  • nova.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-03 13:52:37
Valid until
2027-01-01 13:52:36
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint242a9effd202f46624df796b7c3b41797e5396189ca209fea798e07c240be2ad
Certificate names · 2 SANs
  • *.1st-assylum.org
  • 1st-assylum.org

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

viewdns.info · 104.21.10.25rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
URLQuery
Webroot
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://jrqwoukapy.1st-assylum.org/ready-for-review-ibywuv
Final URL: https://jrqwoukapy.1st-assylum.org/ready-for-review-ibywuv
DOCUSIGN
Response
HTTP 200
HTML body
7.0 KB
Compressed
2.9 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-cache, private
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
Cache-Control
no-cache, private
cf-cache-status
DYNAMIC
CF-RAY
a535eb327a358a15-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 21:58:02 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OrOH9Jnlrjal8ptAHJ4DsofaOIersdqNx3Nr5TRxWY%2Fh7BsbOxDBaXHoPp22RVTO8xYSaSts%2FqQG3okwsaaFnk%2Fb3xRShYcRIijLYyb%2BsFWfknd8%2BqWsvvO%2B6M6Hs0WicTQ
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
accept-encoding

Values retained by the collector; long values may be shortened during collection.

Archived

Captured network requests

Network requests: 2 SHA-256 hashes: 2 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 21:58 UTC.

Open this scan on URLScan 01a190da-8721-702f-b4f2-4ed25be0c402 ↗

All retained availability observations1

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
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 22:59:53.406979
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 8. 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
    jrqwoukapy.1st-assylum.org detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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: 15/92
  • 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

    jrqwoukapy.1st-assylum.org

    View source
  3. VirusTotal

    15/92 engine detections

    View source
  4. URLScan

    Malicious

    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.

jrqwoukapy.1st-assylum.org

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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 jrqwoukapy.1st-assylum.org)
  • 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/jrqwoukapy.1st-assylum.org"
  title="PhishDestroy threat report for jrqwoukapy.1st-assylum.org"
  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>