Domain security and threat intelligence

jeflu.online

Name: jeflu.online — PhishDestroy evidence record
Published: 2026-07-17
License: https://creativecommons.org/licenses/by/4.0/

In short

PhishDestroy first recorded jeflu.online on 2026-07-17. Stored VirusTotal result: 5/91 engines flagged.

Review the evidence

Registrar: Namecheap
Resolved IP: 104.21.32.146Cloudflare, Inc. · CDN
Registered: May 29, 2026
First observed: Jul 17, 2026

PhishDestroy assessment Critical

88/100

Evidence score

Availability Server error The latest stored response was inconclusive Observed Nov 1, 2026 · 02:16 UTCHTTP probe

Risk signals

VirusTotal detections: 5/91

VirusTotal

5 / 91

engine detections

OTX

community references

Page captures

open gallery

Domain age

157 days

registered 2026-05-29 according to RDAP

Analysis

Domain summary

PhishDestroy first recorded jeflu.online on 2026-07-17. Stored VirusTotal result: 5/91 engines flagged. Risk: critical (88/100). Registrar: Namecheap. Status: Server error. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical

Status: Server error
VirusTotal: 5 / 91
Scam type (automated label): Impersonation
Hosting: 104.21.32.146Cloudflare, Inc. · CDN
Registrar: Namecheap
Registered: May 29, 2026
OTX: 4 community refs
Page captures: 3

Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for jeflu.online. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 5 / 91 · OTX 4 references 8 sources

VirusTotal

5 / 91 engine detections

Retrieved / checked: 2026-08-30 04:17:31 · as stored; legacy timezone not established

Open report

URLQuery

Scan report

Open report

OTX

4 community references

2026-10-09 11:58 UTC

Open report

Google Safe Browsing

No threat flag

2026-07-17 09:10 UTC

Open report

URLScan

No malicious flag

2026-07-17 09:09 UTC

Open report

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: 019f6f55-f17d-7648-bf4f-d91811497370
report_url: https://urlscan.io/result/019f6f55-f17d-7648-bf4f-d91811497370/
score: null
malicious: null
result_at: null
enriched_at: 2026-07-20T08:12:50Z
source_timestamps: {"urlscan_result_at":null,"urlscan_enriched_at":"2026-07-20 10:12:50"}
timestamp_basis: Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

2026-09-15 22:30 UTC

Open report

Gridinsoft

No report found

Open report

Stored collection fields

A missing report is not a trust verdict. Legacy zeroes remain in the stored record; the measured trust score is unavailable.

normalized_record: {"trust_score":null,"status":"not_found","signals":[],"report_url":null,"observed_at":null,"rating":null,"review_count":0,"request_url":"https://gridinsoft.com/online-virus-scanner/url/jeflu-online"}
stored_record: {"gs_trust_score":0,"gs_status":"not_found","gs_signals":null,"gs_url":"https://gridinsoft.com/online-virus-scanner/url/jeflu-online","gs_rating":null,"gs_reviews":0}

PhishDestroy DOM

88 / 100 · heuristic score · 0 brand references · 1 classification

2026-07-17 10:20 UTC

Open report

Separate monitor score · 0 / 100 · 2026-07-17T10:20:04Z

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-07-17T10:20:04Z
source_timestamp: 2026-07-17 12:20:04
timestamp_basis: Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Questions about jeflu.online

Is jeflu.online legit?

PhishDestroy rates jeflu.online as critical risk (88/100) from the recorded evidence; it was first recorded on 2026-07-17. Stored VirusTotal result: 5/91 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is jeflu.online safe to connect a wallet?

This report does not record which wallet requests jeflu.online 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 jeflu.online?

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

.online phishing domains
Namecheap: abuse response
Glossary: Phishing kit, Typosquatting
Tools: Check jeflu.online for look-alike characters, Draft an abuse report for jeflu.online
Research: 8 Seed Phrase Stealers Reverse-Engineered · Why Phishing Scanners Disagree: A Field Guide

Blocklist matchesPhishDestroy · no match in the other 11 1

PhishDestroy PhishDestroy list View source

Checked, no match

Last checked 2026-11-02 23:20:02 UTC

Stored Capture · 3 captures

Screenshot of jeflu.online — **Stored capture**Capture time unavailable 1 / 3

SourceStored capture

RecordedCapture time unavailable

StateStored capture

Position1 / 3

