Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 7. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
usrlog-fi.com favicon

usrlog-fi.com

In short

usrlog-fi.com is a phishing page detected by PhishDestroy on 2026-10-25.

“Turvatarkistus”

Review the evidence
Registrar
Name.com
Resolved IP
158.94.208.88
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 7/92 Spamhaus DBL: spam domain Stored blocklist matches: 2
VirusTotal
7 / 92
engine detections ·
OTX
2
community references
Cloudflare Radar
suspicious
source verdict
Page captures
5
open gallery
Domain age
—
Not recorded
Reports sent
—
No sent record
OTX: 2 refs Oct 25, 2026
X Telegram API

Analysis

Domain summary

usrlog-fi.com is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Name.com. Status: Last known active. Hosting: Omegatech LTD. VirusTotal: 7/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
7 / 92
OTX
2 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed usrlog-fi.com as a suspicious domain based on VirusTotal detections from malicious vendors. The domain was first observed by PhishDestroy on 2026-10-25, two days after its registration on 2026-10-23. The recorded page title was “Turvatarkistus”.

How the scam works

A suspicious classification indicates the site could be used for phishing, spam or other fraudulent tactics such as presenting deceptive messages or harvesting credentials, but the captured page showed only a generic title and no concrete malicious content.

Evidence

VirusTotal (retrieved 2026-10-25) reported 7 detections from 92 scanners, labeling the domain malicious by G‑Data and SOCRadar and suspicious by four other vendors. Google Safe Browsing (checked 2026-10-25) found no threat. urlscan.io (captured 2026-10-24) gave an overall clean verdict while its engine flagged the URL as malicious with a high confidence score. External blocklists MetaMask and SEAL listed the domain, and Spamhaus DBL marked it as spam on 2026-10-25. OTX recorded two pulses referencing usrlog-fi.com. PhishDestroy’s internal list added the domain on 2026-10-25.

Infrastructure

The domain was registered with Name.com, Inc. on 2026-10-23 and used the Vercel DNS nameservers ns1.vercel-dns.com and ns2.vercel-dns.com. The recorded IP was 158.94.208.88, belonging to the OMEGATECH‑LTD network (ASN 202412) in Germany. A Let’s Encrypt certificate for usrlog-fi.com was issued on 2026-10-23 and is valid until 2027-01-21, using TLS 1.3. The recorded server header indicated nginx.

What to do

