The domain camilastexmex.com was observed with an HTTP status 200 on 2026-10-11, documenting a successful response at that time. It also utilizes several web technologies including Bootstrap and Google Analytics.
Recorded Evidence
OTX recorded 34 pulses for camilastexmex.com on 2026-10-11. The domain was listed in the PhishDestroy internal catalogue as of 2026-10-11. URLScan reported an available scan for the domain on 2026-10-11. The registration was completed with TUCOWS.COM, CO. on 2018-07-13, and the SSL certificate was issued by Let's Encrypt / YE2.
Interpretation
The OTX source contains a metric called pulses, which documents observed activity or references related to camilastexmex.com. The PhishDestroy internal listing is a catalogue record, representing a publisher-owned entry for the domain. The HTTP status observation measures the domain's recorded response code at a specific date, providing a technical snapshot. The evidence spans several types of records, allowing for comparison of technical and catalogue-based observations.
Recommended Actions
For camilastexmex.com, retain the OTX pulse count, PhishDestroy listing status, and HTTP status code as reference points for future checks. Compare these records with subsequent scans and catalogue entries to track any changes in technical or listing observations. Preserve the URLScan report for additional context in future assessments of the domain.
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: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:00:26 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:26 UTClast content: 2026-10-11 10:00:26 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 23:02:22 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 3.14.223.155.
脅威対応 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.
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 (775 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 (CA):
Criminal Code Section 342.1
Criminal Code Section 380 - Fraud
PIPEDA
Canadian law prohibits computer fraud and unauthorized access.
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.
(CA)