Open capture Wayback Download

All capture links and hashes (3)

Stored capture · Capture time unavailable
URLScan capture · Capture time unavailable · Source report
URLQuery capture · 2026-10-25 12:08 UTC · Source report

Observed page title

404 Not Found

TLS Certificate

Issued by Let's Encrypt / YE2 · stored validity ends in 50 days

**Social preview card** jeflu.online: caution — 5/91 VirusTotal engines. PhishDestroy risk score 88/100 (critical). v e756bf955f80

Domain details

Domain

URLScan verdict Analysis completed score 0 report ↗

IP Context

104.21.32.146 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.

OTX tags 2026-07activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam

Registrar Namecheap

(US)

Abuse contact["abuse@namecheap.com", "registry@namecheap.com"]

ICANN RegistryICANN Lookup (RDAP) →

WHOIS LookupICANN RDAP for jeflu.online →

RegistrationCreated May 29, 2026 (157d) — Expires May 29, 2027

HTTP Status503 Error

Elapsed Since First Report 89 days

What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Server error.

What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.

LLM Report Plain-text dossier structured for AI agents

Technical detailsProvenance & timestamps

First DetectedJul 17, 2026

DOM Analysisanalyzed Jul 17, 2026score 88/100

Submitted URLhttps://jeflu.online/bVKTKCCr?… query redacted

Favicon Hash

ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

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

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge

Resolved IP: 104.21.32.146
Network ASN: AS13335
AS name: CLOUDFLARENET - Cloudflare, Inc., US
Organization: Cloudflare, Inc.
Observed location: Toronto, CA
Server header: cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

noor.ns.cloudflare.com
odin.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer: Let's Encrypt / YE2
Valid from: 2026-09-24 10:29:19
Valid until: 2026-12-23 10:29:18
Validity: Within stored validity dates
Collection time: 2026-10-10 13:02:12 UTC
Collection source: PhishDestroy collector

Certificate fingerprint

f81537061f79a48d5d39f6f7950addcdc66e3c37e20c3bfbe4e237c2d3a7044e

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.32.146 rapiddns.io

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 91 security vendors flagged this domain

View on VT

First positive detection 2026-07-30 02:01:22 UTC Previous stored snapshot: 5 detections

alphaMountain.ai

CRDF

Forcepoint ThreatSeeker

Gridinsoft

SOCRadar

Registration & observation details1

Availability observations

Last reachable observation: 2026-10-13 22:06:33 UTC

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

Captured network requests

Network requests: 7 SHA-256 hashes: 7 URLScan scan: 2026-07-17 09:08 UTC

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-29 03:35 UTC.

Open this scan on URLScan 019f6f55-f17d-7648-bf4f-d91811497370 ↗

Stored observation history12

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

2026-10-17 01:53:52 UTC
Availability monitor · Recorded state
inactive

http_no_content
2026-10-15 01:57:30 UTC
Availability monitor · Recorded state
inactive

http_no_content
2026-10-13 22:29:41 UTC
Domain monitor · Recorded state
Reachable→Unavailable
2026-10-13 22:06:33 UTC
Availability monitor · Recorded state
redirected

http_redirect
2026-10-13 01:41:16 UTC
Availability monitor · Recorded state
redirected

http_redirect

Earlier observations 7

2026-10-11 22:06:04 UTC
Availability monitor · Recorded state
redirected

http_redirect
2026-10-10 22:06:15 UTC
Availability monitor · Recorded state
redirected

http_redirect
2026-10-09 22:05:53 UTC
Availability monitor · Recorded state
redirected

http_redirect
2026-10-09 10:05:43 UTC
Availability monitor · Recorded state
redirected

http_redirect
2026-10-07 01:50:31 UTC
Availability monitor · Recorded state
inactive

http_no_content
2026-10-03 01:41:07 UTC
Availability monitor · Recorded state
inactive

http_no_content
2026-10-01 01:43:35 UTC
Availability monitor · Recorded state
inactive

http_no_content

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC: 2026-07-17T09:15:01Z
Recorded HTTP status: No response code recorded
Original source timestamp: 2026-07-17 11:15:01

All retained availability observations78

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.

