PhishDestroy forensic analysis flagged this domain. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 28 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
The domain leotravels.in returned an HTTP status 200 on 2026-10-11, documenting a successful server response at that time. The record also notes the use of nginx/1.25.5 as the observed server header.
Recorded Evidence
On 2026-10-11 the domain leotravels.in appeared in the PhishDestroy internal listing. OTX recorded 34 pulses for leotravels.in on the same date. URLScan reported an available scan for the domain on 2026-10-11. The domain was registered with GoDaddy on 2018-05-06 and its SSL certificate was issued by Let's Encrypt / YR2.
Interpretation
The PhishDestroy internal listing contains a publisher-owned entry for leotravels.in, serving as a catalogue reference. The HTTP status source documents a technical response measurement. OTX records the domain's appearance in its intelligence pulse count. These sources provide distinct types of records for comparison.
Recommended Actions
For leotravels.in preserve the PhishDestroy internal listing and OTX pulse count as reference points for future reviews. Retain the HTTP status 200 record to compare with subsequent technical measurements. Use the URLScan report as an additional reference for monitoring infrastructure changes.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
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 observationLive contentOrdinary HTTP content served90%2026-10-11 22:00:42 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 22:00:42 UTClast content: 2026-10-11 22:00:42 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-11 01:17:29 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 103.211.216.141.
Threat Response Pipeline
Discovery
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.
Threat Ingested
leotravels.in detected and queued for full analysis
The domain remains reachable or access-restricted; future checks may update this observation.
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.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · leotravels.in
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(IN)
