VirusTotal
6 / 91 engine detections
Buka laporan“Problem loading page”
Phishing: swiftlane.online — Konten tidak tersedia. Ringkasan bukti: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
6 / 91 engine detections
Buka laporan2 det.
Buka laporanDBL_SPAM
2 community references
Buka laporanprovider verdict: clean
Buka laporan14 diperiksa — tidak ada blokir
No threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain swiftlane.online is currently active and classified as a high‑risk generic phishing site employing brand impersonation tactics. The site was registered on 2026‑02‑03 through Global Domain Group LLC and resolves to IP address 163.61.188.7, which geolocates to the United States (MIT). DNS is served by four LyteHosting nameservers (dns1‑dns4.lytehosting.com). An SSL certificate issued by Let’s Encrypt (YR1) is present, and HTTP requests return a 200 status code. Automated analysis detected the use of Bootstrap, LiteSpeed, GSAP, Swiper, jQuery, and HTTP/3. The page title reported by crawlers is "Problem loading page," and no further content has been publicly disclosed, leaving the exact brand being spoofed unknown. Threat intelligence sources corroborate malicious activity: AlienVault OTX lists the domain in two separate pulses, and VirusTotal records detections from two of ninety‑one scanned security vendors. The domain is already blocked by PhishDestroy and appears on one external blocklist. Defenders should block the domain at the DNS and proxy layers, monitor outbound connections to 163.61.188.7, and treat any credential or payment requests originating from this URL as fraudulent. Continued surveillance is advised to detect any evolution of the payload or target brand.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
dns1.lytehosting.comdns2.lytehosting.comdns3.lytehosting.comdns4.lytehosting.comLocation describes the IP network.
86575593ddf259cd687e247c93152e9cc209f069bbe2fa294b7fb7aeb5396bcfSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of swiftlane.online · checked Jul 1, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='swiftlane.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
swiftlane.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Dapat dijangkau→Tidak tersedia
1→2
6/91 engine detections
View sourceNo threat flag
View sourcePD-20260701-6240AE
2 community references
View sourceswiftlane.online
View sourcePage captured
View sourcePD-20260701-6240AE Recipient: abuse@whiteprivacy.com Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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 ↗
swiftlane.online)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan 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.