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

febagye.com

In short

febagye.com is a phishing page detected by PhishDestroy on 2026-10-26.

Registrar
NameCheap
Resolved IP
188.114.96.1
Registered
May 5, 2026
PhishDestroy assessment Critical
95/100
Evidence score
First observed Oct 26, 2026 20:41 UTC · PhishDestroy
VirusTotal detections: 16/92
VirusTotal
engine detections ·
OTX
community references
Page captures
open gallery
Domain age
OTX: 1 ref Oct 26, 2026 CDN
X Telegram API

Analysis

Domain summary

febagye.com is a phishing page detected by PhishDestroy on 2026-10-26. Risk: critical (95/100). Registrar: NameCheap. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
16 / 92
OTX
1 community ref
Page captures
4

PhishDestroy threat report

Overview

PhishDestroy added febagye.com to its internal blocklist on 2026-10-26 after an intake flagged it because VirusTotal reported multiple malicious detections. A fetch of the site on 2026-10-26 returned HTTP status 520, indicating no page content was delivered.

How the scam works

Because the domain is flagged by many security engines as malicious or phishing, it could be used for typical web‑based threats such as credential harvesting, malware delivery, or command‑and‑control, but no concrete payload or form was observed on the captured page.

Evidence

VirusTotal analysis on 2026-10-26 recorded 13 malicious and 3 suspicious detections from 92 engines, with vendors including BitDefender, Fortinet and G‑Data labeling it phishing or malicious. Google Safe Browsing checked on 2026-10-26 did not flag the domain. Cloudflare Radar scan on 2026-10-26 returned a malicious verdict and categorized it as malware. urlscan.io captured a snapshot on 2026-09-02; its automated engine gave a malicious score of 70, though the overall verdict was clean. OTX listed one pulse referencing the domain as of 2026-10-26. PhishDestroy’s internal blocklist includes the domain, while external blocklists checked on 2026-10-26 reported none.

Infrastructure

The domain was registered on 2026-05-05 through NameCheap, Inc., and the registration remained active until its expiration on 2027-05-05. DNS records observed on 2026-10-26 showed Cloudflare nameservers dayana.ns.cloudflare.com and sonny.ns.cloudflare.com, and A records pointing to 188.114.96.0 and 188.114.97.0 (with corresponding AAAA records); DNSSEC was unsigned at that time.

What to do

Visitors should avoid entering any credentials or downloading files from febagye.com; if they did submit login information, they should change the associated passwords and enable two‑factor authentication. Network defenders can add the exact domain to blocklists, monitor DNS queries for it, and review logs for any connections to the recorded IP addresses.

Source evidenceVirusTotal 16 / 92 · OTX 1 references 7 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
13
Suspicious
3
Undetected
33

Vendor labels

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

Reputation score

0

Tags

  • dga

Registrar

NAMECHEAP INC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    dayana.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.10.138
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::ac43:be36
  • TTL, seconds
    21600
    Type
    NS
    Value
    sonny.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.190.54
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::6815:a8a
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    dayana.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.febagye.com
  • febagye.com
Issuer
Let's Encrypt / YE2
Serial
54e65321aac59f313ba8bd71149d67c5d39
SHA-256
1148fbd5a08b48c853f954cf513c91c603930aadc9e44c028555897cccb5e967
Subject
febagye.com
Valid until
Valid from

Registration record

Registrar
NAMECHEAP INC
Registrar IANA ID
1068
Registrar URL
http://www.namecheap.com
Registered
Updated
1-01-01T00:00:00Z
Expires
Status
  • clientTransferProhibited