2026-11-01 · 22:20:11.055498 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-11-01 23:20:11.055498
Evidence SHA-256
7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-11-01 23:20:11.055498
Evidence reason
2026-11-01 · 02:16:05 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-11-01 03:16:05.000000
Evidence SHA-256
1fdf71265619e46ce8d936027457351e10f4f94bf5c04397c01be24f0486d32d

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-11-01 03:16:05
Evidence reason
transient_503
2026-11-01 · 02:16:05 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-11-01 03:16:05.000000
Evidence SHA-256
41c873136fd79e6da4346a0912414b82f54c0b007ac970df0bf09247b157aba4

Evidence timestamp as recorded
2026-11-01 03:16:05
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-31 · 22:20:09.600237 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-31 23:20:09.600237
Evidence SHA-256
fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-31 23:20:09.600237
Evidence reason
2026-10-31 · 02:17:29 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-31 03:17:29.000000
Evidence SHA-256
da7e7d66815d6737f010e4b8782601fe5440c93a232f8bf5dd07e84d492d583f

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-31 03:17:29
Evidence reason
transient_503
2026-10-31 · 02:17:29 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-31 03:17:29.000000
Evidence SHA-256
da7e7d66815d6737f010e4b8782601fe5440c93a232f8bf5dd07e84d492d583f

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-31 03:17:29
Evidence reason
transient_503
2026-10-30 · 16:03:05.966399 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-30 17:03:05.966399
Evidence SHA-256
50a5215b0c566b7822d085a87e391f0469a076c3f7f015e688ebee68afcfcc96

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-30 17:03:05.966399
Evidence reason
2026-10-29 · 16:03:05.221734 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-29 17:03:05.221734
Evidence SHA-256
2f984a79e84ab655d11fb271d10d9444f6b23d40b345ed653cfbb2faf803b616

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-29 17:03:05.221734
Evidence reason
2026-10-29 · 02:26:57 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-29 03:26:57.000000
Evidence SHA-256
44b75f3d2969cbfe23c88dee0d7f5f34524b9df0866f1c6db17be6d43483f3ad

Evidence timestamp as recorded
2026-10-29 03:26:57
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-29 · 02:26:57 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-29 03:26:57.000000
Evidence SHA-256
54ec9d5195fa0512bdc8bb46ff675c77920ebd1f024b4c28218ddf620b271f1c

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-29 03:26:57
Evidence reason
transient_503
2026-10-28 · 08:55:10.533471 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-28 09:55:10.533471
Evidence SHA-256
d7c171c3bc25387a314e97b9f8de814f4cae02ff9867fec22f1e7258a5a26a48

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-28 09:55:10.533471
Evidence reason
2026-10-27 · 08:55:08.586816 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-27 09:55:08.586816
Evidence SHA-256
fa8e9b8de0fa2ff3f2c60817f493162c8480eb1a7ff0a28e0a7abc823995c62f

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-27 09:55:08.586816
Evidence reason
2026-10-27 · 02:28:42 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-27 03:28:42.000000
Evidence SHA-256
5a2949cdd4e06a45505827e79270211bd15f5708e10dadcbeabd090f52df8898

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-27 03:28:42
Evidence reason
transient_503
2026-10-27 · 02:28:42 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-27 03:28:42.000000
Evidence SHA-256
dd45087b807b3256b3d65ddf476045030e9ff635fd0a50b5d357c7e54bc8269e

Evidence timestamp as recorded
2026-10-27 03:28:42
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-26 · 08:55:08.299319 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-26 09:55:08.299319
Evidence SHA-256
37b5c19af06da555fb6055130c267aaeda09ed615e57f17df294ffe2591f7ef9

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-26 09:55:08.299319
Evidence reason
2026-10-25 · 08:55:07.418941 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-25 09:55:07.418941
Evidence SHA-256
f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-25 09:55:07.418941
Evidence reason
2026-10-25 · 02:24:59 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-25 03:24:59.000000
Evidence SHA-256
70b5fb39f36793f363f33daa0c07112694d07dff1a996c5cdf84b4a65fb79872

Evidence timestamp as recorded
2026-10-25 03:24:59
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-25 · 02:24:59 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-25 03:24:59.000000
Evidence SHA-256
797e3457844e74be1b335a5c67e3627901abfadc9a7475a04d59495f22bbced7

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-25 03:24:59
Evidence reason
transient_503
2026-10-23 · 20:56:16.207510 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-23 22:56:16.207510
Evidence SHA-256
c5f098587335747ecb0284c1aaf394d9a7f57967b624ae64d7c6e3e96d6d5417

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-23 22:56:16.207510
Evidence reason
2026-10-23 · 01:30:11 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-23 03:30:11.000000
Evidence SHA-256
192cd1e141e68cfb1b7ce429584c761b40d190d9daf24055866949fe91a186f4

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-23 03:30:11
Evidence reason
transient_503
2026-10-23 · 01:30:11 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-23 03:30:11.000000
Evidence SHA-256
85713cc9267c1485972d0e6362b912f014c75b383eb2a1e2073a4e4611fae3ac

