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

fernand.urge844284.pro

In short

fernand.urge844284.pro is a phishing page detected by PhishDestroy on 2026-10-26.

Review the evidence
Registrar
Dynadot
Resolved IP
188.114.97.1
Registered
May 20, 2026
PhishDestroy assessment Critical
92/100
Evidence score
First observed Oct 26, 2026 20:44 UTC · PhishDestroy
Risk signals
VirusTotal detections: 14/92
VirusTotal
14 / 92
engine detections ·
OTX
0
community references
Page captures
4
open gallery
Domain age
159 days
Oct 26, 2026 CDN
X Telegram API

Analysis

Domain summary

fernand.urge844284.pro is a phishing page detected by PhishDestroy on 2026-10-26. Risk: critical (92/100). Registrar: Dynadot. Hosting: CloudFLARENET-EU. VirusTotal: 14/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
14 / 92
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy classifies fernand.urge844284.pro as a suspicious domain. The domain was first seen by PhishDestroy on 2026-10-26. A page fetch on that date returned HTTP 403 and no page title was recorded.

How the scam works

The detections suggest the site could be used for phishing, where attackers host pages that imitate legitimate services to harvest credentials or other data. Because the captured response was a 403 error, no malicious content or specific phishing page was observed.

Evidence

VirusTotal scanned the domain on 2026-10-24 and reported 12 malicious and 2 suspicious detections out of 92 engines, with vendors such as BitDefender, DNS8 and Fortinet labeling it as phishing. Google Safe Browsing checked on 2026-10-26 and did not flag the domain. urlscan captured a snapshot on 2026-07-30; its automated engine gave a malicious score of 83 and tagged the site as phishing, while the overall verdict was clean. Cloudflare Radar scanned on 2026-10-26 and returned a malicious verdict with a phishing tag; OTX had no pulses as of that date, and external blocklists showed no entries, but PhishDestroy’s internal blocklist contains the domain.

Infrastructure

The domain is 71 days old as of the 2026-10-26 observation and uses a Let’s Encrypt certificate for *.urge844284.pro valid from 2026-09-14 to 2026-12-13. It is served through Cloudflare (ASN 13335, network CloudFLARENET‑EU) with IPv4 address 188.114.97.1 and IPv6 address 2a06:98c1:3120::3, and resolves to additional Cloudflare IPs. DNSSEC is not enabled and the authoritative nameservers are erin.ns.cloudflare.com and ivan.ns.cloudflare.com.

What to do

Do not submit credentials, private keys or personal information to this site; if you have already done so, change any associated passwords and monitor the accounts for unauthorized activity. Defenders should block connections to fernand.urge844284.pro and add the domain to phishing detection lists.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T20:52:46Z)URLScan screenshot (2026-10-26T20:52:00Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 14 / 92 7 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
12
Suspicious
2
Undetected
33

Vendor labels

DNS8
phishing
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
malicious
LevelBlue
suspicious
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.67.176.13
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::ac43:b00d
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.64.49
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::6815:4031

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.urge844284.pro
  • urge844284.pro
Issuer
Let's Encrypt / YE2
Serial
61995b502ba8eb2ccbee7d722f1c0888d0b
SHA-256
950c478cb9ac6671e2b5605793089488616d55a0571d70a455316a453f73aabd
Subject
urge844284.pro
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 12,
    "suspicious": 2,
    "undetected": 33
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "malicious",
    "LevelBlue": "suspicious",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
First seen
2026-05-20T10:27:01Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.176.13"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:b00d"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.64.49"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:4031"
    }
]
Dns at
2026-10-25T06:02:31Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.urge844284.pro",
        "urge844284.pro"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "61995b502ba8eb2ccbee7d722f1c0888d0b",
    "sha256": "950c478cb9ac6671e2b5605793089488616d55a0571d70a455316a453f73aabd",
    "subject": "urge844284.pro",
    "valid_to": "2026-12-13T23:52:21Z",
    "valid_from": "2026-09-14T23:52:22Z"
}
Separate source record · 12 malicious + 2 suspicious / 92 · 2026-10-24 03:43:01 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-24T03:43:01Z
fetched_at
2026-10-26T20:51:12Z
stats
{"timeout":0,"harmless":45,"malicious":12,"suspicious":2,"undetected":33}

