Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
migural.ru favicon

migural.ru

In short

PhishDestroy records the captured homepage of migural.ru, presenting itself as a marble and granite products site.

“МиГ Урал — Изделия из Мрамора и Гранита Урал”

Review the evidence
Registrar
RussiaREGRU-RU
Resolved IP
Russia31.31.196.21Domain names registrar REG.RU , Ltd
Registered
Sep 3, 2015
First observed
Oct 31, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 5/92
VirusTotal
5 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 50
Page captures
7
open gallery
Domain age
4,076 days
registered 2015-09-03 according to WHOIS · source data differ
OTX: 1 ref Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the captured homepage of migural.ru, presenting itself as a marble and granite products site.

Critical
Status
Last known active
VirusTotal
5 / 92
Hosting
Russia31.31.196.21Domain names registrar REG.RU , Ltd
Registrar
RussiaREGRU-RU
Registered
Sep 3, 2015
OTX
1 community ref
Page captures
7
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured migural.ru homepage presents itself as "МиГ Урал — Изделия из Мрамора и Гранита Урал," a Russian-language site about marble and granite products. A search box sits in the header, and the main content opens with a "Главная" heading followed by a paragraph on natural stone as a building and decorative material, with links on "Природный камень" and "мраморные или гранитные" within the text.

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

Source evidenceVirusTotal 5 / 92 · OTX 1 references 8 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
5
Suspicious
0
Undetected
34

Vendor labels

VIPRE
phishing
Seclookup
malicious
Gridinsoft
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Business/Economy, Phishing (alphaMountain.ai)

Registrar

REGRU-RU

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    31.31.196.21
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2a00:f940:2:2:1:1:0:208
  • TTL, seconds
    3600
    Type
    TXT
    Value
    v=spf1 ip4:31.31.196.21 a mx include:_spf.hosting.reg.ru ~all
  • TTL, seconds
    3600
    Type
    MX
    Value
    mx1.hosting.reg.ru
    Priority
    10
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.hosting.reg.ru
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    support.reg.ru
    Value
    server208.hosting.reg.ru
  • TTL, seconds
    3600
    Type
    MX
    Value
    mx2.hosting.reg.ru
    Priority
    20
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.hosting.reg.ru

DNS records observed

JARM fingerprint

29d29d00029d29d00042d42d0000002059a3b916699461c5923779b77cf06b

Certificate

Subject alternative names
  • migural.ru
  • www.migural.ru
Issuer
Let's Encrypt / YR1
Serial
5c2c371351fbd1af81e1e15c39fb22eace5
SHA-256
14a13aaddb93bfc7f1479db278fcb4a8bf8f99e77dcb3465eba81bbab0e692b9
Subject
migural.ru
Valid until
Valid from

Registration record

Registrar
REGRU-RU
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 5,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "VIPRE": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Business/Economy, Phishing (alphaMountain.ai)"
}
Registrar
REGRU-RU
First seen
2024-03-05T16:56:52Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "31.31.196.21"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2a00:f940:2:2:1:1:0:208"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 ip4:31.31.196.21 a mx include:_spf.hosting.reg.ru ~all"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "mx1.hosting.reg.ru",
        "priority": 10
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.hosting.reg.ru"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "support.reg.ru",
        "value": "server208.hosting.reg.ru"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "mx2.hosting.reg.ru",
        "priority": 20
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.hosting.reg.ru"
    }
]
Dns at
2026-10-31T10:45:48Z
Jarm
29d29d00029d29d00042d42d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "migural.ru",
        "www.migural.ru"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5c2c371351fbd1af81e1e15c39fb22eace5",
    "sha256": "14a13aaddb93bfc7f1479db278fcb4a8bf8f99e77dcb3465eba81bbab0e692b9",
    "subject": "migural.ru",
    "valid_to": "2026-12-12T23:37:59Z",
    "valid_from": "2026-09-13T23:38:00Z"
}
Registration record
{
    "registrar": "REGRU-RU"
}
Separate source record · 5 malicious + 0 suspicious / 92 · 2026-10-31 10:09:49 UTC

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

