4k7e[.]com
Phishing- und Sicherheitsprüfung für 4k7e.com
“TikTok-shop”
4k7e.com — Nicht bestätigt. Markenidentität: TikTok; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 18/91 (alphaMountain.ai, BitDefender, Cluster25, CRDF, ESET); URLQuery 4 alerts; CF Radar malicious; PhishDestroy score 95/100. Registrar: Dynadot.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
Assessment
Stored evidence for 4k7e.com: VirusTotal recorded 18 detections among 91 scanners on 2026-08-09. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for 4k7e.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 18 detections among 91 scanners in the stored snapshot dated 2026-08-09. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-09 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish are recorded as named external blocklist observations for 4k7e.com in the snapshot dated 2026-08-09. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains 4k7e.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed 4k7e.com on 2026-08-09. The OpenPhish blocklist snapshot is dated 2026-08-09 and remains a separate event in the stored timeline. The registration date is separately recorded as 2025-12-10. A URLScan reference was stored on 2026-08-09 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The record lists Dynadot Inc as the registrar for 4k7e.com. The source stores 45.203.220.45 as the observed address for 4k7e.com. The registration date for 4k7e.com is recorded as 2025-12-10. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The 4k7e.com record states that VirusTotal recorded 18 detections among 91 scanners on 2026-08-09. OpenPhish remain named blocklist observations from the snapshot dated 2026-08-09. PhishDestroy remains a separate publisher catalogue entry in the stored record. Dynadot Inc is presented only as the recorded registrar, while 45.203.220.45 is presented only as the observed address. The supported conclusion is bounded to the exact stored observations for 4k7e.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Use a known service address obtained separately from this report and avoid submitting sensitive information to 4k7e.com during review. Defenders can retain the exact 4k7e.com hostname as an indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to 4k7e.com; the stored record does not justify extending that rule to 45.203.220.45 or the Dynadot Inc registrar record.
Erkenntnisse zur Netzwerksicherheit
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | 4k7e.com |
malicious | Sinkholed |
| OpenDNS | 4k7e.com |
phishing | Phishing Block |
| DNS4EU | 4k7e.com |
malicious | Sinkholed |
| Cloudflare DNS | 4k7e.com |
malicious | Sinkholed |
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
Gespeicherte Aufnahme
Domain-Intelligenz
Technische DetailsDNS, SSL-SANs, Zeitstempel
ICANN OVERSIGHT
Akkreditierung und RAA-Kontext
Akkreditierung und RAA-Kontext
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Technologien · 4 identified
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
vuejs.org 100 % KonfidenzNginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
nginx.org 100 % KonfidenzHTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
www.rfc-editor.org 100 % KonfidenzHTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
httpwg.org 100 % KonfidenzVirusTotal-Analyse
Archivierte Beweise
Website-Performanceanalyse
Google PageSpeed Insights — mobile performance audit of 4k7e.com · checked Aug 9, 2026
Nachweise und externe Berichte
PD-20260809-8F1290 Recipient: abuse@dynadot.com Wurden Sie von dieser Website betroffen?
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Melden Sie sich bei Ihren örtlichen Behörden
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Jede beliebige Domain prüfen
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenPhishing melden
Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenEchtzeit-Bedrohungsfeed
Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBleiben Sie auf dem Laufenden, bleiben Sie sicher
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt