luxora.qpon was recorded on 2026-10-07 with a PageSpeed performance score of 100, and was listed on the Phishunt blocklist on the same date. The domain was also observed in internal listings and was checked by multiple security sources.
Recorded Evidence
Phishunt included luxora.qpon on its blocklist on 2026-10-07. VirusTotal checked the domain on 2026-09-30, reporting 4 detections out of 92 scanners. OTX recorded 5 pulses for luxora.qpon on 2026-10-07. The domain was registered with Dominet (HK) Limited on 2026-09-29.
Interpretation
The records from Phishunt, VirusTotal, and OTX show that luxora.qpon was noted by several security sources within a short time frame. The presence of detections and blocklist inclusion reflects that the domain was observed by external and internal monitoring platforms. The PageSpeed performance score and registration details provide additional context for technical and historical reference.
Recommended Actions
For luxora.qpon, retain the Phishunt blocklist entry and VirusTotal detection results for future comparison. Keep the OTX pulse count and PageSpeed performance score as reference points for monitoring any subsequent changes. Compare these source records over time to track updates or new observations relevant to the domain.
탐지 회피 분석
클로킹 의심: 스캐너와 방문자 제목이 다름
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Attributionactor class: Hostingmechanism: Suspension Pagesource: Current Http Probe
Evidence layersAvailability: Non Threat ContentContent: Replaced Or ParkedDNS: ResolvedRegistration: Unknown
Latest HTTP observation비활성Hosting Account Suspendedactor class: HostingSuspension Page60%2026-10-11 10:07:46 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 01:40:58 UTClast content: 2026-10-11 01:40:58 UTCcurrent episode first observed: 2026-10-11 10:07:46 UTCobserved RIP window: 2026-10-11 01:40:58 UTC → 2026-10-11 10:07:46 UTC · 8.45hmidpoint estimate ≈ 2026-10-11 05:54:22 UTC · precision medium · 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.
위협 인텔리전스 교차 확인 · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
MalwareURL
Seclookup
SOCRadar
소포스
URLQuery
VIPRE
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of luxora.qpon· 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
1.08s
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-11 10:07:46 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-10-09 01:47:59 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-07 11:14:52 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-07 05:34:07 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 50.6.202.214.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
15 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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)
