On 2026-10-08 the domain gofort.cc returned HTTP status 200, indicating a live server response. The domain was first observed publicly on 2026-10-06, showing recent network presence.
Recorded Evidence
gofort.cc was recorded in the publisher-owned PhishDestroy catalogue on 2026-10-07. VirusTotal detected 7 detections out of 92 total scanners on 2026-10-02. OTX listed the domain in 3 pulses on 2026-10-07. A urlscan report was generated on 2026-09-09 and remains available.
Interpretation
The recorded observations span multiple independent sources over a short period, each documenting different aspects of the domain’s activity. The HTTP response, catalogue listing, and detection counts were collected on distinct dates, providing varied but contemporaneous snapshots rather than a single trend. The availability of a urlscan report adds a detailed page capture for further review.
Recommended Actions
For the domain gofort.cc, preserve the urlscan report and VirusTotal scan for comparison with future checks. Review the OTX pulses and PhishDestroy catalogue entry alongside any new HTTP responses to assess consistency over time. Maintain these dated records to evaluate whether observed characteristics remain stable or change.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='gofort.cc', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCK
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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 10:08:39 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-09 10:07:54 UTClast content: 2026-10-09 10:07:54 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:07:54 UTC → 2026-10-09 20:20:42 UTC · 10.21hmidpoint estimate ≈ 2026-10-09 15:14:18 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.
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Forcepoint ThreatSeeker
Fortinet
LevelBlue
SOCRadar
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of gofort.cc· checked Oct 6, 2026
75
Needs Work
Performance
FCP
4.2s
First Contentful Paint
LCP
4.26s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
54ms
Total Blocking Time
SI
4.2s
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.
VirusTotal Detections Update2026-10-07 11:19:43 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-10-07 05:17:12 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-10-06 15:57:18 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: alphaMountain.ai.
Threat First Observed2026-10-06 05:17:25 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.29.26.38.
위협 대응 Pipeline
발견
Analysis
Monitoring
12 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.
(VN)
