Skip to main content
Sandfish

Phone Khoj — खोया फोन? हम track करके ढूँढते हैं

https://rohit7631.github.io/PHONE-KHOJ/

Groupa4db16e4-6312-477d-96be-37b89d5e3fdesubmitted urlMember 1

Case summary

The target, observed result, and important findings.

Status
Current evaluation

Limited evidence: interaction stalled

Findings
2Low
Kit source work

Loading related source work…

Discover or upload kit source
Domain registration
github.iounsupported
Language
Detecting...
Network
6 requests across 3 hosts
Infrastructure
Loading...
Behavior
0 recorded events
Interaction
12 actions · 1 submission · stopped: repeated state · download stage: no payload control
  1. 1. fillsucceededtext | name | पूरा नाम * | जैसे — राहुल कुमार
  2. 2. fillsucceededtel | mobile | Mobile Number (WhatsApp वाला) * | 10 अंकों का number
  3. 3. fillsucceededemail | email | Email ID * | [email protected]
  4. 4. fillsucceededtext | brand | Phone का Brand * | जैसे — Samsung, Vivo, Redmi, Realme
  5. 5. fillsucceededtext | model | Phone का Model * | जैसे — Galaxy M14, Y28, Note 13
  6. 6. fillsucceededtext | color | Phone का Color / रंग * | जैसे — काला, नीला, सफ़ेद
  7. 7. fillfaileddatetime-local | lostWhen | Phone कब चोरी / खोया? (Date + Time) * |
  8. 8. submitsucceededSubmit करें — Email पर भेजें
  9. 9. validationobservedValidation (valueMissing) | text | imei1 | IMEI Number 1 *
  10. 10. validationobservedValidation (valueMissing) | datetime-local | lostWhen | Phone कब चोरी / खोया? (Date + Time) *
  11. 11. validationobservedValidation (valueMissing) | text | place | कहाँ चोरी / खोया? (जगह / शहर) *
  12. 12. validationobservedValidation (valueMissing) | text | utr | Payment ka UTR / Transaction Number *

Analysis metadata

How and when the analysis ran.

Input kind
url
Execution kind
capture
Duration
40.0s
Navigation
2 navigations
Engine version
0.4.1
Created
2026-11-13 16:36:48Z
Started
2026-11-13 16:36:49Z
Finished
2026-11-13 16:37:29Z
Archive
502 KB
Analysis ID
0304eda9-4b62...

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

No rejected document reads were recorded.

Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

NavigationBrowser-observed HTTP statusRecorded requests
0301Inspect navigation 0 requests
1200Inspect navigation 1 requests
Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type