jaymarutidada.com was observed in a security context on 2026-10-14, with Google Safe Browsing recording a social engineering classification on that date. The domain was also referenced in external blocklist entries from PhishFeed, providing additional context for its security profile.
Recorded Evidence
VirusTotal recorded 4 detections out of 92 scanners for jaymarutidada.com on 2026-10-14. OTX documented 3 pulses referencing the domain on the same date. PhishDestroy included jaymarutidada.com in its internal listing, and the domain registration date is recorded as 2014-10-31 by PDR Ltd. d/b/a PublicDomainRegistry.com.
Interpretation
PhishDestroy contains an internal listing for jaymarutidada.com, which documents its presence in a security monitoring system. VirusTotal provides a measurement of detections from multiple scanners, offering insight into how the domain was evaluated by various security tools. The evidence from OTX and PhishFeed adds further context by documenting external blocklist entries and intelligence records. The timeline of observations, all dated 2026-10-14, enables direct comparison of these records.
Recommended Actions
For jaymarutidada.com, preserve the VirusTotal detection records and Google Safe Browsing classification for ongoing review. Compare the PhishDestroy internal listing and OTX pulse references to external blocklist entries such as PhishFeed for a comprehensive assessment. Retain these source records for future monitoring and reference against new observations.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-14 19:30:50 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 19:30:50 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.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
DNS8
Gridinsoft
SOCRadar
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://jaymarutidada.com/yingin
Final URL:http://jaymarutidada.com/yingin/
Sign In to Get Started
响应 HTTP 200
HTML body 416.3 KB
Compressed 52.4 KB
Links 0 internal · 9 external
Detected technologies
jqueryvueapacheangular
Selected response headers
Server: Apache
Content-Encoding: gzip
Content-Type: text/html
HSTS: not observedDNSSEC: not observedWAF / firewall: observedCloaking flag: not observed
Saved response-header values · 10
Accept-Ranges
bytes
Connection
Keep-Alive
Content-Encoding
gzip
Content-Type
text/html
Date
Wed, 14 Oct 2026 19:28:21 GMT
Keep-Alive
timeout=5, max=74
Last-Modified
Sun, 03 Aug 2025 21:09:57 GMT
Server
Apache
Transfer-Encoding
chunked
Vary
Accept-Encoding
Values retained by the collector; long values may be shortened during collection.
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.
Status Check2026-10-14 19:28:25 UTC
Telemetry event observed.
Threat First Observed2026-10-14 19:28:14 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 207.174.212.247.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
9 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.
PDF notice generated Notice text archived (846 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (IN):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and IN's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(IN)
