Skip to security report
Analytics Dashboard
nienta.ru — PhishDestroy
Stored VirusTotal result: 0/92 engines flagged. malicious: 0. suspicious: 0. Analysis time (as stored): 2026-09-29T13:40:10Z. Retrieved (as stored): 2026-11-01T15:50:18Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
nienta.ru favicon

nienta.ru

In short

PhishDestroy describes nienta.ru as a coat retail homepage featuring a spring collection banner and catalog links.

“Пальто: пошив и продажа по всей России”

Review the evidence
Registrar
RussiaREGRU-RU
Resolved IP
Russia45.130.41.20BEGET.RU
Registered
Apr 6, 2022
First observed
Nov 1, 2026
PhishDestroy assessment Medium
25/100
Evidence score
First observed Nov 1, 2026 15:49 UTC · PhishDestroy
Risk signals
Stored PhishDestroy threat listing
VirusTotal
0 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 97
Page captures
4
open gallery
Domain age
1,670 days
registered 2022-04-06 according to WHOIS · source data differ
Nov 1, 2026
X Telegram API

Analysis

Medium
VirusTotal
0 / 92
Hosting
Russia45.130.41.20BEGET.RU
Registrar
RussiaREGRU-RU
Registered
Apr 6, 2022
Page captures
4
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-01T15:50:23Z
SHA-256: f97befac5e4d69098d53eb6121ec32e52715d333364efdd8d098ddc70d3d6324

PhishDestroy analysis, reviewed version

The captured nienta.ru homepage presents a coat retail page branded "Nienta," with a hero banner advertising a premium spring 2023 collection and a "show more" button as the main call to action. Below the banner, three promotional blocks introduce new arrivals, 2023 trends, and stylish coats, while the header offers catalog, about, delivery, and contact sections alongside a callback request and login or registration links.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidenceVirusTotal 0 / 92 8 sources

URLScan

Malicious · engine verdict · score 97

SHA-256 79ed30726086ca98de9b61e5a7636effca615fcfcf2e690450e62769734d22e3

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

01a197cd-d226-757e-b91c-1492899d695b

Final URL

https://nienta.ru/shop/

HTTP response

200

IP address

45.130.41.20

Contacted IP addresses

  • 45.130.41.20

Autonomous systems (ASN)

  • 198610

Server countries

  • RU

Linked domains

  • headerampher.icu

Document hash

6887f8dc2eb06453a5423994e76ab19dd30c5fc3eab4b5e34a1bb9f75c56a928

TLS session and certificate

Subject alternative names
  • nienta.ru
  • www.nienta.ru
Cipher
AES_256_GCM
Issuer
YR2
Subject
nienta.ru
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1381

Differs from the registration date in WHOIS (2022-04-06), which gives 1670 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1381

Differs from the registration date in WHOIS (2022-04-06), which gives 1670 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Certificate age, days