Nameservers
  • dayana.ns.cloudflare.com
  • sonny.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 33
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
NAMECHEAP INC
Created
2026-05-05T08:11:45Z
Expires
2027-05-05T08:11:45Z
Updated
2026-05-05T18:48:24Z
First seen
2026-05-05T19:15:00Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "dayana.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.10.138"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:be36"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sonny.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.190.54"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:a8a"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "dayana.ns.cloudflare.com"
    }
]
Dns at
2026-10-17T11:48:52Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.febagye.com",
        "febagye.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "54e65321aac59f313ba8bd71149d67c5d39",
    "sha256": "1148fbd5a08b48c853f954cf513c91c603930aadc9e44c028555897cccb5e967",
    "subject": "febagye.com",
    "valid_to": "2026-11-29T21:26:13Z",
    "valid_from": "2026-08-31T21:26:14Z"
}
Registration record
{
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068",
    "registrar_url": "http://www.namecheap.com",
    "created": "2026-05-05T08:11:45Z",
    "updated": "1-01-01T00:00:00Z",
    "expires": "2027-05-05T08:11:45Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dayana.ns.cloudflare.com",
        "sonny.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "registration": "2026-05-05T08:11:45Z",
        "registrar expiration": "2027-05-05T08:11:45Z",
        "last update of RDAP database": "2026-10-17T11:48:52Z"
    }
}
Separate source record · 13 malicious + 3 suspicious / 92 · 2026-10-17 11:43:36 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-17T11:43:36Z
fetched_at
2026-10-26T20:43:38Z
stats
{"timeout":0,"harmless":43,"malicious":13,"suspicious":3,"undetected":33}

URLScan

Malicious · engine verdict · score 70

Open report
URLScanOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Report ID

01a06230-af8c-71f8-ba6b-0b24b61f9c29

Final URL

https://febagye.com/

HTTP response

522

IP address

188.114.96.3

Contacted IP addresses

  • 188.114.96.3

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com
  • developers.cloudflare.com

Document hash

427c64e2b865c1c7d6f952dec293ef769aa8660ba7781e62fcb0192aaf16b4d2

TLS session and certificate

Subject alternative names
  • *.febagye.com
  • febagye.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
febagye.com
Protocol
QUIC
Valid until
Valid from

Domain age, days

119

Registered domain age, days

119

Certificate age, days

1

Certificate validity, days

89

Page requests

8

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
70
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
01a06230-af8c-71f8-ba6b-0b24b61f9c29
Final url
https://febagye.com/
Status
522
Ip
188.114.96.3
Contacted IP addresses
[
    "188.114.96.3"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com",
    "developers.cloudflare.com"
]
Document hash
427c64e2b865c1c7d6f952dec293ef769aa8660ba7781e62fcb0192aaf16b4d2
Tls
{
    "san": [
        "*.febagye.com",
        "febagye.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "febagye.com",
    "protocol": "QUIC",
    "valid_to": "2026-11-29T21:26:13Z",
    "valid_from": "2026-08-31T21:26:14Z"
}
Domain age days
119
Apex age days
119
Tls age days
1
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 70,
        "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
01a06230-af8c-71f8-ba6b-0b24b61f9c29
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

1 community reference

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

de305d1b-e087-4588-a2c2-98829a11b5cc

Final URL

https://febagye.com/

HTTP response

520

Navigation history

  • URL
    https://febagye.com/
    Status
    520

DOM structure hash

44f83b86670a53701e60f71195a3f41260783e3e1297f0ec6a48f6f4d16a372e

Document hash

47f8e19de5557eb59dc2b8bf13fdc7f62af6ba6a6307bc7680c403a474aceede

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    febagye.com
    Type
    A
    Value
    188.114.96.0
  • Name
    febagye.com
    Type
    A
    Value
    188.114.97.0
  • Name
    febagye.com
    Type
    AAAA
    Value
    2a06:98c1:3120::
  • Name
    febagye.com
    Type
    AAAA
    Value
    2a06:98c1:3121::

DNSSEC valid

No

IP address

188.114.96.0

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
NameCheap, Inc.
Registered
Updated
Expires
Nameservers
  • dayana.ns.cloudflare.com
  • sonny.ns.cloudflare.com
Original source fields · JSON
Uuid
de305d1b-e087-4588-a2c2-98829a11b5cc
Final url
https://febagye.com/
Status
520
History
[
    {
        "url": "https://febagye.com/",
        "status": 520
    }
]
DOM structure hash
44f83b86670a53701e60f71195a3f41260783e3e1297f0ec6a48f6f4d16a372e
Document hash
47f8e19de5557eb59dc2b8bf13fdc7f62af6ba6a6307bc7680c403a474aceede
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "febagye.com",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "febagye.com",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "febagye.com",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "febagye.com",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2026-05-05T08:11:45Z",
    "updated": "2026-05-05T18:48:24Z",
    "expires": "2027-05-05T08:11:45Z",
    "nameservers": [
        "dayana.ns.cloudflare.com",
        "sonny.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:00:57Z

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:00:57Z
source_timestamp
2026-10-26 22:00:57
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
febagye.com — Suspicious Domain
ai_description
PhishDestroy lists febagye.com as a suspicious domain after multiple security vendors flagged it as malicious, with VirusTotal and Cloudflare Radar detections.
ai_generated_at
2026-10-26T20:50:05Z
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: 6 fields

Mail configuration

SPF lookups
0

CAA records

Domain
febagye.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

DNS servers

Nameservers
  • IP address
    162.159.44.66
    Host
    sonny.ns.cloudflare.com
  • IP address
    172.64.34.103
    Host
    dayana.ns.cloudflare.com
DNS zone
febagye.com

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • sonny.ns.cloudflare.com
  • dayana.ns.cloudflare.com
SOA
Primary nameserver
dayana.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2415940507
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

Technology stack

Technologies
  • Cloudflare
  • HTTP/3
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "febagye.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.66",
            "host": "sonny.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.103",
            "host": "dayana.ns.cloudflare.com"
        }
    ],
    "zone": "febagye.com"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "NS": [
        "sonny.ns.cloudflare.com",
        "dayana.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"dayana.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415940507, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "HTTP/3"
    ]
}

