oklahoma.gov-pox.click is a subdomain of gov-pox.click. PhishDestroy first observed the hostname on Oct 7, 2026. The captured page title is “Welcome to CentOS”. Current evidence score: 92/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and Spamhaus DBL. VirusTotal recorded 14 detections among 92 engines: alphaMountain.ai, ArcSight Threat Intelligence, BitDefender, Chong Lua Dao, ESET, Fortinet, G-Data, Gridinsoft, LevelBlue, Lionic, SOCRadar, Sophos, VIPRE, Webroot on Oct 10, 2026 at 14:10 UTC. Spamhaus DBL: DBL_PHISH on Oct 7, 2026 at 18:30 UTC.
Latest classified outcome: unknown; cause probe inconclusive on Oct 11, 2026 at 08:08 UTC. Registration records for the registrable domain gov-pox.click list Dynadot, LLC as the registrar and Apr 11, 2026 as the creation date. At collection time, the hostname resolved to 47.84.28.89 on AS45102 (Alibaba (US) Technology Co., Ltd.). The recorded endpoint location is Singapore, SG. The stored server header is nginx/1.20.1. The evidence archive retains 1 visual capture from PhishDestroy.
The content indicators and 2 positive source findings support the current phishing classification.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='oklahoma.gov-pox.click', port=80): Max retries exceeded with url: / (Caused by NewConnecti
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Registration (base domain)gov-pox.click · 생성됨 2026년 4월 11일 (183d)
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 7일
Submitted URLhttp://oklahoma.gov-pox.click/
ICANN OVERSIGHTRegistration: gov-pox.click
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For the registrable domain gov-pox.click behind this subdomain, 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.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 10:08:47 UTC
RDAP registration알 수 없음
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.
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
ArcSight Threat Intelligence
BitDefender
Chong Lua Dao
ESET
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
SOCRadar
소포스
VIPRE
Webroot
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.
Threat First Observed2026-10-07 16:07:15 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 47.84.28.89.
위협 대응 Pipeline
발견
Analysis
Monitoring
7 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.
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)