0

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
nginx-reuseport/1.21.1
Content-type
text/html
Original source fields · JSON
Uuid
01a197cd-d226-757e-b91c-1492899d695b
Final url
https://nienta.ru/shop/
Status
200
Ip
45.130.41.20
Contacted IP addresses
[
    "45.130.41.20"
]
Asns
[
    "198610"
]
Countries
[
    "RU"
]
Linked domains
[
    "headerampher.icu"
]
Document hash
6887f8dc2eb06453a5423994e76ab19dd30c5fc3eab4b5e34a1bb9f75c56a928
Tls
{
    "san": [
        "nienta.ru",
        "www.nienta.ru"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "nienta.ru",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-30T04:18:26Z",
    "valid_from": "2026-11-01T04:18:27Z"
}
Domain age days
1381

Differs from the registration date in WHOIS (2022-04-06), which gives 1670 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Apex age days
1381

Differs from the registration date in WHOIS (2022-04-06), which gives 1670 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Tls age days
0
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx-reuseport/1.21.1",
    "content-type": "text/html"
}
Separate monitor record · 2026-11-02 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a197cd-d226-757e-b91c-1492899d695b
score
0
malicious
false
result_at
2026-11-02T04:30:18Z
enriched_at
2026-11-02T09:13:09Z
source_timestamps
{"urlscan_result_at":"2026-11-02 05:30:18","urlscan_enriched_at":"2026-11-02 10:13:09"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
0
Suspicious
0
Undetected
38

Reputation score

0

Registrar

REGRU-RU

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.beget.ru
  • TTL, seconds
    300
    Type
    MX
    Value
    mx1.beget.com
    Priority
    10
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.beget.ru
  • TTL, seconds
    300
    Type
    MX
    Value
    mx2.beget.com
    Priority
    20
  • TTL, seconds
    600
    Type
    A
    Value
    45.130.41.20
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.beget.pro
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.beget.pro
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.beget.com
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.beget.com
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 redirect=beget.com
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.beget.com
    Value
    ns1.beget.com

DNS records observed

JARM fingerprint

2ad2ad0002ad2ad22c42d42d000000307ee0eb468e9fdb5cfcd698a80a67ef

Certificate

Subject alternative names
  • nienta.ru
  • www.nienta.ru
Issuer
Let's Encrypt / YR2
Serial
6deb678b4f8066abffcb4fad91826d0bab6
SHA-256
3602c04d4963efdee4802df9f57102f42d6595a72c2a051b0c50476b38f439af
Subject
nienta.ru
Valid until
Valid from

Registration record

Registrar
REGRU-RU
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 38
}
Reputation
0
Registrar
REGRU-RU
First seen
2023-11-07T15:12:36Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.beget.ru"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx1.beget.com",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.beget.ru"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx2.beget.com",
        "priority": 20
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "45.130.41.20"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.beget.pro"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.beget.pro"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.beget.com"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.beget.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 redirect=beget.com"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.beget.com",
        "value": "ns1.beget.com"
    }
]
Dns at
2026-09-29T13:58:04Z
Jarm
2ad2ad0002ad2ad22c42d42d000000307ee0eb468e9fdb5cfcd698a80a67ef
Certificate
{
    "san": [
        "nienta.ru",
        "www.nienta.ru"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "6deb678b4f8066abffcb4fad91826d0bab6",
    "sha256": "3602c04d4963efdee4802df9f57102f42d6595a72c2a051b0c50476b38f439af",
    "subject": "nienta.ru",
    "valid_to": "2026-11-30T09:33:43Z",
    "valid_from": "2026-09-01T09:33:44Z"
}
Registration record
{
    "registrar": "REGRU-RU"
}
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
0
denominator
92
malicious
null
suspicious
null
vendors
[]
observed_at
2026-09-29 13:40:10
checked_at
2026-11-01 16:50:18
fetched_at
2026-11-01 15:50:18
time_basis
as stored; legacy timezone not established

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

21be70f8-8eba-4870-8afe-e3a5dadf12d4

Final URL

https://nienta.ru/

HTTP response

200

Navigation history

  • URL
    https://nienta.ru/
    Status
    200

DOM structure hash

3a8314607ff1a881a28a31acbc96d187440d678a11d6b7f6e877f1e6d5fc8e67

Document hash

1351228532c1b862c92747bb5808ebfee9cad07d7b16406743ce7cd99eeee16e

Domain risk categories

  • Clothing
  • Society & Lifestyle

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    nienta.ru
    Type
    A
    Value
    45.130.41.20

DNSSEC valid

No

IP address

127.0.1.8

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

Registration record

Registrar
REGRU-RU
Registered
Expires
Nameservers
  • ns1.beget.com
  • ns1.beget.pro
  • ns2.beget.com
  • ns2.beget.pro
Original source fields · JSON
Uuid
21be70f8-8eba-4870-8afe-e3a5dadf12d4
Final url
https://nienta.ru/
Status
200
History
[
    {
        "url": "https://nienta.ru/",
        "status": 200
    }
]
DOM structure hash
3a8314607ff1a881a28a31acbc96d187440d678a11d6b7f6e877f1e6d5fc8e67
Document hash
1351228532c1b862c92747bb5808ebfee9cad07d7b16406743ce7cd99eeee16e
Domain risks
[
    "Clothing",
    "Society & Lifestyle"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "nienta.ru",
        "type": "A",
        "value": "45.130.41.20"
    }
]
Dnssec valid
false
Ip
127.0.1.8

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