Questions about febagye.com

Is febagye.com legit?

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

Is febagye.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on febagye.com. 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 febagye.com?

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

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)
febagye.com: caution — 16/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card febagye.com: caution — 16/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v aa2c88912211

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
RegistrationCreated May 5, 2026 (174d) — Expires May 5, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant3b5f76ecd769308f93fd36a51f72e294s@withheldforprivacy.com VirusTotal WHOIS
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 0/100
Submitted URLhttp://febagye.com/
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 34 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.1
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dayana.ns.cloudflare.com
  • sonny.ns.cloudflare.com

SOA

  • nsname: dayana.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2415940507
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-08-31 21:26:14
Valid until
2026-11-29 21:26:13
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1148fbd5a08b48c853f954cf513c91c603930aadc9e44c028555897cccb5e967
Certificate names · 2 SANs
  • *.febagye.com
  • febagye.com

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of febagye.com · checked Oct 26, 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
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 520
Requested URL: http://febagye.com/
febagye.com | 520: Web server is returning an unknown error
Response
HTTP 520
HTML body
7.2 KB
Compressed
2.1 KB
Links
4 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
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 · 12
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
a50c4859896ddcbe-FRA
Connection
keep-alive
Content-Length
7325
Content-Type
text/html; charset=UTF-8
Date
Mon, 26 Oct 2026 20:41:34 GMT
Expires
Thu, 01 Jan 1970 00:00:01 GMT
Referrer-Policy
same-origin
Retry-After
60
Server
cloudflare
X-Frame-Options
SAMEORIGIN

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

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: 9. 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
    febagye.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 70
  • 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: 16/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • 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

4 entries
  1. AlienVault OTX

    1 community references

    View source
  2. VirusTotal

    16/92 engine detections

    View source
  3. Added to PhishDestroy

    febagye.com

    View source
  4. URLScan

    Malicious · engine verdict · score 70

    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.

Check for cloaking

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

febagye.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

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

Official reporting routes

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.

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 febagye.com)
  • 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

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.

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/febagye.com"
  title="PhishDestroy threat report for febagye.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>