VirusTotal
6 / 89 engine detections
Відкрити звіт“403 Forbidden”
фішинг: 300radio.com — Доступно · доступ обмежено (HTTP 403). Зведення доказів: VirusTotal 6/89 (CRDF, Forcepoint ThreatSeeker, Gridinsoft, PhishFort…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
6 / 89 engine detections
Відкрити звіт3 community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
300radio.com is on the PhishDestroy blocklist as a suspicious domain. No impersonated brand or specific scheme has been confirmed yet. PhishDestroy first saw it on 2026-09-04, and it was still online on 2026-10-19. The server responds but blocks access, and the page title reads "403 Forbidden".
The "403 Forbidden" title is a server error page with no lure or brand on it, which differs from what the blocklist entry and vendor flags suggest. The risk lies in where the domain could lead. Several independent security vendors, including an anti-phishing specialist, consider it unsafe. A domain flagged this way can later serve a login form, a fake wallet prompt or a download. Any page on 300radio.com that asks for a password, a recovery phrase or a transaction approval should be treated as hostile.
VirusTotal shows 6 of 89 engines flagging the domain as of 2026-09-14. The vendors are CRDF, Forcepoint ThreatSeeker, Gridinsoft, PhishFort, SOCRadar and VIPRE. That is a minority of engines, but they come from separate threat-intelligence sources, and PhishFort focuses on phishing aimed at crypto and brand users. The domain also appears in three AlienVault OTX pulses, so other researchers are tracking it independently. Beyond PhishDestroy, no other blocklist lists it.
The domain was registered on 2026-07-13, about seven weeks before PhishDestroy first saw it. That is a short lifespan, typical of throwaway domains. Hostinger handles both the registration and the hosting, with the server on Hostinger International Limited's network in the US. Its Let's Encrypt certificate means browsers show a padlock, but that only proves the connection is encrypted, not that the site is legitimate.
If you reached 300radio.com through a link, do not return or follow any further redirects. If you entered a password or other login details on any page tied to this domain, change that password wherever you reuse it and turn on two-factor authentication. Never type a recovery phrase or approve a wallet request on a site you reached this way. Defenders should block the domain and its hosting address at the DNS and proxy level. They should also check logs for earlier visits and keep watching it, since the page content may change while the domain stays live.
orbit.dns-parking.comLocation describes the IP network.
59c2e9e8930e4ea4c3dfef66192897714a94f294c6d5982dd6ddd8da7756a3cbwww.300radio.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.300radio.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of 300radio.com · checked Sep 13, 2026
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.
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
Невідомо→protected
http_access_restricted · access_restriction
1→2
3 community references
View sourceNo threat flag
View source6/89 engine detections
View source300radio.com
View source1 повідомлення спільноти
КатегоріяPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-04T14:30:50.604Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
300radio.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
300radio.com)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.