Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 5/92 engines flagged. malicious: 3. suspicious: 2. Analysis time (as stored): 2026-10-31T11:18:07Z. Retrieved (as stored): 2026-11-01T03:11:13Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Redirect recorded nevaldki.netfisios2-quo9.sbs +2 more Details
Domain security and threat intelligence
nevaldki.net favicon

nevaldki.net

In short

The captured page is a German-language landing page for Nevald KI, presenting itself as an intelligent algo-trading platform. Its headline invites visitors to redefine the status quo with Nevald KI, supported by a short paragraph about transforming conventional paradigms into disruptive growth architectures. Two buttons, "Ecosystem entdecken" and "Unsere Vision", offer the main interactions, while a row of figures below highlights 180+ global markets, a 12x scaling factor, and 99.9% system stability.

“Nevald KI: Intelligente Algo-Trading-Plattform”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Sweden88.80.24.133Fredrik Holmqvist · CDN
Registered
Jul 26, 2026
First observed
Nov 1, 2026
PhishDestroy assessment Critical
95/100
Evidence score
First observed Nov 1, 2026 03:03 UTC · PhishDestroy
Risk signals
VirusTotal detections: 5/92 Spamhaus DBL: spam domain
VirusTotal
5 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 78
Cloudflare Radar
Scam
Page captures
7
open gallery
Domain age
104 days
registered 2026-07-26 according to WHOIS
OTX: 1 ref Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded nevaldki.net on 2026-11-01. Stored VirusTotal result: 5/92 engines flagged. malicious: 3. suspicious: 2. Analysis time (as stored): 2026-10-31T11:18:07Z. Retrieved (as stored): 2026-11-01T03:11:13Z. Risk: critical (95/100). Registrar: Dynadot. Hosting: Fredrik Holmqvist. Do not enter credentials or connect a wallet.

Critical
VirusTotal
5 / 92
Hosting
Sweden88.80.24.133Fredrik Holmqvist · CDN
Registrar
United StatesDynadot
Registered
Jul 26, 2026
OTX
1 community ref
Page captures
7
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-01T03:19:21Z
SHA-256: f3a3c05436fb7105c1ac03263c1d6acbae5a09ca136a8cefcc89b6df654ffc9f

PhishDestroy analysis, reviewed version

The captured page is a German-language landing page for Nevald KI, presenting itself as an intelligent algo-trading platform. Its headline invites visitors to redefine the status quo with Nevald KI, supported by a short paragraph about transforming conventional paradigms into disruptive growth architectures. Two buttons, "Ecosystem entdecken" and "Unsere Vision", offer the main interactions, while a row of figures below highlights 180+ global markets, a 12x scaling factor, and 99.9% system stability.

The stored VirusTotal domain result reports 5 detections out of 92 engines. DNS8 reported "suspicious"; VIPRE reported "phishing".

Source evidenceVirusTotal 5 / 92 · OTX 1 references 8 sources

VirusTotal

5 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
3
Suspicious
2
Undetected
31

Vendor labels

DNS8
suspicious
VIPRE
phishing
SOCRadar
phishing
Gridinsoft
suspicious
alphaMountain.ai
malicious

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.nevaldki.net
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    88.80.24.133

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.nevaldki.net
  • nevaldki.net
Issuer
Let's Encrypt / YE2
Serial
5f91b505eb1710f3859aacb210d04643ac1
SHA-256
1df0c56373257f35566eca2e9f0babf88a27ac8f210083cac49b4c2daefdc6f2
Subject
nevaldki.net
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
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": 56,
    "malicious": 3,
    "suspicious": 2,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "VIPRE": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-07-26T08:22:33Z
Expires
2027-07-26T08:22:33Z
Updated
2026-08-13T12:29:55Z
First seen
2026-07-26T09:09:10Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.nevaldki.net",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "88.80.24.133"
    }
]
Dns at
2026-10-31T11:25:38Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.nevaldki.net",
        "nevaldki.net"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5f91b505eb1710f3859aacb210d04643ac1",
    "sha256": "1df0c56373257f35566eca2e9f0babf88a27ac8f210083cac49b4c2daefdc6f2",
    "subject": "nevaldki.net",
    "valid_to": "2027-01-28T07:08:51Z",
    "valid_from": "2026-10-30T07:08:52Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-07-26T08:22:33Z",
    "updated": "2026-08-13T12:29:55Z",
    "expires": "2027-07-26T08:22:33Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-07-26T08:22:33Z",
        "last changed": "2026-10-30T08:07:36Z",
        "registration": "2026-07-26T08:22:33Z",
        "registrar expiration": "2027-07-26T08:22:33Z",
        "last update of RDAP database": "2026-10-30T08:10:05Z"
    }
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
19
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Chong Lua Dao","CRDF","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Lionic","Netcraft","PREBYTES","Seclookup","SOCRadar","Sophos","VIPRE"]
observed_at
null
checked_at
2026-11-05 04:06:13
fetched_at
2026-11-05 03:06:14
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Scam

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