URLScan

Malicious · engine verdict · score 83

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

019fb49f-90ae-703c-b227-8d26774056fd

Final URL

https://fernand.urge844284.pro/

HTTP response

403

IP address

2a06:98c1:3120::3

Contacted IP addresses

  • 2a06:98c1:3120::3

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com

Document hash

b5f5cf7a91bc0a384b3bf99257080816f361630956b639a7b89cd3e6336c9301

JavaScript globals

  • _cf_translation

TLS session and certificate

Subject alternative names
  • *.urge844284.pro
  • urge844284.pro
Cipher
AES_128_GCM
Issuer
YE2
Subject
urge844284.pro
Protocol
QUIC
Valid until
Valid from

Domain age, days

71

Registered domain age, days

71

Certificate age, days

12

Certificate validity, days

89

Page requests

5

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
Referrer-policy
same-origin
Original source fields · JSON
Uuid
019fb49f-90ae-703c-b227-8d26774056fd
Final url
https://fernand.urge844284.pro/
Status
403
Ip
2a06:98c1:3120::3
Contacted IP addresses
[
    "2a06:98c1:3120::3"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
b5f5cf7a91bc0a384b3bf99257080816f361630956b639a7b89cd3e6336c9301
Globals
[
    "_cf_translation"
]
Tls
{
    "san": [
        "*.urge844284.pro",
        "urge844284.pro"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "urge844284.pro",
    "protocol": "QUIC",
    "valid_to": "2026-10-16T00:20:09Z",
    "valid_from": "2026-07-18T00:20:10Z"
}
Domain age days
71
Apex age days
71
Tls age days
12
Tls valid days
89
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 83,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN",
    "referrer-policy": "same-origin"
}
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
019fb49f-90ae-703c-b227-8d26774056fd
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

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

13b6f2e2-199b-48c1-b8f1-f511820803a8

Final URL

https://fernand.urge844284.pro/

HTTP response

403

Navigation history

  • URL
    https://fernand.urge844284.pro/
    Status
    403

DOM structure hash

11a3897f82dd5c71e053fdd08f745dfed630a911694965172c89e6f17585f6c3

Document hash

e5fe12981a9e19bb7276831717d67fd8823c187495ff423b688a7541b3dc32a6

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    fernand.urge844284.pro
    Type
    A
    Value
    188.114.97.0
  • Name
    fernand.urge844284.pro
    Type
    A
    Value
    188.114.96.0
  • Name
    fernand.urge844284.pro
    Type
    AAAA
    Value
    2a06:98c1:3120::
  • Name
    fernand.urge844284.pro
    Type
    AAAA
    Value
    2a06:98c1:3121::

DNSSEC valid

No

IP address

188.114.97.0

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • erin.ns.cloudflare.com
  • ivan.ns.cloudflare.com
Original source fields · JSON
Uuid
13b6f2e2-199b-48c1-b8f1-f511820803a8
Final url
https://fernand.urge844284.pro/
Status
403
History
[
    {
        "url": "https://fernand.urge844284.pro/",
        "status": 403
    }
]
DOM structure hash
11a3897f82dd5c71e053fdd08f745dfed630a911694965172c89e6f17585f6c3
Document hash
e5fe12981a9e19bb7276831717d67fd8823c187495ff423b688a7541b3dc32a6
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "fernand.urge844284.pro",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "fernand.urge844284.pro",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "fernand.urge844284.pro",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "fernand.urge844284.pro",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
188.114.97.0
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-05-20T01:45:39Z",
    "updated": "2026-08-12T06:26:02Z",
    "expires": "2027-05-20T01:45:39Z",
    "nameservers": [
        "erin.ns.cloudflare.com",
        "ivan.ns.cloudflare.com"
    ]
}

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-26T21:06:08Z

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-26T21:06:08Z
source_timestamp
2026-10-26 22:06:08
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
fernand.urge844284.pro — Suspicious Domain
ai_description
PhishDestroy flags fernand.urge844284.pro as a suspicious domain after multiple vendor detections and a 403 response, with no malicious page content captured.
ai_generated_at
2026-10-26T20:56:22Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 15 fields

CAA records

Domain
fernand.urge844284.pro

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

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

DNS servers