Evidence timestamp as recorded
2026-10-23 03:30:11
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-22 · 20:55:15.888363 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-22 22:55:15.888363
Evidence SHA-256
3b646e5bc1bac379c47f59c89fb9159326ef6c40d3366eb6dfd5fa43e677c4aa

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-22 22:55:15.888363
Evidence reason
2026-10-21 · 14:53:36.928467 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-21 16:53:36.928467
Evidence SHA-256
80d44683077929d57cc69d3d485aa4d0ee469673c8067e794714c21730456f32

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-21 16:53:36.928467
Evidence reason
2026-10-21 · 01:19:31 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-21 03:19:31.000000
Evidence SHA-256
6c6f352df5424faabbb5ff16079191281e49a62641cae75c9c11b618f0590871

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-21 03:19:31
Evidence reason
transient_503
2026-10-21 · 01:19:31 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-21 03:19:31.000000
Evidence SHA-256
bfe4fb7a49312c99ef0e6643d04e992b18839da610c6a84f5274374ea6a52b65

Evidence timestamp as recorded
2026-10-21 03:19:31
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-20 · 08:21:37.183325 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-20 10:21:37.183325
Evidence SHA-256
f6ebc34c637ae5924f85300e39eeddc978e4821086a9222c87005e67a3b0d797

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-20 10:21:37.183325
Evidence reason
2026-10-19 · 08:21:20.392196 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-19 10:21:20.392196
Evidence SHA-256
470b54ea6ccbe7f04a3825ada981b64179b616b50f8ee2944c5c5cf09876edf4

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-19 10:21:20.392196
Evidence reason
2026-10-19 · 01:19:37 UTChttp_observationunknown

Observation source
http_observation
Cause
origin_unreachable
Availability state
unreachable
Content state
unknown
DNS state
unknown
Recorded HTTP status
503
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Mechanism
http_5xx
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-19 03:19:37.000000
Evidence SHA-256
0b164b4ffba05a6ba231e29d2e44f99fb00a048dfe880f168ae0aaa666b1b1ad

HTTP probe value as recorded
503
Evidence timestamp as recorded
2026-10-19 03:19:37
Evidence reason
transient_503
2026-10-19 · 01:19:37 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
503
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-19 03:19:37.000000
Evidence SHA-256
1c7bccaa155835703a4f604fa0d8500f291be74686f7a15420a44d66319f1757

Evidence timestamp as recorded
2026-10-19 03:19:37
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-18 · 08:21:15.144873 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-18 10:21:15.144873
Evidence SHA-256
d137b34b07ce5d4f8c2c0144bb3a689c0914216b2acecc6045167a7531565b2d

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-18 10:21:15.144873
Evidence reason
2026-10-17 · 01:53:52 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
404
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-17 03:53:52.000000
Evidence SHA-256
a610d973558c5f562fb08763407b31752769011f189e5ef2658aac5cf7a81443

Evidence timestamp as recorded
2026-10-17 03:53:52
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-17 · 01:53:52 UTChttp_observationinactive

Observation source
http_observation
Cause
http_no_content
Availability state
root_no_content
Content state
absent_at_root
DNS state
unknown
Recorded HTTP status
404
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
70
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-17 03:53:52.000000
Evidence SHA-256
dbb8920a06ccb02a03968e01354e470ae29b5eb0ea9e0f0ef869200b1478ab8b

HTTP probe value as recorded
404
Evidence timestamp as recorded
2026-10-17 03:53:52
Evidence reason
http_other
2026-10-16 · 20:22:38.733165 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-16 22:22:38.733165
Evidence SHA-256
715151e070bd7bc191e99245412b910620c301fbdb64cf388d91d23b9dbf29da

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-16 22:22:38.733165
Evidence reason
2026-10-15 · 20:22:19.692675 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-15 22:22:19.692675
Evidence SHA-256
6c278207335eea35544133b166242cb2e0215578c9ef66df1220a947d8ab535c

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-15 22:22:19.692675
Evidence reason
2026-10-15 · 01:57:30 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
404
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-15 03:57:30.000000
Evidence SHA-256
348f4ab04ce8843bfaf31798db668ae495d109a5ea3433c3bba19d1fc94696af