record_source
collected_observations.vt
analysis_at
2026-10-31T10:09:49Z
fetched_at
2026-10-31T19:11:52Z
stats
{"timeout":0,"harmless":53,"malicious":5,"suspicious":0,"undetected":34}

URLScan

Malicious · engine verdict · score 50

SHA-256 c40b38d4494afa783742e017c42bc191f7dac8519b7f7e921d863a1c3f34c406

Open report
URLScanOriginal source recordObserved: 25 fields

Observed: · Retrieved:

Report ID

01a19368-e649-76da-abc0-674fab6051ec

Final URL

https://migural.ru/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://migural.ru/
    From
    http://migural.ru/
    Status
    307

IP address

31.31.196.21

Reverse DNS (PTR)

server208.hosting.reg.ru

Contacted domains

  • mc.yandex.com
  • mc.yandex.ru
  • informer.yandex.ru

Contacted IP addresses

  • 77.88.21.119
  • 87.250.250.119
  • 31.31.196.21

Autonomous systems (ASN)

  • 13238
  • 197695

Server countries

  • RU

Linked domains

  • metrika.yandex.ru
  • catchthemes.com

Document hash

c40b38d4494afa783742e017c42bc191f7dac8519b7f7e921d863a1c3f34c406

Script hashes

  • cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf
  • 5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89
  • 7b4db17ae6cefea8f0fd97df42be3adcbe560e5ed494b45455c0fb966b545dce
  • a9848907e998784525523ba5c1985975164e67ab9b033e64e61e94e2d7530dd5
  • f9f8bd8563818a4fc6b90510703dd64cb2a70185540ad3a37e55bb77dca44a6f
  • 73b7c13bdf77881a7546967c4f52b3c6e306b61bb00387d34ddee583f410f6b2
  • 5c9b97d326150b1d83aa4fbb7ee58bb3a17d35208bb182c26b8eb3aa01cd179a
  • fb82877818fa23c8c028053cc5744c5d7947faca82bd50a82b918016499bfb62
  • 49e2437ef0089b28fa0eee95e5a16a9b74c9b345fd8f7581acead07b1039a46c
  • d35452fad65d6f3bc1d026ce4eff08cdf6b503b0ed61b70c663529c0bb5a83ff

JavaScript globals

  • jQuery
  • ym
  • Waypoint
  • bazz_ajax
  • bazz_options
  • _wpemojiSettings
  • waypointContextKey
  • twemoji
  • wp
  • Ya
  • yaCounter66588130

Cookies

  • bh
  • _ym_uid
  • _ym_d
  • sync_cookie_csrf
  • _ym_isad
  • yabs-sid
  • i
  • yandexuid
  • yuidss
  • ymex
  • sync_cookie_csrf_secondary

Browser storage keys

  • wpEmojiSettingsSupports
  • _ymBRC
  • _ym_synced
  • _ym66588130_lsid
  • _ym66588130:0_reqNum
  • _ym_uid
  • _ym_retryReqs
  • _ym_jn

TLS session and certificate

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

Domain age, days

3375

Differs from the registration date in WHOIS (2015-09-03), which gives 4076 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

3375

Differs from the registration date in WHOIS (2015-09-03), which gives 4076 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

47

Certificate validity, days

89

Page requests