Registration record
{
    "registrar": "REGRU-RU",
    "created": "2022-04-06T11:56:01Z",
    "expires": "2027-04-06T11:56:01Z",
    "nameservers": [
        "ns1.beget.com",
        "ns1.beget.pro",
        "ns2.beget.com",
        "ns2.beget.pro"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-01T16:06:32Z

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
10
analyzed_at
2026-11-01T16:06:32Z
source_timestamp
2026-11-01 17:06:32
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
nienta.ru coat shop homepage with spring collection banner
ai_description
PhishDestroy describes nienta.ru as a coat retail homepage featuring a spring collection banner and catalog links.
ai_summary
The captured nienta.ru homepage presents a coat retail page branded "Nienta," with a hero banner advertising a premium spring 2023 collection and a "show more" button as the main call to action. Below the banner, three promotional blocks introduce new arrivals, 2023 trends, and stylish coats, while the header offers catalog, about, delivery, and contact sections alongside a callback request and login or registration links. The stored VirusTotal domain result reports 0 detections out of 92 engines.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 16:51:39
revision
e2297eed31e8749c74ede0c809cc74ee5617a550cdd87475e8de016366fe7d18
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: 27 fields

Mail configuration

MX records
  • mx2.beget.com
  • mx1.beget.com
SPF record
v=spf1 redirect=beget.com
SPF lookups
7

CAA records

Domain
nienta.ru

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
24
Archived days
28
Snapshots per day
0.02
Average page size, bytes
28950

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • http://nienta.ru/sitemap_index.xml

Sitemap

Present
Yes
URL count
102

Page title and metadata

Open Graph URL
https://nienta.ru/
Page title
Пальто: пошив и продажа по всей России
Open Graph type
website
Indexing directives
index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Open Graph image
http://nienta.ru/wp-content/uploads/2022/08/DSC05654.webp
Open Graph title
Пальто: пошив и продажа по всей России
Generator
WordPress 6.1.16
Open Graph site name
Nienta
Description
Пальто оптом и в розницу от производителя Niento. Драповые, шерстяные, кашемировые и др. Гарантия качества! Заказывайте со скидкой
Twitter card
summary_large_image
Canonical URL
https://nienta.ru/
Open Graph description
Пальто оптом и в розницу от производителя Niento. Драповые, шерстяные, кашемировые и др. Гарантия качества! Заказывайте со скидкой

Trackers

Requests
206
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google Marketing Platform
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    3
  • Name
    Yandex
    Company
    Yandex
    Country
    RU
    Category
    Advertising
    Requests
    2
  • Name
    YouTube
    Company
    Google
    Country
    US
    Category
    Audio/Video Player
    Requests
    9
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    Yandex Metrika
    Company
    Yandex
    Country
    RU
    Category
    Site Analytics
    Requests
    2

Forms and mixed content

Passive insecure
  • http://nienta.ru/wp-content/uploads/2023/06/tel2.png
  • http://nienta.ru/wp-content/uploads/2023/07/vk.png
Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
66
TLS
62
Waiting
2215
Connection
58
Download
727
Response time, ms
3128

TLS connection

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

Ports

Open ports
  • 21
  • 22
  • 80
  • 443
  • 3306

Carbon estimate

Bytes
234119
CO₂, grams
0.0086
Cleaner than, %
4

DNS servers

Nameservers
  • IP address
    185.50.27.12
    Host
    ns2.beget.pro
  • IP address
    93.92.81.0
    Host
    ns1.beget.pro
  • IP address
    185.50.27.12
    Host
    ns2.beget.com
  • IP address
    93.92.81.0
    Host
    ns1.beget.com
  • IP address
    185.50.27.12
    Host
    ns2.beget.ru
  • IP address
    5.101.159.11
    Host
    ns1.beget.ru
DNS zone
nienta.ru

Cookies

Cookies
  • Name
    __Secure-YNID
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    YSC
    Secure
    Yes
    Session cookie
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    VISITOR_INFO1_LIVE
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    VISITOR_PRIVACY_METADATA
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    __Secure-ROLLOUT_TOKEN
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    bh
    Secure
    Yes
    SameSite
    None
  • Name
    _ym_uid
    Secure
    Yes
    SameSite
    None
  • Name
    _ym_d
    Secure
    Yes
    SameSite
    None
  • Name
    sync_cookie_csrf
    Secure
    Yes
    SameSite
    None
  • Name
    _ym_isad
    Secure
    Yes
    SameSite
    None
  • Name
    sync_cookie_csrf
    Secure
    Yes
    SameSite
    None
  • Name
    yabs-sid
    Secure
    Yes
    Session cookie
    Yes
    SameSite
    None
  • Name
    i
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    yandexuid
    Secure
    Yes
    SameSite
    None
  • Name
    yuidss
    Secure
    Yes
    SameSite
    None
  • Name
    ymex
    Secure
    Yes
    SameSite
    None
  • Name
    receive-cookie-deprecation
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    bh
    Secure
    Yes
    SameSite
    None

Location

IP address
45.130.41.20
ASN
198610
Organization
BEGET.RU
City
St Petersburg
Country
RU

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
nienta.ru

DNS records

A
  • 45.130.41.20
MX
  • Mail server
    mx2.beget.com
    Priority
    20
  • Mail server
    mx1.beget.com
    Priority
    10
NS
  • ns1.beget.pro
  • ns2.beget.com
  • ns2.beget.pro
  • ns2.beget.ru
  • ns1.beget.ru
  • ns1.beget.com
SOA
Primary nameserver
ns1.beget.com
Hostmaster
hostmaster.beget.com
Serial
1754680243
Refresh, seconds
300
Retry, seconds
600
Expiry, seconds
86400
Minimum TTL, seconds
300
TXT
  • v=spf1 redirect=beget.com

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
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
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
45.130.41.20
IP version
4

Redirects

Redirect chain
  • https://nienta.ru

Subdomains

Count
1
Subdomains
  • www.nienta.ru

Page links

External link addresses
  • https://t.me/nienta_ru
  • https://vk.com/nienta
  • https://connect.ok.ru/offer
  • https://api.whatsapp.com/send
  • https://vk.com/share.php
  • https://telegram.me/share/url
  • https://connect.ok.ru/offer
  • https://api.whatsapp.com/send
  • https://vk.com/share.php
  • https://telegram.me/share/url
  • https://connect.ok.ru/offer
  • https://api.whatsapp.com/send
  • https://vk.com/share.php
  • https://telegram.me/share/url
  • https://connect.ok.ru/offer
  • https://api.whatsapp.com/send
  • https://vk.com/share.php
  • https://telegram.me/share/url
External links
18
Internal links
43

Registration record

Registrar
REGRU-RU
Registered
Expires
Status
  • REGISTERED, DELEGATED, UNVERIFIED
Nameservers
  • ns1.beget.com.
  • ns1.beget.pro.
  • ns2.beget.com.
  • ns2.beget.pro.

HTTP headers

Response headers
Server
nginx-reuseport/1.21.1
Content-type
text/html; charset=UTF-8
X-powered-by
PHP/7.4.33
Link
<https://nienta.ru/wp-json/>; rel="https://api.w.org/", <https://nienta.ru/wp-json/wp/v2/pages/3228>; rel="alternate"; type="application/json", <https://nienta.ru/>; rel=shortlink
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mx2.beget.com",
        "mx1.beget.com"
    ],
    "spf": "v=spf1 redirect=beget.com",
    "spf_lookups": 7
}
Caa records
{
    "domain": "nienta.ru"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-01T15:49:52Z",
    "first": "2023-03-21T18:42:54Z",
    "changes": 24,
    "days_archived": 28,
    "scans_per_day": 0.02,
    "avg_page_bytes": 28950
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "http://nienta.ru/sitemap_index.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 102
}
Page title and metadata
{
    "ogUrl": "https://nienta.ru/",
    "title": "Пальто: пошив и продажа по всей России",
    "ogType": "website",
    "robots": "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1",
    "ogImage": "http://nienta.ru/wp-content/uploads/2022/08/DSC05654.webp",
    "ogTitle": "Пальто: пошив и продажа по всей России",
    "generator": "WordPress 6.1.16",
    "ogSiteName": "Nienta",
    "description": "Пальто оптом и в розницу от производителя Niento. Драповые, шерстяные, кашемировые и др. Гарантия качества! Заказывайте со скидкой",
    "twitterCard": "summary_large_image",
    "canonicalUrl": "https://nienta.ru/",
    "ogDescription": "Пальто оптом и в розницу от производителя Niento. Драповые, шерстяные, кашемировые и др. Гарантия качества! Заказывайте со скидкой"
}
Trackers
{
    "requests": 206,
    "trackers": [
        {
            "name": "Google",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google Marketing Platform",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 3
        },
        {
            "name": "Yandex",
            "company": "Yandex",
            "country": "RU",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "YouTube",
            "company": "Google",
            "country": "US",
            "category": "Audio/Video Player",
            "requests": 9
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Yandex Metrika",
            "company": "Yandex",
            "country": "RU",
            "category": "Site Analytics",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "passive_insecure": [
        "http://nienta.ru/wp-content/uploads/2023/06/tel2.png",
        "http://nienta.ru/wp-content/uploads/2023/07/vk.png"
    ],
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 66,
        "tls": 62,
        "wait": 2215,
        "connect": 58,
        "download": 727
    },
    "response_ms": 3128
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        80,
        443,
        3306
    ]
}
Carbon
{
    "bytes": 234119,
    "co2_grams": 0.0086,
    "cleaner_than": 4
}
Dns server
{
    "ns": [
        {
            "ip": "185.50.27.12",
            "host": "ns2.beget.pro"
        },
        {
            "ip": "93.92.81.0",
            "host": "ns1.beget.pro"
        },
        {
            "ip": "185.50.27.12",
            "host": "ns2.beget.com"
        },
        {
            "ip": "93.92.81.0",
            "host": "ns1.beget.com"
        },
        {
            "ip": "185.50.27.12",
            "host": "ns2.beget.ru"
        },
        {
            "ip": "5.101.159.11",
            "host": "ns1.beget.ru"
        }
    ],
    "zone": "nienta.ru"
}
Cookies
{
    "cookies": [
        {
            "name": "__Secure-YNID",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "YSC",
            "secure": true,
            "session": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "VISITOR_INFO1_LIVE",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "VISITOR_PRIVACY_METADATA",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "__Secure-ROLLOUT_TOKEN",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "bh",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_ym_uid",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_ym_d",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "sync_cookie_csrf",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_ym_isad",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "sync_cookie_csrf",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "yabs-sid",
            "secure": true,
            "session": true,
            "same_site": "None"
        },
        {
            "name": "i",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "yandexuid",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "yuidss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "ymex",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "receive-cookie-deprecation",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "bh",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "45.130.41.20",
    "asn": "198610",
    "org": "BEGET.RU",
    "city": "St Petersburg",
    "country": "RU"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "nienta.ru"
}
DNS records
{
    "A": [
        "45.130.41.20"
    ],
    "MX": [
        "{\"exchange\": \"mx2.beget.com\", \"priority\": 20}",
        "{\"exchange\": \"mx1.beget.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns1.beget.pro",
        "ns2.beget.com",
        "ns2.beget.pro",
        "ns2.beget.ru",
        "ns1.beget.ru",
        "ns1.beget.com"
    ],
    "SOA": "{\"nsname\": \"ns1.beget.com\", \"hostmaster\": \"hostmaster.beget.com\", \"serial\": 1754680243, \"refresh\": 300, \"retry\": 600, \"expire\": 86400, \"minttl\": 300}",
    "TXT": [
        "v=spf1 redirect=beget.com"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "45.130.41.20",
    "family": 4
}
Redirects
{
    "chain": [
        "https://nienta.ru"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.nienta.ru"
    ]
}
Page links
{
    "external": [
        "https://t.me/nienta_ru",
        "https://vk.com/nienta",
        "https://connect.ok.ru/offer",
        "https://api.whatsapp.com/send",
        "https://vk.com/share.php",
        "https://telegram.me/share/url",
        "https://connect.ok.ru/offer",
        "https://api.whatsapp.com/send",
        "https://vk.com/share.php",
        "https://telegram.me/share/url",
        "https://connect.ok.ru/offer",
        "https://api.whatsapp.com/send",
        "https://vk.com/share.php",
        "https://telegram.me/share/url",
        "https://connect.ok.ru/offer",
        "https://api.whatsapp.com/send",
        "https://vk.com/share.php",
        "https://telegram.me/share/url"
    ],
    "external_count": 18,
    "internal_count": 43
}
Registration record
{
    "registrar": "REGRU-RU",
    "created": "2022-04-06T11:56:01Z",
    "expires": "2027-04-06T11:56:01Z",
    "status": [
        "REGISTERED, DELEGATED, UNVERIFIED"
    ],
    "nameservers": [
        "ns1.beget.com.",
        "ns1.beget.pro.",
        "ns2.beget.com.",
        "ns2.beget.pro."
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx-reuseport/1.21.1",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "PHP/7.4.33",
        "link": "<https://nienta.ru/wp-json/>; rel=\"https://api.w.org/\", <https://nienta.ru/wp-json/wp/v2/pages/3228>; rel=\"alternate\"; type=\"application/json\", <https://nienta.ru/>; rel=shortlink"
    }
}

Explore

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

Checked, no match

Last checked

Stored Capture · 4 captures

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: f97befac5e4d69098d53eb6121ec32e52715d333364efdd8d098ddc70d3d6324 SHA-256 of the prepared copy given to the model: a1dde75c6e7f5959a53be26773d27e36fe29e0d65faec27be5e23efd2f333aea
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://nienta.ru/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
IP Reputation Russia45.130.41.20 abuse score 0/100 1 report Port Scan checked Nov 1, 2026 last reported
Registrar REGRU-RU RU(RU)
Abuse contactabuse@beget.ru
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for nienta.ru →
Hosting abuse contact abuse@beget.ru BEGET.RU · AS198610
RegistrationCreated Apr 6, 2022 — Expires Apr 6, 2027
WHOIS statusREGISTERED,
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1001 brand signal
Submitted URLhttps://nienta.ru/shop/
Favicon Hash
Observed page title
Пальто: пошив и продажа по всей России
Automated brand references
Telegram
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 28 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Russia45.130.41.20
Network ASN
AS198610
AS name
BEGET-AS Beget LLC, RU
Organization
BEGET.RU
Observed location
RussiaSt Petersburg, RU
Server header
nginx-reuseport/1.21.1

Nameservers 6

  • ns1.beget.com
  • ns1.beget.pro
  • ns1.beget.ru
  • ns2.beget.com
  • ns2.beget.pro
  • ns2.beget.ru

SOA

  • nsname: ns1.beget.com
  • hostmaster: hostmaster.beget.com
  • serial: 1754680243
  • refresh: 300
  • retry: 600
  • expire: 86400
  • minttl: 300

Mail routing 2 MX records

  • mx1.beget.compriority 10
  • mx2.beget.compriority 20

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-01 09:33:44
Valid until
2026-11-30 09:33:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3602c04d4963efdee4802df9f57102f42d6595a72c2a051b0c50476b38f439af
Certificate names · 2 SANs
  • nienta.ru
  • www.nienta.ru

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

viewdns.info · 45.130.41.20rapiddns.io
Recorded subdomains1

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

  • www.nienta.ruDomain record
Technologies · 15 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of nienta.ru · checked Nov 1, 2026

64
Needs Work
Performance
FCP
1.87 s
First Contentful Paint
LCP
6.46 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
227 ms
Total Blocking Time
SI
8.99 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: https://nienta.ru/shop/
Meritking | Meritking Yenilenen İsim Hakkı - Online 2026
Meritking çalışan giriş adresiyle Türkçe destek ve yerel ödeme seçenekleri ile deneyimi yaşayın.
Response
HTTP 200
HTML body
22.9 KB
Compressed
6.8 KB
Links
14 internal · 1 external
Detected technologies
nginx
Selected response headers
Server: nginx-reuseport/1.21.1
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Meritking | Meritking Yenilenen İsim Hakkı - Online 2026
Open Graph description: Meritking çalışan giriş adresiyle Türkçe destek ve yerel ödeme seçenekleri ile deneyimi yaşayın.
Twitter card: summary_large_image
Saved response-header values · 10
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 01 Nov 2026 15:50:00 GMT
Etag
W/"5bb7-65efe053b82a4"
Keep-Alive
timeout=30
Last-Modified
Thu, 29 Oct 2026 17:29:22 GMT
Server
nginx-reuseport/1.21.1
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived
Registration & observation details1

Availability observations

Last reachable 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: 4 SHA-256 hashes: 3 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 15:53 UTC.

Open this scan on URLScan 01a197cd-d226-757e-b91c-1492899d695b ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

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_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-02 01:08:56.000000
    Evidence SHA-256
    78fc5ca8b23434d386e69657e8c096c9340b2ca3037278de93e0b0081ca9b479
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 01:08:56
    Evidence reason
    unavailable
  2. 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-02 01:08:56.000000
    Evidence SHA-256
    78fc5ca8b23434d386e69657e8c096c9340b2ca3037278de93e0b0081ca9b479
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 01:08:56
    Evidence reason
    unavailable
  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-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
  4. 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 16:50:59.000000
    Evidence SHA-256
    773995be5afe8681499260c71ff6715e88b0232046f58df83ea0c10320f783d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 16:50:59
    Evidence reason
  5. 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 16:50:59.000000
    Evidence SHA-256
    773995be5afe8681499260c71ff6715e88b0232046f58df83ea0c10320f783d9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 16:50:59
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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
    nienta.ru detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 97
  • 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
  • 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

4 entries
  1. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    nienta.ru

    View source
  4. VirusTotal

    0/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.

nienta.ru

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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?

2 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 nienta.ru)
  • 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/nienta.ru"
  title="PhishDestroy threat report for nienta.ru"
  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>