Evidence timestamp as recorded
2026-10-15 03:57:30
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-15 · 01:57:30 UTChttp_observationinactive

Observation source
http_observation
Cause
http_no_content
Availability state
root_no_content
Content state
absent_at_root
DNS state
unknown
Recorded HTTP status
404
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
70
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-15 03:57:30.000000
Evidence SHA-256
a9e8d00e75a2b5a2d30511cdfc765d2eebb720bb3008099753e3b7841c44f9af

HTTP probe value as recorded
404
Evidence timestamp as recorded
2026-10-15 03:57:30
Evidence reason
http_other
2026-10-14 · 20:21:26.687207 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-14 22:21:26.687207
Evidence SHA-256
84b3890be530ef4dfe4674dbe40cf3c017c8e665cc7af4be1060bb48d22e958e

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-14 22:21:26.687207
Evidence reason
2026-10-13 · 22:06:33 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-14 00:06:33.000000
Evidence SHA-256
da08e1690ea43b43f0835a901e0537fdab925a5468c17c2257bdb35fbae24b14

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-14 00:06:33
Evidence reason
redirect
2026-10-13 · 22:06:33 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-14 00:06:33.000000
Evidence SHA-256
da08e1690ea43b43f0835a901e0537fdab925a5468c17c2257bdb35fbae24b14

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-14 00:06:33
Evidence reason
redirect
2026-10-13 · 20:21:07.146269 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-13 22:21:07.146269
Evidence SHA-256
d402eaa2a918551b0c13724c34dc7c6f5747360d1b3897bd73ccc2aa9d2e9da2

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-13 22:21:07.146269
Evidence reason
2026-10-13 · 10:07:06 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-13 12:07:06.000000
Evidence SHA-256
7a095980e9c0ca39b32819adfb98b084ceafab3dcb36eb4c4fa4ad993ca0d297

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-13 12:07:06
Evidence reason
redirect
2026-10-13 · 10:07:06 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-13 12:07:06.000000
Evidence SHA-256
7a095980e9c0ca39b32819adfb98b084ceafab3dcb36eb4c4fa4ad993ca0d297

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-13 12:07:06
Evidence reason
redirect
2026-10-13 · 01:41:16 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-13 03:41:16.000000
Evidence SHA-256
b920f78c59b16b871980c50044b000af33e52d38ec97cdc8efe1d8df62b9ca99

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-13 03:41:16
Evidence reason
redirect
2026-10-13 · 01:41:16 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-13 03:41:16.000000
Evidence SHA-256
b920f78c59b16b871980c50044b000af33e52d38ec97cdc8efe1d8df62b9ca99

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-13 03:41:16
Evidence reason
redirect
2026-10-12 · 20:20:57.953315 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-12 22:20:57.953315
Evidence SHA-256
b0927403a99131c7bcdd762cc5daf4b5da8ff49029520964407d00c9043f360e

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-12 22:20:57.953315
Evidence reason
2026-10-12 · 10:06:43 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-12 12:06:43.000000
Evidence SHA-256
dd0877a78c23bfc9e24842bf9dfa01047cbcdb9a679b1ae0d2f395a942e3c33b

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-12 12:06:43
Evidence reason
redirect
2026-10-12 · 10:06:43 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-12 12:06:43.000000
Evidence SHA-256
dd0877a78c23bfc9e24842bf9dfa01047cbcdb9a679b1ae0d2f395a942e3c33b

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-12 12:06:43
Evidence reason
redirect
2026-10-11 · 22:06:04 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-12 00:06:04.000000
Evidence SHA-256
d990cff23f4f2dbddfcce64f53c0e9f08e592eb320a32acf69da4ad6f0952336

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-12 00:06:04
Evidence reason
redirect
2026-10-11 · 22:06:04 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-12 00:06:04.000000
Evidence SHA-256
d990cff23f4f2dbddfcce64f53c0e9f08e592eb320a32acf69da4ad6f0952336

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-12 00:06:04
Evidence reason
redirect
2026-10-11 · 20:20:50.151913 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 22:20:50.151913
Evidence SHA-256
06138ca909a4f3051eacea3d7a21df5e64801de0f27b809182dd0385032cd5b4

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-11 22:20:50.151913
Evidence reason
2026-10-11 · 10:06:37 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 12:06:37.000000
Evidence SHA-256
c4d0f11fc2decaf5cbe44020f8b7d9c77355f1501919aad96a2648b2532ca0f2

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-11 12:06:37
Evidence reason
redirect
2026-10-11 · 10:06:37 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 12:06:37.000000
Evidence SHA-256
c4d0f11fc2decaf5cbe44020f8b7d9c77355f1501919aad96a2648b2532ca0f2

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-11 12:06:37
Evidence reason
redirect
2026-10-11 · 01:39:46 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 03:39:46.000000
Evidence SHA-256
727197f82bdfee1f2ad58d61a751d3bcf1d79d50daabb13a2398a861545d4c41

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-11 03:39:46
Evidence reason
redirect
2026-10-11 · 01:39:46 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 03:39:46.000000
Evidence SHA-256
727197f82bdfee1f2ad58d61a751d3bcf1d79d50daabb13a2398a861545d4c41

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-11 03:39:46
Evidence reason
redirect
2026-10-10 · 22:06:15 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 00:06:15.000000
Evidence SHA-256
0b6fd45c13b937a2c0d0711db5a6a4e884b33fd5e81a32660f98b687edbff75c

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-11 00:06:15
Evidence reason
redirect
2026-10-10 · 22:06:15 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-11 00:06:15.000000
Evidence SHA-256
0b6fd45c13b937a2c0d0711db5a6a4e884b33fd5e81a32660f98b687edbff75c

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-11 00:06:15
Evidence reason
redirect
2026-10-10 · 20:20:48.858561 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-10 22:20:48.858561
Evidence SHA-256
11ef8921e63041943b1b74a04946731f8dff73b042235954f632140452c757a1

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-10 22:20:48.858561
Evidence reason
2026-10-10 · 10:05:45 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-10 12:05:45.000000
Evidence SHA-256
f9bdb726e30ac2cf2a87dd29a3dca626039e019a053f57700ac8f87a27e83948

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-10 12:05:45
Evidence reason
redirect
2026-10-10 · 10:05:45 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-10 12:05:45.000000
Evidence SHA-256
f9bdb726e30ac2cf2a87dd29a3dca626039e019a053f57700ac8f87a27e83948

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-10 12:05:45
Evidence reason
redirect
2026-10-09 · 22:05:53 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-10 00:05:53.000000
Evidence SHA-256
32b4d6745528f491851c9ba482cd4497f08c361ad515354ad78ae0a447e40435

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-10 00:05:53
Evidence reason
redirect
2026-10-09 · 22:05:53 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-10 00:05:53.000000
Evidence SHA-256
32b4d6745528f491851c9ba482cd4497f08c361ad515354ad78ae0a447e40435

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-10 00:05:53
Evidence reason
redirect
2026-10-09 · 20:20:42.401113 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-09 22:20:42.401113
Evidence SHA-256
a36a067ca705bb74c2c35205661a07c0cfb9775d48d28db2e1eb50c1eb58d9d2

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-09 22:20:42.401113
Evidence reason
2026-10-09 · 10:05:43 UTCcurrent_http_proberedirected