28

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a19368-e649-76da-abc0-674fab6051ec
Final url
https://migural.ru/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://migural.ru/",
        "from": "http://migural.ru/",
        "status": 307
    }
]
Ip
31.31.196.21
Ptr
server208.hosting.reg.ru
Contacted domains
[
    "mc.yandex.com",
    "mc.yandex.ru",
    "informer.yandex.ru"
]
Contacted IP addresses
[
    "77.88.21.119",
    "87.250.250.119",
    "31.31.196.21"
]
Asns
[
    "13238",
    "197695"
]
Countries
[
    "RU"
]
Linked domains
[
    "metrika.yandex.ru",
    "catchthemes.com"
]
Document hash
c40b38d4494afa783742e017c42bc191f7dac8519b7f7e921d863a1c3f34c406
Script hashes
[
    "cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf",
    "5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89",
    "7b4db17ae6cefea8f0fd97df42be3adcbe560e5ed494b45455c0fb966b545dce",
    "a9848907e998784525523ba5c1985975164e67ab9b033e64e61e94e2d7530dd5",
    "f9f8bd8563818a4fc6b90510703dd64cb2a70185540ad3a37e55bb77dca44a6f",
    "73b7c13bdf77881a7546967c4f52b3c6e306b61bb00387d34ddee583f410f6b2",
    "5c9b97d326150b1d83aa4fbb7ee58bb3a17d35208bb182c26b8eb3aa01cd179a",
    "fb82877818fa23c8c028053cc5744c5d7947faca82bd50a82b918016499bfb62",
    "49e2437ef0089b28fa0eee95e5a16a9b74c9b345fd8f7581acead07b1039a46c",
    "d35452fad65d6f3bc1d026ce4eff08cdf6b503b0ed61b70c663529c0bb5a83ff"
]
Globals
[
    "jQuery",
    "ym",
    "Waypoint",
    "bazz_ajax",
    "bazz_options",
    "_wpemojiSettings",
    "waypointContextKey",
    "twemoji",
    "wp",
    "Ya",
    "yaCounter66588130"
]
Cookies
[
    "bh",
    "_ym_uid",
    "_ym_d",
    "sync_cookie_csrf",
    "_ym_isad",
    "yabs-sid",
    "i",
    "yandexuid",
    "yuidss",
    "ymex",
    "sync_cookie_csrf_secondary"
]
Storage keys
[
    "wpEmojiSettingsSupports",
    "_ymBRC",
    "_ym_synced",
    "_ym66588130_lsid",
    "_ym66588130:0_reqNum",
    "_ym_uid",
    "_ym_retryReqs",
    "_ym_jn"
]
Tls
{
    "san": [
        "migural.ru",
        "www.migural.ru"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "migural.ru",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-12T23:37:59Z",
    "valid_from": "2026-09-13T23:38:00Z"
}
Domain age days
3375

Differs from the registration date in WHOIS (2015-09-03), which gives 4076 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
3375

Differs from the registration date in WHOIS (2015-09-03), which gives 4076 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
47
Tls valid days
89
Requests
28
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 50,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=UTF-8"
}

OTX

1 community reference

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

0b8f926c-c2e3-4d16-ba08-509a6e19e97a

Final URL

https://migural.ru/

HTTP response

200

Navigation history

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

DOM structure hash

748322943dfadcc0068579ab99f45e9bb9df16ba91d237ef29d375ce0bd34a30

Document hash

c40b38d4494afa783742e017c42bc191f7dac8519b7f7e921d863a1c3f34c406

Domain risk categories

  • Business
  • Business & Economy

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    migural.ru
    Type
    A
    Value
    31.31.196.21
  • Name
    migural.ru
    Type
    AAAA
    Value
    2a00:f940:2:2:1:1:0:208

DNSSEC valid

No

IP address

127.0.1.68

127.0.1.68 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.hosting.reg.ru
  • ns2.hosting.reg.ru
Original source fields · JSON
Uuid
0b8f926c-c2e3-4d16-ba08-509a6e19e97a
Final url
https://migural.ru/
Status
200
History
[
    {
        "url": "https://migural.ru/",
        "status": 200
    }
]
DOM structure hash
748322943dfadcc0068579ab99f45e9bb9df16ba91d237ef29d375ce0bd34a30
Document hash
c40b38d4494afa783742e017c42bc191f7dac8519b7f7e921d863a1c3f34c406
Domain risks
[
    "Business",
    "Business & Economy"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "migural.ru",
        "type": "A",
        "value": "31.31.196.21"
    },
    {
        "name": "migural.ru",
        "type": "AAAA",
        "value": "2a00:f940:2:2:1:1:0:208"
    }
]
Dnssec valid
false
Ip
127.0.1.68