4ddaddf7-778a-4054-989e-24b7099e08bc

Final URL

https://nevaldki.net/

HTTP response

200

Navigation history

  • URL
    https://nevaldki.net/
    Status
    200

DOM structure hash

30a7269664c88cff69477b5aba45e4d554c5699feaddc34c092555b4ca867412

Document hash

d1add2ed28603e693c7064a465e2efa6efb1dced45461f4d87d218b47c9dacb6

URL risk categories

  • Scam

Domain risk categories

  • Scam
  • Security threats
  • Malware
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    nevaldki.net
    Type
    A
    Value
    88.80.24.133

DNSSEC valid

No

IP address

127.0.1.14

127.0.1.14 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
Original source fields · JSON
Uuid
4ddaddf7-778a-4054-989e-24b7099e08bc
Final url
https://nevaldki.net/
Status
200
History
[
    {
        "url": "https://nevaldki.net/",
        "status": 200
    }
]
DOM structure hash
30a7269664c88cff69477b5aba45e4d554c5699feaddc34c092555b4ca867412
Document hash
d1add2ed28603e693c7064a465e2efa6efb1dced45461f4d87d218b47c9dacb6
Url risks
[
    "Scam"
]
Domain risks
[
    "Scam",
    "Security threats",
    "Malware",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "nevaldki.net",
        "type": "A",
        "value": "88.80.24.133"
    }
]
Dnssec valid
false
Ip
127.0.1.14

127.0.1.14 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-07-26T08:22:33Z",
    "updated": "2026-08-13T12:29:55Z",
    "expires": "2027-07-26T08:22:33Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 78

SHA-256 00ebc80f0bff13359fcb7fa43d898cd6e80ffe19b0ceeb0859c358cba51fb9cd

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1951e-5081-738a-b631-2454d0ac54dd

Final URL

https://nevaldki.net/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://nevaldki.net/
    From
    http://nevaldki.net/
    Status
    307

IP address

88.80.24.133

Contacted IP addresses

  • 88.80.24.133

Autonomous systems (ASN)

  • 33837

Server countries

  • SE

Document hash

a377860a55f8c86ffbb727aaa03b359feb41debb9888bd813525b289d0d1fd68

Script hashes

  • 8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce

JavaScript globals

  • __dclq
  • __dclOrig
  • __dclFlush
  • __smsCheckBeforeSubmit
  • __isSmsEnabled
  • __isSmsVerified
  • intlTelInput
  • navToggle
  • mobileNav
  • langBtn
  • langDropdown

Cookies

  • connect.sid

TLS session and certificate

Subject alternative names
  • *.nevaldki.net
  • nevaldki.net
Cipher
AES_128_GCM
Issuer
YE2
Subject
nevaldki.net
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

97

Registered domain age, days

97

Certificate age, days

1

Certificate validity, days

89

Page requests

