The domain luxfab.luxe was observed on the Phishunt blocklist as of 2026-10-07, reflecting a recorded entry in an external security database. On the same date, a PageSpeed performance score of 100 was recorded, indicating a technically responsive web presence.
Recorded Evidence
Phishunt listed luxfab.luxe on its blocklist on 2026-10-07. VirusTotal checked the domain on 2026-10-05, reporting 10 detections out of 92 scanners. OTX pulses were recorded twice on 2026-10-07. The domain was registered with Dominet (HK) Limited on 2026-09-23.
Interpretation
These records show that luxfab.luxe was noted by multiple monitoring sources within a short period after its registration. The blocklist entry and VirusTotal scan reflect external reviews, while OTX and PageSpeed data provide additional technical context. Each source offers a distinct perspective on the domain's status at the time of observation.
Recommended Actions
It is advisable to review the Phishunt blocklist entry and VirusTotal detection results for luxfab.luxe to understand the basis for their records. Preserve OTX pulse history and PageSpeed performance data for future comparison. Continue monitoring these sources for any updates or changes related to the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='luxfab.luxe', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 01:33:47 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-07 05:45:27 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-07 05:45:27 UTC → 2026-10-07 11:14:54 UTC · 5.49hmidpoint estimate ≈ 2026-10-07 08:30:10 UTC · precision high · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
기술 · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of luxfab.luxe· checked Oct 7, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-10-07 11:14:54 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-07 05:33:58 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 50.6.202.214.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
2026년 10월 7일
최초 이용 불가까지 걸린 시간
감지부터 사용할 수 없는 첫 번째 관찰까지 5 시간이 경과되었습니다.
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+
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.
(US)
