On 2026-10-01, dulcineatravel.com returned an HTTP 404 status code, a recorded response indicating the requested page was not found. The domain also appears in the PhishDestroy internal catalogue, and its registration date is recorded as 2025-12-04.
Recorded Evidence
The registrar for dulcineatravel.com is recorded as NameCheap, Inc., with registration on 2025-12-04. VirusTotal recorded 16 detections out of 89 scanners on 2026-09-17. OTX recorded 5 pulses on 2026-09-17. The domain resolved to IP address 178.16.54.253, located in NL under Omegatech LTD, and a PageSpeed check on 2026-09-15 returned a performance score of 100.
Interpretation
The HTTP 404 response and the PhishDestroy catalogue entry are separate records with different dates, so they should be compared rather than merged. The VirusTotal and OTX observations share a calendar date, but that alone does not establish simultaneous measurement or direct comparability. The PageSpeed score describes a performance measurement, not a security judgment. These records describe only what each named source reported on its own date.
Recommended Actions
Preserve the VirusTotal, OTX, and PhishDestroy records for dulcineatravel.com so future scans can be compared against them. Compare the HTTP status record with later responses to see whether the recorded code changes. Review the PhishDestroy catalogue entry alongside the other source records when assessing the domain. Keep each source's observations separate when documenting findings.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dulcineatravel.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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-13 01:16:37 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-07 20:28: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.
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of dulcineatravel.com· checked Sep 15, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.97s
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.
Domain Status Transition2026-09-15 22:00:21 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 20:03:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 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.
(US)