5

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
same-origin
Via
1.1 Caddy
Original source fields · JSON
Uuid
01a1951e-5081-738a-b631-2454d0ac54dd
Final url
https://nevaldki.net/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://nevaldki.net/",
        "from": "http://nevaldki.net/",
        "status": 307
    }
]
Ip
88.80.24.133
Contacted IP addresses
[
    "88.80.24.133"
]
Asns
[
    "33837"
]
Countries
[
    "SE"
]
Document hash
a377860a55f8c86ffbb727aaa03b359feb41debb9888bd813525b289d0d1fd68
Script hashes
[
    "8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
]
Globals
[
    "__dclq",
    "__dclOrig",
    "__dclFlush",
    "__smsCheckBeforeSubmit",
    "__isSmsEnabled",
    "__isSmsVerified",
    "intlTelInput",
    "navToggle",
    "mobileNav",
    "langBtn",
    "langDropdown"
]
Cookies
[
    "connect.sid"
]
Tls
{
    "san": [
        "*.nevaldki.net",
        "nevaldki.net"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "nevaldki.net",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-28T07:08:51Z",
    "valid_from": "2026-10-30T07:08:52Z"
}
Domain age days
97
Apex age days
97
Tls age days
1
Tls valid days
89
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 78,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin",
    "via": "1.1 Caddy"
}

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report

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
nevaldki.net: Nevald KI algo-trading landing page
ai_description
PhishDestroy records the German-language Nevald KI landing page captured on nevaldki.net, promoting AI-driven trading automation.
ai_summary
The captured page is a German-language landing page for Nevald KI, presenting itself as an intelligent algo-trading platform. Its headline invites visitors to redefine the status quo with Nevald KI, supported by a short paragraph about transforming conventional paradigms into disruptive growth architectures. Two buttons, "Ecosystem entdecken" and "Unsere Vision", offer the main interactions, while a row of figures below highlights 180+ global markets, a 12x scaling factor, and 99.9% system stability. The stored VirusTotal domain result reports 5 detections out of 92 engines. DNS8 reported "suspicious"; VIPRE reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 04:20:47
revision
f0aef4c086a3da6889d7cf1b655fd417129a9f9fcd3ca6292e9f8348ccfbe4ed
mode
reviewed
interpretation
Selected public package; text generation time is separate from source 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: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
nevaldki.net

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://nevaldki.net/sitemap.xml

Sitemap

Present
Yes
URL count
5

Page title and metadata

Page title
Nevald KI: Intelligente Algo-Trading-Plattform
Indexing directives
index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1
Description
Globale Märkte. Maximale Effizienz. Nevald KI liefert KI-gestützte Handelsautomatisierung mit 180+ Märkten und bewährter Systemstabilität von 99,9 %.
Canonical URL
https://nevaldki.net/

Trackers

Requests
4

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
354
TLS
113
Waiting
56
Connection
60
Download
108
Response time, ms
691

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
92689
CO₂, grams
0.0034
Cleaner than, %
24

DNS servers

Nameservers
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
DNS zone
nevaldki.net

Cookies

Cookies
  • Name
    connect.sid
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax

Location

IP address
88.80.24.133
ASN
33837
Organization
Fredrik Holmqvist
City
Stockholm
Country
SE

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
nevaldki.net

DNS records

A
  • 88.80.24.133
NS
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.nevaldki.net
Serial
2026103002
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
same-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
88.80.24.133
IP version
4

Redirects

Redirect chain
  • https://nevaldki.net

Page links