127.0.1.68 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": "2015-09-03T15:52:52Z",
    "expires": "2027-09-03T15:52:52Z",
    "nameservers": [
        "ns1.hosting.reg.ru",
        "ns2.hosting.reg.ru"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 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
migural.ru homepage for МиГ Урал marble and granite products
ai_description
PhishDestroy records the captured homepage of migural.ru, presenting itself as a marble and granite products site.
ai_summary
The captured migural.ru homepage presents itself as "МиГ Урал — Изделия из Мрамора и Гранита Урал," a Russian-language site about marble and granite products. A search box sits in the header, and the main content opens with a "Главная" heading followed by a paragraph on natural stone as a building and decorative material, with links on "Природный камень" and "мраморные или гранитные" within the text. The stored VirusTotal domain result reports 5 detections out of 92 engines. VIPRE reported "phishing"; Seclookup reported "malicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 20:14:15
revision
c6a80827343c47b1e3146068e23de2770bb28df2090b63c433349285b2bbfc97
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
  • mx1.hosting.reg.ru
  • mx2.hosting.reg.ru
SPF record
v=spf1 ip4:31.31.196.21 a mx include:_spf.hosting.reg.ru ~all
SPF lookups
3

CAA records

Domain
migural.ru

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
66
Archived days
73
Snapshots per day
0.02
Average page size, bytes
6043

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • http://migural.ru/
  • http://migural.ru/
  • http://migural.ru/
  • http://migural.ru/
  • http://migural.ru/

Sitemap

Present
Yes
URL count
8

Page title and metadata

Page title
МиГ Урал — Изделия из Мрамора и Гранита Урал
Indexing directives
max-image-preview:large
Generator
WordPress 7.1.4
Canonical URL
https://migural.ru/

Trackers

Requests
23
Observed services
  • Name
    Yandex
    Company
    Yandex
    Country
    RU
    Category
    Advertising
    Requests
    2
  • Name
    Yandex Metrika
    Company
    Yandex
    Country
    RU
    Category
    Site Analytics
    Requests
    1

Forms and mixed content

Passive insecure
  • http://migural.ru/wp-content/uploads/2015/10/reWalls.com-35251-e1444656025559-150x94.jpg
Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
58
Waiting
206
Connection
60
Download
5
Response time, ms
333

TLS connection

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

Ports

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

Carbon estimate

Bytes
37435
CO₂, grams
0.0014
Cleaner than, %
43

DNS servers

Nameservers
  • IP address
    31.31.198.177
    Host
    ns1.hosting.reg.ru
  • IP address
    37.140.192.31
    Host
    ns2.hosting.reg.ru
DNS zone
migural.ru

Cookies

Cookies
  • 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
2a00:f940:2:2:1:1:0:208
ASN
197695
Organization
Domain names registrar REG.RU , Ltd
City
Moscow
Country
RU

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
migural.ru

DNS records

A
  • 31.31.196.21
MX
  • Mail server
    mx1.hosting.reg.ru
    Priority
    10
  • Mail server
    mx2.hosting.reg.ru
    Priority
    20
NS
  • ns2.hosting.reg.ru
  • ns1.hosting.reg.ru
SOA
Primary nameserver
server208.hosting.reg.ru
Hostmaster
support.reg.ru
Serial
2022041742
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
86400
TXT
  • v=spf1 ip4:31.31.196.21 a mx include:_spf.hosting.reg.ru ~all
AAAA
  • 2a00:f940:2:2:1:1:0:208

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
2a00:f940:2:2:1:1:0:208
IP version
6

Redirects

Redirect chain
  • https://migural.ru

Subdomains

Count
1
Subdomains
  • www.migural.ru

Page links

External link addresses
  • http://migural.ru/%d0%be%d0%b1%d1%80%d0%b0%d0%b7%d1%86%d1%8b-%d0%ba%d0%b0%d0%bc%d0%bd%d1%8f/
  • http://migural.ru/
  • http://migural.ru/%d0%b3%d0%bb%d0%b0%d0%b2%d0%bd%d0%b0%d1%8f/rewalls-com-3525-2/
  • https://metrika.yandex.ru/stat/
  • http://catchthemes.com/
External links
5
Internal links
13

Registration record

Registrar
REGRU-RU
Registered
Expires
Status
  • REGISTERED, DELEGATED, VERIFIED
Nameservers
  • ns1.hosting.reg.ru.
  • ns2.hosting.reg.ru.

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mx1.hosting.reg.ru",
        "mx2.hosting.reg.ru"
    ],
    "spf": "v=spf1 ip4:31.31.196.21 a mx include:_spf.hosting.reg.ru ~all",
    "spf_lookups": 3
}
Caa records
{
    "domain": "migural.ru"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T19:10:12Z",
    "first": "2015-11-03T18:13:18Z",
    "changes": 66,
    "days_archived": 73,
    "scans_per_day": 0.02,
    "avg_page_bytes": 6043
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "http://migural.ru/",
        "http://migural.ru/",
        "http://migural.ru/",
        "http://migural.ru/",
        "http://migural.ru/"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 8
}
Page title and metadata
{
    "title": "МиГ Урал — Изделия из Мрамора и Гранита Урал",
    "robots": "max-image-preview:large",
    "generator": "WordPress 7.1.4",
    "canonicalUrl": "https://migural.ru/"
}
Trackers
{
    "requests": 23,
    "trackers": [
        {
            "name": "Yandex",
            "company": "Yandex",
            "country": "RU",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "Yandex Metrika",
            "company": "Yandex",
            "country": "RU",
            "category": "Site Analytics",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "passive_insecure": [
        "http://migural.ru/wp-content/uploads/2015/10/reWalls.com-35251-e1444656025559-150x94.jpg"
    ],
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 58,
        "wait": 206,
        "connect": 60,
        "download": 5
    },
    "response_ms": 333
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Carbon
{
    "bytes": 37435,
    "co2_grams": 0.0014,
    "cleaner_than": 43
}
Dns server
{
    "ns": [
        {
            "ip": "31.31.198.177",
            "host": "ns1.hosting.reg.ru"
        },
        {
            "ip": "37.140.192.31",
            "host": "ns2.hosting.reg.ru"
        }
    ],
    "zone": "migural.ru"
}
Cookies
{
    "cookies": [
        {
            "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": "2a00:f940:2:2:1:1:0:208",
    "asn": "197695",
    "org": "Domain names registrar REG.RU , Ltd",
    "city": "Moscow",
    "country": "RU"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "migural.ru"
}
DNS records
{
    "A": [
        "31.31.196.21"
    ],
    "MX": [
        "{\"exchange\": \"mx1.hosting.reg.ru\", \"priority\": 10}",
        "{\"exchange\": \"mx2.hosting.reg.ru\", \"priority\": 20}"
    ],
    "NS": [
        "ns2.hosting.reg.ru",
        "ns1.hosting.reg.ru"
    ],
    "SOA": "{\"nsname\": \"server208.hosting.reg.ru\", \"hostmaster\": \"support.reg.ru\", \"serial\": 2022041742, \"refresh\": 10800, \"retry\": 3600, \"expire\": 604800, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 ip4:31.31.196.21 a mx include:_spf.hosting.reg.ru ~all"
    ],
    "AAAA": [
        "2a00:f940:2:2:1:1:0:208"
    ]
}
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": "2a00:f940:2:2:1:1:0:208",
    "family": 6
}
Redirects
{
    "chain": [
        "https://migural.ru"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.migural.ru"
    ]
}
Page links
{
    "external": [
        "http://migural.ru/%d0%be%d0%b1%d1%80%d0%b0%d0%b7%d1%86%d1%8b-%d0%ba%d0%b0%d0%bc%d0%bd%d1%8f/",
        "http://migural.ru/",
        "http://migural.ru/%d0%b3%d0%bb%d0%b0%d0%b2%d0%bd%d0%b0%d1%8f/rewalls-com-3525-2/",
        "https://metrika.yandex.ru/stat/",
        "http://catchthemes.com/"
    ],
    "external_count": 5,
    "internal_count": 13
}
Registration record
{
    "registrar": "REGRU-RU",
    "created": "2015-09-03T15:52:52Z",
    "expires": "2027-09-03T15:52:52Z",
    "status": [
        "REGISTERED, DELEGATED, VERIFIED"
    ],
    "nameservers": [
        "ns1.hosting.reg.ru.",
        "ns2.hosting.reg.ru."
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about migural.ru

Is migural.ru legit?

PhishDestroy records the captured homepage of migural.ru, presenting itself as a marble and granite products site.

Is migural.ru safe to connect a wallet?

This report does not record which wallet requests migural.ru 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 migural.ru?

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

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

Domain details

Domain
IP Reputation Russia31.31.196.21 abuse score 0/100 0 reports checked Oct 31, 2026 last reported
Registrar REGRU-RU RU(RU)
Abuse contactabuse@reg.ru
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for migural.ru →
Hosting abuse contact abuse@reg.ru Domain names registrar REG.RU , Ltd · AS197695
RegistrationCreated Sep 3, 2015 — Expires Sep 3, 2027
WHOIS statusREGISTERED,
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://migural.ru/
Favicon Hash
Observed page title
МиГ Урал — Изделия из Мрамора и Гранита Урал
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 42 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Russia31.31.196.21
Network ASN
AS197695
Organization
Domain names registrar REG.RU , Ltd
Observed location
RussiaMoscow, RU
Server header
nginx

Nameservers 2

  • ns1.hosting.reg.ru
  • ns2.hosting.reg.ru

SOA

  • nsname: server208.hosting.reg.ru
  • hostmaster: support.reg.ru
  • serial: 2022041742
  • refresh: 10800
  • retry: 3600
  • expire: 604800
  • minttl: 86400

Mail routing 2 MX records

  • mx1.hosting.reg.rupriority 10
  • mx2.hosting.reg.rupriority 20

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-13 23:38:00
Valid until
2026-12-12 23:37:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint14a13aaddb93bfc7f1479db278fcb4a8bf8f99e77dcb3465eba81bbab0e692b9
Certificate names · 2 SANs
  • migural.ru
  • www.migural.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 · 31.31.196.21rapiddns.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.migural.ruDomain record
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
alphaMountain.ai
Chong Lua Dao
Gridinsoft
Seclookup
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of migural.ru · checked Oct 31, 2026

99
Good
Performance
FCP
1.26 s
First Contentful Paint
LCP
1.26 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
5 ms
Total Blocking Time
SI
3.28 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://migural.ru/
МиГ Урал — Изделия из Мрамора и Гранита Урал
Response
HTTP 200
HTML body
36.5 KB
Compressed
9.7 KB
Links
35 internal · 2 external
Detected technologies
jquerynginxwordpress
Selected response headers
Server: nginx
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 11a6206e52283ee404530545d790b93ff07d50ce1f41434f6af4ed32b93845dc
Saved response-header values · 8
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sat, 31 Oct 2026 19:10:12 GMT
Link
; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived

Captured network requests

Network requests: 28 SHA-256 hashes: 26 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-10-31 19:28 UTC.

Open this scan on URLScan 01a19368-e649-76da-abc0-674fab6051ec ↗

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 observations1

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_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-10-31 20:14:01.789535
    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 · in progress

Recorded events: 10. 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
    migural.ru detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 50
  • 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.
  • 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 · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    migural.ru

    View source
  5. 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

Check for cloaking

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

migural.ru

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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 Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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 migural.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/migural.ru"
  title="PhishDestroy threat report for migural.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>