VirusTotal
5 / 92 engine detections
Open report5 / 92 engine detections
Open reportMalicious
Open reportMalicious
Open reportno community references
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
ns2.siteug.comLocation describes the IP network.
399b5f3836e418a8191c271105528ffdc7839963ae92e8b077f5b6f7e0b58343www.eday.item.com.login.secured.karapapati.comSaved 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 eday.item.com.login.secured.karapapati.com · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://eday.item.com.login.secured.karapapati.com/https://eday.item.com.login.secured.karapapati.com/Content-Type: text/html; charset=UTF-8Content-Encoding: gziph3=":443"; ma=2592000, h3-29=":443"; ma=2592000Keep-Alivegzip11383text/html; charset=UTF-8Sat, 17 Oct 2026 17:28:50 GMTtimeout=5, max=100Accept-EncodingValues 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.
dns_inactive→live_content
content_served
4→5
live_content→dns_inactive
dns_nxdomain
13→4
12→13
11→12
10→11
Unknown→live_content
content_served
3→10
2→3
1→2
No threat flag
View source5/92 engine detections
View sourceeday.item.com.login.secured.karapapati.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
eday.item.com.login.secured.karapapati.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 ↗
eday.item.com.login.secured.karapapati.com)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.
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.