Nameservers
  • IP address
    173.245.59.120
    Host
    ivan.ns.cloudflare.com
  • IP address
    173.245.58.113
    Host
    erin.ns.cloudflare.com
DNS zone
urge844284.pro

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
urge844284.pro

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
same-origin
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
2a06:98c1:3120::3
IP version
6

Technology stack

Technologies
  • Cloudflare
  • HTTP/3

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
Referrer-policy
same-origin
Original source fields · JSON
Caa records
{
    "domain": "fernand.urge844284.pro"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
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
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.59.120",
            "host": "ivan.ns.cloudflare.com"
        },
        {
            "ip": "173.245.58.113",
            "host": "erin.ns.cloudflare.com"
        }
    ],
    "zone": "urge844284.pro"
}
Location
{
    "ip": "2a06:98c1:3121::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "urge844284.pro"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": "same-origin",
    "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": "2a06:98c1:3120::3",
    "family": 6
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "HTTP/3"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "x-frame-options": "SAMEORIGIN",
        "referrer-policy": "same-origin"
    }
}

Questions about fernand.urge844284.pro

Is fernand.urge844284.pro legit?

No. PhishDestroy classifies fernand.urge844284.pro as a phishing page (risk: critical, 92/100); it was first detected on 2026-10-26. VirusTotal: 14/92 engines flag it. Treat the site as unsafe.

Is fernand.urge844284.pro safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on fernand.urge844284.pro. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used fernand.urge844284.pro?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. 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 · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
HTTP status403
Final URLhttps://fernand.urge844284.pro/
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
fernand.urge844284.pro: caution — 14/92 VirusTotal engines. PhishDestroy risk score 92/100 (critical).
Social preview card fernand.urge844284.pro: caution — 14/92 VirusTotal engines. PhishDestroy risk score 92/100 (critical). v 90db5a68addf

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Dynadot US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for urge844284.pro →
Registration (base domain)urge844284.pro · Created May 20, 2026 (159d) — Expires May 20, 2027
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 0/100
Submitted URLhttp://fernand.urge844284.pro/
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 48 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.1
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • erin.ns.cloudflare.com
  • ivan.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-14 23:52:22
Valid until
2026-12-13 23:52:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint950c478cb9ac6671e2b5605793089488616d55a0571d70a455316a453f73aabd
Certificate names · 2 SANs
  • *.urge844284.pro
  • urge844284.pro

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

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

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed
BitDefender
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of fernand.urge844284.pro · checked Oct 26, 2026

100
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
0.77 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.77 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 403
Requested URL: http://fernand.urge844284.pro/
Attention Required! | Cloudflare
Response
HTTP 403
HTML body
4.8 KB
Compressed
2.0 KB
Links
0 internal · 1 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-Encoding: gzip
Server: cloudflare
Security headers present
X-Frame-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Cache-Control
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
CF-RAY
a50c4e492eacc3b1-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Mon, 26 Oct 2026 20:45:38 GMT
Expires
Thu, 01 Jan 1970 00:00:01 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=0BrnEeqpN%2FcqGzzeAc1iclVvwylOQnx3mlOIdBCRARluzkHuu1c3X0WDNT1NIorbSUS3OUMbHTUda9nRw5yAbI3VgnpUsdhuTz%2BoO%2B3fJL0wAptb9CZM0fU7CWLwTqrApG5HTlfHx
Server
cloudflare
Server-Timing
cfEdge;dur=26,cfOrigin;dur=0
Transfer-Encoding
chunked
X-Frame-Options
SAMEORIGIN

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

Archived
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
    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-26 21:51:02.785322
    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 · recorded

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
    fernand.urge844284.pro 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 machine-learning engines classified the page as malicious · Score: 83
  • 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: 14/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 Recorded: 1 of 1

Recorded activity

3 entries
  1. VirusTotal

    14/92 engine detections

    View source
  2. Added to PhishDestroy

    fernand.urge844284.pro

    View source
  3. URLScan

    Malicious · engine verdict · score 83

    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.

fernand.urge844284.pro

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 14 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 Unverified
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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 fernand.urge844284.pro)
  • 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/fernand.urge844284.pro"
  title="PhishDestroy threat report for fernand.urge844284.pro"
  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>