Observation source
current_http_probe
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-09 12:05:43.000000
Evidence SHA-256
93189643865ee5e4232cd9aab4cce21291144b293af6b6bd0c25563024df61b6

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-09 12:05:43
Evidence reason
redirect
2026-10-09 · 10:05:43 UTChttp_observationredirected

Observation source
http_observation
Cause
http_redirect
Availability state
reachable_redirect
Content state
unknown
DNS state
unknown
Recorded HTTP status
301
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
80
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-09 12:05:43.000000
Evidence SHA-256
93189643865ee5e4232cd9aab4cce21291144b293af6b6bd0c25563024df61b6

HTTP probe value as recorded
301
Evidence timestamp as recorded
2026-10-09 12:05:43
Evidence reason
redirect
2026-10-08 · 20:20:32.448533 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-08 22:20:32.448533
Evidence SHA-256
0da49a5add3e494d62c4dd99eadc9a6eb4fa06348e3d5f894716599a81c8b1a7

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-08 22:20:32.448533
Evidence reason
2026-10-07 · 01:50:31 UTChttp_observationinactive

Observation source
http_observation
Cause
http_no_content
Availability state
root_no_content
Content state
absent_at_root
DNS state
unknown
Recorded HTTP status
404
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
70
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-07 03:50:31.000000
Evidence SHA-256
73eaeb0febbb6ae7cf6bd09060a02402328e4b90123124343627aca8c8afa174