Do not submit login credentials, personal data or cryptocurrency information to usrlog-fi.com. If credentials were entered, change the associated passwords immediately and review account activity for unauthorized access. Defenders should add the exact domain to blocklists, monitor DNS queries for 158.94.208.88, and inspect web proxy logs for requests to the recorded URL path.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T02:05:27Z)URLScan screenshot (2026-10-25T02:02:05Z)URLScan capture reportURLScan screenshot (2026-10-25T02:08:15Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 7 / 92 · OTX 2 references 8 sources

VirusTotal

7 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
49
Malicious
3
Suspicious
4
Undetected
36

Vendor labels

G-Data
phishing
Sophos
spam
Fortinet
spam
SOCRadar
phishing
Gridinsoft
suspicious
alphaMountain.ai
spam
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
spam urls
alphaMountain.ai
Spam, Suspicious (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.vercel-dns.com
  • TTL, seconds
    60
    Type
    CAA
    Value
    pki.goog
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.vercel-dns.com
  • TTL, seconds
    60
    Type
    A
    Value
    158.94.208.88
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    hostmaster.nsone.net
    Value
    ns1.vercel-dns.com
  • TTL, seconds
    60
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    60
    Type
    CAA
    Value
    sectigo.com

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d0000002059a3b916699461c5923779b77cf06b

Certificate

Subject alternative names
  • usrlog-fi.com
Issuer
Let's Encrypt / YR2
Serial
598c76a3c447f93d933731822b6a831a80d
SHA-256
6b787a972841027e988c069c1a6fa7d99c7a275f47fd80e7cef8ea2dea47823d
Subject
usrlog-fi.com
Valid until
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar IANA ID
625
Registrar URL
http://www.name.com
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
DNSSEC
unSigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 3,
    "suspicious": 4,
    "undetected": 36
}
Vendor labels
{
    "G-Data": "phishing",
    "Sophos": "spam",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "spam urls",
    "alphaMountain.ai": "Spam, Suspicious (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Name.com, Inc.
Created
2026-10-23T13:20:05Z
Expires
2027-10-23T13:20:05Z
Updated
2026-10-23T13:20:05Z
First seen
2026-10-23T15:11:21Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.vercel-dns.com"
    },
    {
        "ttl": 60,
        "type": "CAA",
        "value": "pki.goog"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.vercel-dns.com"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "158.94.208.88"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "hostmaster.nsone.net",
        "value": "ns1.vercel-dns.com"
    },
    {
        "ttl": 60,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 60,
        "type": "CAA",
        "value": "sectigo.com"
    }
]
Dns at
2026-10-25T06:34:51Z
Jarm
29d3fd00029d29d00042d43d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "usrlog-fi.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "598c76a3c447f93d933731822b6a831a80d",
    "sha256": "6b787a972841027e988c069c1a6fa7d99c7a275f47fd80e7cef8ea2dea47823d",
    "subject": "usrlog-fi.com",
    "valid_to": "2027-01-21T12:24:31Z",
    "valid_from": "2026-10-23T12:24:32Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2026-10-23T13:20:05Z",
    "updated": "2026-10-23T13:20:05Z",
    "expires": "2027-10-23T13:20:05Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ],
    "dnssec": "unSigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-23T13:20:05Z",
        "last changed": "2026-10-23T13:20:05Z",
        "registration": "2026-10-23T13:20:05Z",
        "registrar expiration": "2027-10-23T13:20:05Z",
        "last update of RDAP database": "2026-10-23T13:20:05Z"
    }
}
Separate source record · 3 malicious + 4 suspicious / 92 · 2026-10-25 06:34:28 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-25T06:34:28Z
fetched_at
2026-10-25T07:52:11Z
stats
{"timeout":0,"harmless":49,"malicious":3,"suspicious":4,"undetected":36}

Cloudflare Radar

Suspicious

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

13365b3e-11b7-460c-807a-a7ba88edc13d

Final URL

https://usrlog-fi.com/

HTTP response

200

Navigation history

  • URL
    https://usrlog-fi.com/
    Status
    200

DOM structure hash

863b0e04b9e8af02d763cb98563ca8d9f80c6b99a3ec2eb6395db229bc3f8ba9

Document hash

587cdc48d51a7732ad2019d0d9099c3d1c50ecbc25083cb607db301422373df1

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    usrlog-fi.com
    Type
    A
    Value
    158.94.208.88

DNSSEC valid

No

IP address

158.94.208.88

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
Original source fields · JSON
Uuid
13365b3e-11b7-460c-807a-a7ba88edc13d
Final url
https://usrlog-fi.com/
Status
200
History
[
    {
        "url": "https://usrlog-fi.com/",
        "status": 200
    }
]
DOM structure hash
863b0e04b9e8af02d763cb98563ca8d9f80c6b99a3ec2eb6395db229bc3f8ba9
Document hash
587cdc48d51a7732ad2019d0d9099c3d1c50ecbc25083cb607db301422373df1
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "usrlog-fi.com",
        "type": "A",
        "value": "158.94.208.88"
    }
]
Dnssec valid
false
Ip
158.94.208.88
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-10-23T13:20:05Z",
    "updated": "2026-10-23T13:20:05Z",
    "expires": "2027-10-23T13:20:05Z",
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ]
}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 99

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a16d24-4bab-7598-a13a-3918f950bc52

Final URL

https://usrlog-fi.com/b08416b8ab36c365e2a2d01fc470a30b

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://usrlog-fi.com/
    From
    http://usrlog-fi.com/
    Status
    307
  • To
    https://usrlog-fi.com/b08416b8ab36c365e2a2d01fc470a30b
    From
    https://usrlog-fi.com/
    Status
    302

IP address

158.94.208.88