Internal links
29

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
same-origin
Via
1.1 Caddy
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "nevaldki.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://nevaldki.net/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5
}
Page title and metadata
{
    "title": "Nevald KI: Intelligente Algo-Trading-Plattform",
    "robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
    "description": "Globale Märkte. Maximale Effizienz. Nevald KI liefert KI-gestützte Handelsautomatisierung mit 180+ Märkten und bewährter Systemstabilität von 99,9 %.",
    "canonicalUrl": "https://nevaldki.net/"
}
Trackers
{
    "requests": 4
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 354,
        "tls": 113,
        "wait": 56,
        "connect": 60,
        "download": 108
    },
    "response_ms": 691
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 92689,
    "co2_grams": 0.0034,
    "cleaner_than": 24
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "nevaldki.net"
}
Cookies
{
    "cookies": [
        {
            "name": "connect.sid",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "88.80.24.133",
    "asn": "33837",
    "org": "Fredrik Holmqvist",
    "city": "Stockholm",
    "country": "SE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "nevaldki.net"
}
DNS records
{
    "A": [
        "88.80.24.133"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.nevaldki.net\", \"serial\": 2026103002, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "same-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "88.80.24.133",
    "family": 4
}
Redirects
{
    "chain": [
        "https://nevaldki.net"
    ]
}
Page links
{
    "internal_count": 29
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-07-26T08:22:33Z",
    "updated": "2026-08-13T12:29:55Z",
    "expires": "2027-07-26T08:22:33Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin",
        "via": "1.1 Caddy"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Malware Scam Malware
View full Cloudflare Radar report

Questions about nevaldki.net

Is nevaldki.net legit?

PhishDestroy rates nevaldki.net as critical risk (95/100) from the recorded evidence; it was first recorded on 2026-11-01. Stored VirusTotal result: 5/92 engines flagged. malicious: 3. suspicious: 2. Analysis time (as stored): 2026-10-31T11:18:07Z. Retrieved (as stored): 2026-11-01T03:11:13Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is nevaldki.net safe to connect a wallet?

This report does not record which wallet requests nevaldki.net makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used nevaldki.net?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

URLScan · 2026-11-01 1 / 7
SourceURLScan · 2026-11-01
Recorded
StateStored capture
HTTP status200
Final URLhttps://nevaldki.net/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 78 report ↗
IP Context Sweden88.80.24.133 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dynadot US(US)
Abuse contactabuse@dcs.net, abuse@prq.se, abuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for nevaldki.net →
RegistrationCreated Jul 26, 2026 (104d) — Expires Jul 26, 2027
WHOIS statusclientTransferProhibited
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1003 brand signals
Submitted URLhttp://nevaldki.net/
Favicon Hash
Observed page title
Nevald KI: Intelligente Algo-Trading-Plattform
Automated brand references
Signal Synapse Zelle
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 81 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Sweden88.80.24.133
Network ASN
AS33837
Organization
Fredrik Holmqvist
Observed location
SwedenStockholm, SE
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.nevaldki.net
  • serial: 2026103002
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-30 07:08:52
Valid until
2027-01-28 07:08:51
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1df0c56373257f35566eca2e9f0babf88a27ac8f210083cac49b4c2daefdc6f2
Certificate names · 2 SANs
  • *.nevaldki.net
  • nevaldki.net

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

viewdns.info · 88.80.24.133rapiddns.io
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.nevaldki.netDomain record
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
DNS8
VIPRE
SOCRadar
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of nevaldki.net · checked Nov 1, 2026

100
Good
Performance
FCP
0.95 s
First Contentful Paint
LCP
0.95 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.72 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://nevaldki.net/
Final URL: https://nevaldki.net/
Nevald KI: Intelligente Algo-Trading-Plattform
Globale Märkte. Maximale Effizienz. Nevald KI liefert KI-gestützte Handelsautomatisierung mit 180+ Märkten und bewährter Systemstabilität von 99,9 %.
Response
HTTP 200
HTML body
90.5 KB
Compressed
20.9 KB
Links
71 internal · 0 external
Selected response headers
Cache-Control: private, no-store
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 12
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
private, no-store
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 01 Nov 2026 03:12:11 GMT
Etag
W/"16a11-JQI8xV88KnRaHAMx/aynCEkJJWQ"
Referrer-Policy
same-origin
Transfer-Encoding
chunked
Vary
Cookie
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Directa-Origin
prq-1576

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

Archived
Registration & observation details2

Availability observations

Last reachable observation
Last content observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 5 SHA-256 hashes: 5 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-01 03:25 UTC.

Open this scan on URLScan 01a1951e-5081-738a-b631-2454d0ac54dd ↗

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Domain monitor · First collection record

    Reachable

All retained availability observations26

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_probeunknown
    Observation source
    current_http_probe
    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-11-08 00:12:08.000000
    Evidence SHA-256
    21c5b718b7eb477a5d686eeba8c14fc487f19958a8deda95b68ece9f93ec4e23
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-08 00:12:08
    Evidence reason
    unavailable
  2. current_http_probeunknown
    Observation source
    current_http_probe
    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-11-07 12:10:43.000000
    Evidence SHA-256
    1dc64b4ffbf013662589f5462bd6b7be4f3c5faa6d36e6239ba56cd01eca40f1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 12:10:43
    Evidence reason
    unavailable
  3. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-11-07 12:10:43.000000
    Evidence SHA-256
    1dc64b4ffbf013662589f5462bd6b7be4f3c5faa6d36e6239ba56cd01eca40f1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 12:10:43
    Evidence reason
    unavailable
  4. current_http_probeunknown
    Observation source
    current_http_probe
    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-11-07 03:49:51.000000
    Evidence SHA-256
    8b73e205fd90d83611ca9ca33cb54ab5d58178d9d98f792350cb96b9f8dddcde
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 03:49:51
    Evidence reason
    unavailable
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-11-07 03:49:51.000000
    Evidence SHA-256
    8b73e205fd90d83611ca9ca33cb54ab5d58178d9d98f792350cb96b9f8dddcde
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 03:49:51
    Evidence reason
    unavailable
  6. current_http_probeunknown
    Observation source
    current_http_probe
    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-11-07 00:00:46.000000
    Evidence SHA-256
    f6481949917dcecbcb77d0fd87165f68d83ea4f58f18df547bccf3b9e8a43aaa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 00:00:46
    Evidence reason
    unavailable
  7. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-11-07 00:00:46.000000
    Evidence SHA-256
    f6481949917dcecbcb77d0fd87165f68d83ea4f58f18df547bccf3b9e8a43aaa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 00:00:46
    Evidence reason
    unavailable
  8. 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-11-06 23:21:40.556826
    Evidence SHA-256
    2071dfbc1c6ae55fbd72318bd0bd5b8ac6720ae3a22d4fd33ac3fef7bf7b47da
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 23:21:40.556826
    Evidence reason
  9. 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-11-05 23:21:20.401484
    Evidence SHA-256
    6561edb8793c530bd35b9930c0ef92bee67e8e1395a2c6e53ebfe984a32e4303
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 23:21:20.401484
    Evidence reason
  10. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-05 00:59:05.000000
    Evidence SHA-256
    14aa3174c75cbf9f69a7f2e11900ed230530311cb2909389a3e120ba96f937d1
    Evidence timestamp as recorded
    2026-11-05 00:59:05
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  11. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-11-05 00:59:05.000000
    Evidence SHA-256
    911dfb2af63f443dce3a66bcda2902ec20bc5f21eae1f34a5d4e430a020a22c7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 00:59:05
    Evidence reason
    unavailable
  12. 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-11-04 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    Evidence reason
  13. current_http_probeunknown
    Observation source
    current_http_probe
    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-11-04 12:58:09.000000
    Evidence SHA-256
    ece8a9bfc6233ca96cb0f54ea0875406663104636b456397986dc4841c463831
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 12:58:09
    Evidence reason
    unavailable
  14. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-11-04 12:58:09.000000
    Evidence SHA-256
    ece8a9bfc6233ca96cb0f54ea0875406663104636b456397986dc4841c463831
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 12:58:09
    Evidence reason
    unavailable
  15. 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-11-03 23:21:00.551669
    Evidence SHA-256
    93de4ce3edcedd421525733b44961d482bf295f4b8d35b7851f110ca6f86698b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:21:00.551669
    Evidence reason
  16. 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-11-02 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  17. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    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-11-02 12:31:33.000000
    Evidence SHA-256
    0eeee5ee74861389110ce5f409e0d65bd451f40670caeaa522f912d32416eabd
    Evidence timestamp as recorded
    2026-11-02 12:31:33
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:33.000000
    Evidence SHA-256
    face250988452c89b57675b6e92915efb813ba586839a6875624f61bc123a8a0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:33
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:31:49.000000
    Evidence SHA-256
    7be296ff6ebf1da05c7e1a7c9912298bfd8fb76dce86081a3f8bfc08f84e0943
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:31:49
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:31:49.000000
    Evidence SHA-256
    7be296ff6ebf1da05c7e1a7c9912298bfd8fb76dce86081a3f8bfc08f84e0943
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:31:49
    Evidence reason
    alive_content
  21. 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-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  22. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:33:35.000000
    Evidence SHA-256
    f3ace0f176fbe990aa4821518cfa2baf6110e4f35bef3cbf4a2c68a4cb63ebf0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:33:35
    Evidence reason
    alive_content
  23. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:33:35.000000
    Evidence SHA-256
    f3ace0f176fbe990aa4821518cfa2baf6110e4f35bef3cbf4a2c68a4cb63ebf0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:33:35
    Evidence reason
    alive_content
  24. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:21:15.000000
    Evidence SHA-256
    7c75376e85e2128200873cc17e9d42cd065d225366ab39f441b5859c10ab2fcb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:21:15
    Evidence reason
  25. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:21:15.000000
    Evidence SHA-256
    7c75376e85e2128200873cc17e9d42cd065d225366ab39f441b5859c10ab2fcb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:21:15
    Evidence reason
  26. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-11-01 04:12:19.466817
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    nevaldki.net detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 78
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 5/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Security threats, malware, Scam
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

6 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Cloudflare Radar

    Scam

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    nevaldki.net

    View source
  6. VirusTotal

    5/92 engine detections

    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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

nevaldki.net

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious OTX 1 ref 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 Unverified
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.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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 →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 nevaldki.net)
  • 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/nevaldki.net"
  title="PhishDestroy threat report for nevaldki.net"
  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>