VirusTotal
14 / 91 engine detections
Bericht öffnen“DHL Livraison | US”
updthl.lat — Inhalt nicht verfügbar. Markenidentität: DHL; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft); URLScan malicious verdict; Google Safe Browsing flagged; CF Radar malicious; PhishDestroy score 100/100. Registrar: Porkbun.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
14 / 91 engine detections
Bericht öffnenSchädlich
Bericht öffnenThreat flag recorded
Bericht öffnenSchädlich
Bericht öffnen1 community reference
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
Stored evidence for updthl.lat: VirusTotal recorded 14 detections among 91 scanners on 2026-09-29. 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 updthl.lat. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 14 detections among 91 scanners in the stored snapshot dated 2026-09-29. 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-09-29 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.
OpenPhish are recorded as named external blocklist observations for updthl.lat in the snapshot dated 2026-09-29. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains updthl.lat 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.
The record first observed updthl.lat on 2026-09-29. The OpenPhish blocklist snapshot is dated 2026-09-29 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-25. 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.
For updthl.lat, the registrar field records Porkbun LLC; this is kept as an exact source value. The source stores 192.142.45.219 as the observed address in this record. The registration date for updthl.lat is recorded as 2026-09-25. 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.
The updthl.lat record states that VirusTotal recorded 14 detections among 91 scanners on 2026-09-29. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-29. PhishDestroy remains a separate publisher catalogue entry in the stored record. For updthl.lat, the registrar field records Porkbun LLC; this remains separate from the other source fields. The observed address field in this record contains 192.142.45.219. The supported conclusion is bounded to the exact stored observations for updthl.lat. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to updthl.lat during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain updthl.lat as an exact 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 updthl.lat. The stored record does not justify extending that rule to 192.142.45.219 or to other infrastructure records.
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.
curitiba.ns.porkbun.comfortaleza.ns.porkbun.commaceio.ns.porkbun.comsalvador.ns.porkbun.comLocation describes the IP network.
6e788e24b3392bd6803077486fb04f44dfecf569de1bdd08e53c7acbbeced1b4www.updthl.latSaved 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.updthl.latDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of updthl.lat · checked Sep 29, 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.
updthl.lat
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
Unbekannt→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Erreichbar→Nicht verfügbar
No flag recorded→Flag recorded
Page captured
View source1 community references
View sourceThreat flag recorded
View source14/91 engine detections
View sourceupdthl.lat
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
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.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
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 ↗
updthl.lat)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
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
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
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.