HTTP probe value as recorded
404
Evidence timestamp as recorded
2026-10-07 03:50:31
Evidence reason
dead_http
2026-10-07 · 01:50:31 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
404
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-07 03:50:31.000000
Evidence SHA-256
7f7ee5c8abc2e97bca11fd1daaf6356e12ffda54c226eaabdf91271d327de36a

Evidence timestamp as recorded
2026-10-07 03:50:31
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-06 · 22:13:39.270476 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-07 00:13:39.270476
Evidence SHA-256
0f399a21e98e0256f98d43c4d230f6dc7ee0a7a8efd7ef9c6c107be031afd218

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-07 00:13:39.270476
Evidence reason
2026-10-05 · 22:13:39.266033 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-06 00:13:39.266033
Evidence SHA-256
73a145cd4429727962b5329d34695921409b9b9666743d039a9cc9ba9e3526c7

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-06 00:13:39.266033
Evidence reason
2026-10-04 · 22:13:35.837561 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-05 00:13:35.837561
Evidence SHA-256
74452d0282caf7aefe2eabc79f33c87072b1889a11d214b6860e6b3e5f762831

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-05 00:13:35.837561
Evidence reason
2026-10-03 · 16:16:30.317188 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-03 18:16:30.317188
Evidence SHA-256
70d02346b5dbc706195b1302376a295ce40556bf1954b2c513314c32a40a1aeb

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-03 18:16:30.317188
Evidence reason
2026-10-03 · 01:41:07 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
404
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-03 03:41:07.000000
Evidence SHA-256
064eaed8335f191d4efaa77248babe0a430677a6ad34e5751bfcd9b173edfccb

Evidence timestamp as recorded
2026-10-03 03:41:07
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-10-03 · 01:41:07 UTChttp_observationinactive

Observation source
http_observation
Cause
http_no_content
Availability state
root_no_content
Content state
absent_at_root
DNS state
unknown
Recorded HTTP status
404
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
70
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-03 03:41:07.000000
Evidence SHA-256
160ca658c32a109dc10ed0f1f403d51bcc1014c11fec390399d28d59cf2f22c1

HTTP probe value as recorded
404
Evidence timestamp as recorded
2026-10-03 03:41:07
Evidence reason
dead_http
2026-10-02 · 16:16:28.238873 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-02 18:16:28.238873
Evidence SHA-256
83187e78159518c7977f539ffd2603b7d792d43342363046cf38db99dacb648d

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-02 18:16:28.238873
Evidence reason
2026-10-01 · 16:16:25.663717 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-01 18:16:25.663717
Evidence SHA-256
028c1788389f548aae03eebc6ec364be02a41bf49d956382ace6ac5f6bd2196b

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-10-01 18:16:25.663717
Evidence reason
2026-10-01 · 01:43:35 UTChttp_observationinactive

Observation source
http_observation
Cause
http_no_content
Availability state
root_no_content
Content state
absent_at_root
DNS state
unknown
Recorded HTTP status
404
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
70
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-10-01 03:43:35.000000
Evidence SHA-256
15a18671ce234e39b1213bab6506177bc995be0b50cc5ae8d8f6befd51467f81

HTTP probe value as recorded
404
Evidence timestamp as recorded
2026-10-01 03:43:35
Evidence reason
dead_http
2026-10-01 · 01:43:35 UTCcurrent_http_probeunknown

Observation source
current_http_probe
Cause
stale_current_evidence
Availability state
unknown
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Recorded HTTP status
404
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-01 03:43:35.000000
Evidence SHA-256
c3c7be42407e0c3cafc73e2871a569ddb4d7ea7d2b2b5544009e170f928b7427

Evidence timestamp as recorded
2026-10-01 03:43:35
DNS evidence marked stale
false
HTTP evidence marked stale
true
2026-09-30 · 16:14:55.856480 UTCdns_observationunknown

Observation source
dns_observation
Cause
probe_inconclusive
Availability state
unreachable
Content state
unknown
DNS state
resolved
DNS response code
NOERROR
Registration state
unknown
RDAP statuses
[]
Recorded actor type
unknown
Monitor confidence
20
Provider action verified
false
Registrar mechanism verified
false
Linked to a report
false
Original source timestamp
2026-09-30 18:14:55.856480
Evidence SHA-256
846116c132129e5b112ba4a0acda2d143f17093abc1c08a35fa0f050bcd750ea

HTTP probe value as recorded
0 · no HTTP response code recorded
Evidence timestamp as recorded
2026-09-30 18:14:55.856480
Evidence reason

Threat Response Pipeline

Discovery · recorded
Analysis · recorded
Monitoring · recorded

Recorded events: 7. 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

jeflu.online detected and queued for full analysis

Jul 17, 2026

Threat Intelligence ChecksURLScan.io Capture · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 5 of 5

URLScan.io Capture

Stored URLScan report with capture artifacts

Jul 17, 2026
OTX Community References

Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.

Oct 9, 2026
Forensic Evidence Collected

Stored evidence from URLScan.io, URLQuery, stored screenshot

Jul 17, 2026
Technical Analysis Recorded

The report contains stored results of technology detection or forensic analysis.

Jul 17, 2026
Content Observed Unavailable

Monitoring recorded an unavailable response (HTTP 301); the cause was not independently established.

Oct 13, 2026

Publication & AvailabilityDestroyList Published Recorded: 1 of 1

DestroyList Published

Listed in the public repository PhishDestroy/DestroyList

Jul 17, 2026

Recorded activity

3 entries

AlienVault OTX
4 community references
View source
2026-10-09 11:58:52 UTC
Added to PhishDestroy
jeflu.online
View source
2026-07-17 09:09:41 UTC
URLScan
Page captured
View source
2026-07-17 09:09:41 UTC

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.

Google Safe Browsing Transparency Report

Check whether Google currently lists the URL as unsafe.

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.

abuse.ch ThreatFox IOC correlation

Look for matching indicators and associated threat records.

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

Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Source Download all records as JSON

Check for cloaking

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

jeflu.online

Evidence & External Reports

Security Analysis

URLScan Analyzed VirusTotal 5 det. ChainPatrol URLQuery Report stored SSL Labs OTX 4 refs 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

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked Server error

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

FBI IC3

Report internet-enabled crime in the United States

IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance

Federal tips line1-800-CALL-FBI

Report online

Europol

Find the official reporting channel for your EU country

National police directory

Find your country

Action Fraud

Report fraud and cybercrime in England, Wales and Northern Ireland

Current service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.

Contact centre0300 123 2040

Report online

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.

NCSC United Kingdom

Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.

Emailreport@phishing.gov.uk Text messages7726

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.

APWG Worldwide

Forward phishing emails to the Anti-Phishing Working Group.

Emailreportphishing@apwg.org

cybercrime.gov.in India

National Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.

Helpline1930

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.

Canadian Anti-Fraud Centre Canada

Report fraud and scams in Canada and read current scam alerts.

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 jeflu.online)
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 response FBI IC3 · reports & evidence FTC · 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

Live Threat Feed Appeal This Listing

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.

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/jeflu.online"
  title="PhishDestroy threat report for jeflu.online"
  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>

jeflu.online

Analysis

VirusTotal

URLQuery

OTX

Google Safe Browsing

URLScan

Spamhaus DBL

Gridinsoft

PhishDestroy DOM

Questions about jeflu.online

Is jeflu.online legit?

Is jeflu.online safe to connect a wallet?

What should I do if I used jeflu.online?

Explore

Stored Capture · 3 captures

Domain details

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

Network & certificates

Nameservers 2

VirusTotal Analysis

Availability observations

Captured network requests

Threat Response Pipeline

Recorded activity

Public scans, evidence and abuse channels

Related Infrastructure & Reports

Content matches 4

Unclassified kit records: Unknown 8

Same registrar: Namecheap 6

Recent threat reports 4

Check for cloaking

Evidence & External Reports

Were You Affected by This Site?

Official reporting routes

More official reporting routes

Report to Your Local Authorities

Recommendations & Advice for Victims

What should I do immediately?

What information should I collect for my report?

Where should I report the scam?

How do phishing scams typically work?

How can I protect myself in the future?

Check Any Domain

Report Phishing

Live Threat Feed

Stay Informed, Stay Safe