Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
On 2026-10-07, jaipurvanchal.com was checked by VirusTotal and found to have zero detections among 92 scanners. The same day, a PageSpeed performance score of 83 was also recorded for this domain, reflecting a specific measurement of its web performance.
Recorded Evidence
VirusTotal reported zero detections out of 92 scanners for jaipurvanchal.com on 2026-10-07. OTX included the domain in four pulses as of 2026-10-07. The domain appeared in the internal PhishDestroy listing on 2026-10-07. Registration was recorded with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-09-25, and an SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-10-07.
Interpretation
The records from VirusTotal, OTX, and PhishDestroy provide details on how jaipurvanchal.com was observed by different monitoring services on 2026-10-07. These sources offer information about the domain's scan results, inclusion in monitoring lists, and technical setup on the dates specified.
Recommended Actions
To facilitate future assessments of jaipurvanchal.com, retain the VirusTotal, OTX, and PhishDestroy records for comparison. It is also practical to preserve the PageSpeed and SSL certificate observations for tracking any changes in performance or configuration.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Active
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-14 02:42:21 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-09-25 10:07:06 UTCchecked 2026-10-09 04:32:58 UTC
Observed timelinelast reachable: 2026-10-14 02:42:21 UTClast content: 2026-10-14 02:42:21 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.
Google PageSpeed Insights — mobile performance audit of jaipurvanchal.com· checked Oct 7, 2026
83
Needs Work
Performance
FCP
3.04s
First Contentful Paint
LCP
3.04s
Largest Contentful Paint
CLS
0.138
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.11s
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.
Threat First Observed2026-10-07 14:51:07 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.137.167.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(RU)
PhishDestroy Investigation