Contacted domains

  • www.google.com

Contacted IP addresses

  • 158.94.208.88

Autonomous systems (ASN)

  • 202412

Server countries

  • DE

Document hash

5c2ea5d0a628849583cdf56b70fb2f7e524b6e767204ddc13581ae9b3bd250a7

Cookies

  • PHPSESSID

TLS session and certificate

Subject alternative names
  • usrlog-fi.com
Cipher
AES_128_GCM
Issuer
YR2
Subject
usrlog-fi.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/8.4.27 PleskLin
X-frame-options
DENY
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a16d24-4bab-7598-a13a-3918f950bc52
Final url
https://usrlog-fi.com/b08416b8ab36c365e2a2d01fc470a30b
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://usrlog-fi.com/",
        "from": "http://usrlog-fi.com/",
        "status": 307
    },
    {
        "to": "https://usrlog-fi.com/b08416b8ab36c365e2a2d01fc470a30b",
        "from": "https://usrlog-fi.com/",
        "status": 302
    }
]
Ip
158.94.208.88
Contacted domains
[
    "www.google.com"
]
Contacted IP addresses
[
    "158.94.208.88"
]
Asns
[
    "202412"
]
Countries
[
    "DE"
]
Document hash
5c2ea5d0a628849583cdf56b70fb2f7e524b6e767204ddc13581ae9b3bd250a7
Cookies
[
    "PHPSESSID"
]
Tls
{
    "san": [
        "usrlog-fi.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "usrlog-fi.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-21T12:24:31Z",
    "valid_from": "2026-10-23T12:24:32Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "PHP/8.4.27\nPleskLin",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff"
}
Separate monitor record · 2026-10-25 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a16d24-4bab-7598-a13a-3918f950bc52
score
0
malicious
false
result_at
2026-10-25T04:30:51Z
enriched_at
2026-10-25T09:13:02Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:51","urlscan_enriched_at":"2026-10-25 10:13:02"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

100 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-25T07:55:06Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-25T07:55:06Z
source_timestamp
2026-10-25 08:55:06
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
usrlog-fi.com — Suspicious Domain
ai_description
PhishDestroy flagged usrlog-fi.com as suspicious on 2026-10-25 after VirusTotal flagged it and a page titled “Turvatarkistus”, it marked malicious or suspicious.
ai_generated_at
2026-10-25T07:54:48Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

CAA records

Count
3
Domain
usrlog-fi.com
Allowed issuers
  • sectigo.com
  • letsencrypt.org
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes

Trackers

Requests
2
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
30
TLS
77
Waiting
94
Connection
75
Download
0
Response time, ms
276

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 22
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 993
  • 995

Carbon estimate

Bytes
69
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    198.51.44.13
    Host
    ns1.vercel-dns.com
  • IP address
    198.51.45.13
    Host
    ns2.vercel-dns.com
DNS zone
usrlog-fi.com

Cookies

Cookies
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    SEARCH_SAMESITE
    SameSite
    Strict
  • Name
    AEC
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    __Secure-STRP
    Secure
    Yes
    SameSite
    Strict
  • Name
    NID
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

IP address
158.94.208.88
ASN
202412
Organization
Omegatech LTD
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
usrlog-fi.com

DNS records

A
  • 158.94.208.88
NS
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com
SOA
Primary nameserver
ns1.vercel-dns.com
Hostmaster
hostmaster.nsone.net
Serial
1792761607
Refresh, seconds
43200
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
600

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
No
X-XSS-Protection
0
Permissions-Policy
unload=()
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
same-origin-allow-popups; report-to="gws"
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
158.94.208.88
IP version
4

Redirects

Redirect chain
  • https://usrlog-fi.com
  • https://www.google.com
Count
1

Page links

External link addresses
  • https://about.google/
  • https://store.google.com/DE
  • https://mail.google.com/mail/&ogbl
  • https://www.google.com/imghp
  • https://www.google.de/intl/de/about/products
  • https://accounts.google.com/ServiceLogin
  • https://www.google.com/webhp
  • https://support.google.com/websearch/answer/106230
  • https://www.google.com/intl/de_de/ads/
  • https://www.google.com/services/
  • https://google.com/search/howsearchworks/
  • https://sustainability.google/intl/de/klimaschutz/
  • https://policies.google.com/privacy
  • https://policies.google.com/terms
  • https://www.google.com/preferences
  • https://consent.google.com/d
  • https://support.google.com/websearch/
  • https://policies.google.com/technologies/cookies
  • https://policies.google.com/privacy
  • https://policies.google.com/terms
External links
20
Internal links
3

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

HTTP headers

Response headers
Server
gws
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
Permissions-policy
unload=()
Cross-origin-opener-policy
same-origin-allow-popups; report-to="gws"
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 3,
    "domain": "usrlog-fi.com",
    "issuers": [
        "sectigo.com",
        "letsencrypt.org",
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Trackers
{
    "requests": 2,
    "trackers": [
        {
            "name": "Google",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 302,
    "timings": {
        "dns": 30,
        "tls": 77,
        "wait": 94,
        "connect": 75,
        "download": 0
    },
    "response_ms": 276
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        993,
        995
    ]
}
Carbon
{
    "bytes": 69,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.13",
            "host": "ns1.vercel-dns.com"
        },
        {
            "ip": "198.51.45.13",
            "host": "ns2.vercel-dns.com"
        }
    ],
    "zone": "usrlog-fi.com"
}
Cookies
{
    "cookies": [
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "SEARCH_SAMESITE",
            "same_site": "Strict"
        },
        {
            "name": "AEC",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "__Secure-STRP",
            "secure": true,
            "same_site": "Strict"
        },
        {
            "name": "NID",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "158.94.208.88",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "usrlog-fi.com"
}
DNS records
{
    "A": [
        "158.94.208.88"
    ],
    "NS": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ],
    "SOA": "{\"nsname\": \"ns1.vercel-dns.com\", \"hostmaster\": \"hostmaster.nsone.net\", \"serial\": 1792761607, \"refresh\": 43200, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 600}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": "SAMEORIGIN",
    "referrerPolicy": false,
    "xXSSProtection": "0",
    "permissionsPolicy": "unload=()",
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": "same-origin-allow-popups; report-to=\"gws\"",
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "158.94.208.88",
    "family": 4
}
Redirects
{
    "chain": [
        "https://usrlog-fi.com",
        "https://www.google.com"
    ],
    "count": 1
}
Page links
{
    "external": [
        "https://about.google/",
        "https://store.google.com/DE",
        "https://mail.google.com/mail/&ogbl",
        "https://www.google.com/imghp",
        "https://www.google.de/intl/de/about/products",
        "https://accounts.google.com/ServiceLogin",
        "https://www.google.com/webhp",
        "https://support.google.com/websearch/answer/106230",
        "https://www.google.com/intl/de_de/ads/",
        "https://www.google.com/services/",
        "https://google.com/search/howsearchworks/",
        "https://sustainability.google/intl/de/klimaschutz/",
        "https://policies.google.com/privacy",
        "https://policies.google.com/terms",
        "https://www.google.com/preferences",
        "https://consent.google.com/d",
        "https://support.google.com/websearch/",
        "https://policies.google.com/technologies/cookies",
        "https://policies.google.com/privacy",
        "https://policies.google.com/terms"
    ],
    "external_count": 20,
    "internal_count": 3
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-10-23T13:20:05Z",
    "updated": "2026-10-23T13:20:05Z",
    "expires": "2027-10-23T13:20:05Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.vercel-dns.com",
        "ns2.vercel-dns.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "gws",
        "content-type": "text/html; charset=UTF-8",
        "x-frame-options": "SAMEORIGIN",
        "permissions-policy": "unload=()",
        "cross-origin-opener-policy": "same-origin-allow-popups; report-to=\"gws\""
    }
}

