VirusTotal
15 / 92 engine detections
Open report“Parking Page”
15 / 92 engine detections
Open report2 det.
Open reportMalicious
Open report4 community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy listed antalya-transfer.org as a suspicious domain after intake flagged it due to multiple malicious detections on VirusTotal and a client‑side redirect to an external site. The domain was first seen by PhishDestroy on 2026-10-21. The recorded page title is “Parking Page” and the HTTP response on that date returned status 200 with a client redirect to the external site.
Domains that display a placeholder or parking page and then automatically redirect visitors are commonly used for traffic monetization, affiliate abuse, or as a stepping stone for phishing campaigns. No credential capture, wallet interaction, or other malicious payload was observed on the fetched page.
VirusTotal analysis on 2026-10-18 (retrieved 2026-10-21) reported 13 malicious and 2 suspicious detections out of 92 engines, with vendors such as Fortinet, Kaspersky and Sophos labeling it phishing or malicious. Google Safe Browsing checked on 2026-10-21 did not flag the domain. urlscan capture on 2026-10-21 showed the final URL remained the original domain, returned HTTP 200, its engine verdict gave a malicious score of 66 while the overall rating was non‑malicious. OTX listed four pulses referencing the domain as of 2026-10-21. External DNS blocklists recorded one hit among twelve resolvers, and PhishDestroy’s internal blocklist marks the domain as suspicious.
The domain was registered with Spaceship, Inc. on 2023-10-01. Hosting records show it resolved to IP 44.233.250.75, part of the Amazon.com, Inc. network located in the United States.
Users should avoid clicking links to antalya-transfer.org and should not submit credentials or personal information to the site. If any credentials were entered, change them promptly. Defenders should block the exact hostname at firewalls or proxy filters and monitor access logs for requests to this domain.
launch1.spaceship.netlaunch2.spaceship.netLocation describes the IP network.
c48249886be0276b034ab76493cc21e60acb1847c04295c2338fd54d4fc284eaantalya-transfer.orgSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://antalya-transfer.org/Server: openresty/1.31.1.1Content-Type: text/htmlContent-Encoding: gzipkeep-alivegzipframe-ancestors 'self'text/htmlWed, 21 Oct 2026 02:53:29 GMTW/"bde668a7c38f0d2256aaf5038893734b"Tue, 13 Oct 2026 11:14:20 GMTstrict-origin-when-cross-originopenresty/1.31.1.1max-age=31536000; includeSubDomains; preloadchunkedAccept-EncodingQY6V3xlwIljEtbvmReA7UNNhIpd092l.HITnosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
4 community references
View sourceNo threat flag
View source15/92 engine detections
View sourcePD-20261021-134C2D
antalya-transfer.org
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
antalya-transfer.org
PD-20261021-134C2D Recipient: abuse@spaceship.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
antalya-transfer.org)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.