garammatka.com was observed with an HTTP status 200 on 2026-10-11, documenting a successful response at that time. The domain is also listed in the PhishDestroy internal catalogue, which records domains for monitoring purposes.
Recorded Evidence
The HTTP status source recorded a 200 response for garammatka.com on 2026-10-11. OTX referenced the domain with 31 pulses as of 2026-10-11. The domain is included in the PhishDestroy internal listing, noted on the same date. The registrar is Gname.com Pte. Ltd., and registration was documented on 2024-12-07.
Interpretation
The PhishDestroy internal listing contains a catalogue entry for garammatka.com, which serves as a record for internal tracking. OTX provides a measurement of community activity through its pulse count, reflecting engagement with the domain. The HTTP status source documents a technical response from the domain, offering insight into its network accessibility at the recorded date.
Recommended Actions
For garammatka.com, preserve the HTTP status record and PhishDestroy internal listing for future comparison with new observations. Retain the OTX pulse count as a reference for monitoring changes in community intelligence. Use these dated records to guide ongoing review and update procedures for the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:01:29 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:01:29 UTClast content: 2026-10-11 10:01:29 UTC
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.
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-10 22:01:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 201.5.224.57.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(CN)
