On 2026-10-01 the domain dpd.ffmka.club returned HTTP status 502, a recorded server error at that measurement time. The same domain was first observed on 2026-08-31, according to the recorded observation timeline.
Recorded Evidence
Google Safe Browsing checked dpd.ffmka.club on 2026-09-14 and flagged it for social engineering. VirusTotal recorded 19 detections across 89 total scanners for the domain on 2026-09-14. The PhishDestroy internal listing included dpd.ffmka.club, with a blocklist check dated 2026-10-02. An SSL scan on 2026-08-31 recorded the issuer as Google Trust Services / WE1.
Interpretation
The dated records describe separate measurements: an HTTP response, a Safe Browsing flag, VirusTotal detection counts, and a PhishDestroy listing. Because these observations fall on different dates, they should be read as individual snapshots rather than a single combined result. The HTTP 502 describes only the response recorded on its date, not all content the domain may serve.
Recommended Actions
Anyone reviewing dpd.ffmka.club should preserve the dated HTTP response, the Safe Browsing flag, the VirusTotal detection counts, and the PhishDestroy listing as separate records. Compare those saved records against later observations of dpd.ffmka.club to see whether the recorded values change. Treat the domain cautiously in browsing and security decisions while relying on the dated evidence rather than any single metric.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dpd.ffmka.club', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Registration (base domain)ffmka.club · 생성됨 2026년 8월 22일 (50d · New)
최초 이용 불가까지 걸린 시간11 days
집계 기준
처음 저장된 악용사례 신고부터 콘텐츠를 사용할 수 없다는 첫 번째 관찰까지의 경과 시간입니다. 이것은 원인을 확립하지 못합니다.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 8월 31일
Submitted URLhttp://dpd.ffmka.club/com
Favicon Hash
ICANN OVERSIGHTRegistration: ffmka.club
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For the registrable domain ffmka.club 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.
Certificate fingerprintef7828d36d7f1944932eafe29d7a1cf37a2ac173480116b361e4d406d084beccCertificate names · 1 SANs
ffmka.club
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:15:40 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-15 22:17:55 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:55 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:25 UTC · precision low · 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.
기술 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 19 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
카스퍼스키
LevelBlue
Lionic
넷크래프트
Seclookup
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.
Domain Status Transition2026-09-11 22:17:43 UTC
Domain state transitioned from dead to alive.
VirusTotal Detections Update2026-09-11 09:05:12 UTC
VirusTotal scanner detections updated from 20 to 19. Resolved alerts: Cluster25.
Domain Status Transition2026-09-10 22:21:34 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-08-31 22:30:33 UTC
VirusTotal scanner detections updated from 15 to 20. Added scanner alerts: BitDefender, Forcepoint ThreatSeeker, Lionic, Seclookup, VIPRE.
Status Check2026-08-31 08:10:02 UTC
Telemetry event observed.
Threat First Observed2026-08-31 08:06:35 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
위협 대응 Pipeline
발견
Analysis
Monitoring
18 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년 9월 11일
최초 이용 불가까지 걸린 시간
감지부터 사용할 수 없는 첫 번째 관찰까지 254 시간이 경과되었습니다.
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.
(HK)