Questions about usrlog-fi.com

Is usrlog-fi.com legit?

No. PhishDestroy classifies usrlog-fi.com as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 7/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is usrlog-fi.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on usrlog-fi.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used usrlog-fi.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://usrlog-fi.com/b08416b8ab36c365e2a2d01fc470a30b
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Name.com SE(SE)
Abuse contact["abuse@name.com", "00b6b0b31deb8c62s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for usrlog-fi.com →
RegistrationExpires Oct 23, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 100/100
Submitted URLhttp://usrlog-fi.com/
Favicon Hash
Observed page title
Turvatarkistus
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
158.94.208.88
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Frankfurt am Main, DE
Server header
nginx

Nameservers 2

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-23 12:24:32
Valid until
2027-01-21 12:24:31
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6b787a972841027e988c069c1a6fa7d99c7a275f47fd80e7cef8ea2dea47823d
Certificate names · 1 SAN
  • usrlog-fi.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 158.94.208.88rapiddns.io

Latest Classified Outcome 2026-10-25 11:00:25 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 11:00:25 UTC
RDAP registration Unknown
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
SOCRadar
Sophos
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of usrlog-fi.com · checked Oct 25, 2026

78
Needs Work
Performance
FCP
2.73 s
First Contentful Paint
LCP
3.52 s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
293 ms
Total Blocking Time
SI
4.09 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://usrlog-fi.com/
Final URL: https://usrlog-fi.com/9bff7c56fcd5c0f470dd3477fb38881c
Turvatarkistus
Response
HTTP 200
HTML body
9.5 KB
Compressed
3.1 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/8.4.27
Cache-Control: no-store, no-cache
Content-Encoding: gzip
Security headers present
X-Frame-OptionsX-Content-Type-Options
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 14
Cache-Control
no-store, no-cache
Connection
keep-alive
Content-Encoding
gzip
Content-Length
3242
Content-Type
text/html; charset=UTF-8
Date
Sun, 25 Oct 2026 01:59:52 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Server
nginx
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
X-Frame-Options
DENY
X-Powered-By
PHP/8.4.27
X-Robots-Tag
noindex, nofollow

Values retained by the collector; long values may be shortened during collection.

Archived
Stored observation history4

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. VirusTotal · Detection count

    0→7

    Engines added
    Forcepoint ThreatSeeker · Fortinet · G-Data · Gridinsoft · SOCRadar · Sophos · alphaMountain.ai
    Engines removed
    None recorded
    Recorded vendor total
    7
  3. VirusTotal · Detection count

    3→Observation retained

    Engines added
    None recorded
    Engines removed
    G-Data · SOCRadar · Sophos
    Recorded vendor total
    0
  4. VirusTotal · Detection count

    5→3

    Engines added
    None recorded
    Engines removed
    Gridinsoft · alphaMountain.ai
    Recorded vendor total
    3
All retained availability observations5

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:25.000000
    Evidence SHA-256
    efdbfd9a819a9bc0d3dc0051669fe967c37fe52e072ed1c57fb5e9446b50898f
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-25 12:00:25
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:25.000000
    Evidence SHA-256
    efdbfd9a819a9bc0d3dc0051669fe967c37fe52e072ed1c57fb5e9446b50898f
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-25 12:00:25
    Evidence reason
    redirect
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 10:06:24.862259
    Evidence SHA-256
    8895fe784317ce956fd87b3c03d7dee28c93bf969fb14b515b4f932e1c762121
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 10:06:24.862259
    Evidence reason
  4. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:17:38.541144
    Evidence SHA-256
    95dedd1e4016ea57e34bdbce51e0ec491a6e3d89d4fb09684d0437765fe8625c
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 10:58:18.229546
    Evidence SHA-256
    5466dc0e4e63428315f23f9df131d80602c351ccc05c3d5f30d3622cc0a8cc70
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 10:58:18.229546
    Evidence reason

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. VirusTotal

    7/92 engine detections

    View source
  3. Added to PhishDestroy

    usrlog-fi.com

    View source
  4. URLScan

    Malicious · engine verdict · score 99

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

usrlog-fi.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 7 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 2 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including usrlog-fi.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/usrlog-fi.com"
  title="PhishDestroy threat report for usrlog-fi.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>