Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 7. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
t-prolg.com favicon

t-prolg.com

In short

t-prolg.com is a MetaMask impersonation page detected by PhishDestroy on 2026-09-04.

“T-Pro”

Review the evidence
Registrar
Realtime
Resolved IP
104.21.48.188
Registered
Jul 22, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
Risk signals
VirusTotal detections: 7/90 Stored blocklist matches: 2 Automated brand label: MetaMask Scam type: Impersonation
VirusTotal
7 / 90
engine detections ·
OTX
5
community references
Cloudflare Radar
clean
source verdict
Page captures
8
open gallery
Domain age
96 days
Reports sent
1
view timeline
OTX: 5 refs Sep 4, 2026 1 Report Sent CDN
X Telegram API

Analysis

Domain summary

t-prolg.com is a MetaMask impersonation page detected by PhishDestroy on 2026-09-04. Risk: critical (100/100). Registrar: Realtime. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 7/90 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
7 / 90
OTX
5 community refs
Page captures
8
Page captures Source results Registration record

PhishDestroy threat report

Overview

t-prolg.com is an impersonation phishing site that presented itself under the page title "T-Pro". The domain name is built to pass as a T-Pro address at a glance, and its presence on the MetaMask and SEAL blocklists points to crypto users as the intended audience. PhishDestroy first detected it on 2026-09-04. The site has been offline since 2026-09-11, and its DNS was still inactive when we last checked on 2026-10-19.

How the scam works

Impersonation pages like this copy the name and look of a brand the victim already trusts. Traffic usually arrives through ads, direct messages or search results. Once the visitor accepts the fake T-Pro page as real, it asks for something valuable: login credentials, a seed phrase or private key, a deposit, or a wallet connection that ends in a malicious signature. Whatever is entered goes straight to the operators. Stolen account access or wallet control lets them move funds out quickly, and those transfers usually cannot be reversed.

Evidence

On 2026-09-06, seven of 90 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, SOCRadar and VIPRE. That is a minority of engines, but they come from several independent vendors. Two crypto-specific blocklists, MetaMask's and SEAL's, list it alongside PhishDestroy, so wallet software may warn users before they interact with the page. The domain also appears in five AlienVault OTX threat pulses, which shows that other researchers tracked it.

Infrastructure

The domain was registered through Realtime Register B.V. on 2026-07-22, about six weeks before PhishDestroy flagged it. The site resolved to Cloudflare, Inc. address space geolocated to Canada. Because Cloudflare acts as a reverse proxy, that address belongs to the content delivery network and does not identify the server that actually hosted the phishing page. The page went dark one week after our first detection.

What to do

If you entered a T-Pro password on this site, change it now, along with any account that reuses it, and turn on app-based 2FA. If you typed a seed phrase or private key into it, treat that wallet as compromised and move the remaining funds to a new wallet created on a clean device. If you connected a wallet or signed anything, review and revoke token approvals granted around 2026-09-04 to 2026-09-11. Defenders should block t-prolg.com and closely spelled T-Pro lookalikes, and watch for the same lure reappearing on newly registered domains.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 7 / 90 · OTX 5 references 9 sources

VirusTotal

7 / 90 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
48
Malicious
7
Suspicious
2
Undetected
35

Vendor labels

CRDF
malicious
G-Data
phishing
Lionic
phishing
Sophos
malware
Fortinet
spam
SOCRadar
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
spam

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Realtime Register B.V.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    dorthy.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::6815:30bc
  • TTL, seconds
    21600
    Type
    NS
    Value
    osmar.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::ac43:88c9
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.48.188
  • TTL, seconds
    21600
    Type
    NS
    Value
    dorthy.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.136.201

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • t-prolg.com
  • *.t-prolg.com
Issuer
Google Trust Services / WE1
Serial
1f879defba8ab7a60e72b19bf8b1d46a
SHA-256
98ceab13c35fe75d3c925de1f2d424be6a20a38169ee1b0722cd21dc98f29e86
Subject
t-prolg.com
Valid until
Valid from

Registration record

Registrar
Realtime Register B.V.
Registrar IANA ID
839
Registrar URL
http://www.realtimeregister.com
Registered
Updated
Expires
Status
  • clientHold
Nameservers
  • dorthy.ns.cloudflare.com
  • osmar.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • active
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 7,
    "suspicious": 2,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "malware",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "spam"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Realtime Register B.V.
Created
2026-07-22T10:42:33Z
Expires
2027-07-22T10:42:33Z
Updated
2026-09-20T10:43:17Z
First seen
2026-07-22T11:13:20Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "dorthy.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:30bc"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "osmar.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:88c9"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.48.188"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "dorthy.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.136.201"
    }
]
Dns at
2026-09-06T02:02:33Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "t-prolg.com",
        "*.t-prolg.com"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "1f879defba8ab7a60e72b19bf8b1d46a",
    "sha256": "98ceab13c35fe75d3c925de1f2d424be6a20a38169ee1b0722cd21dc98f29e86",
    "subject": "t-prolg.com",
    "valid_to": "2026-10-20T10:45:40Z",
    "valid_from": "2026-07-22T09:48:09Z"
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "registrar_iana_id": "839",
    "registrar_url": "http://www.realtimeregister.com",
    "created": "2026-07-22T10:42:33Z",
    "updated": "2026-09-20T10:43:17Z",
    "expires": "2027-07-22T10:42:33Z",
    "status": [
        "clientHold"
    ],
    "nameservers": [
        "dorthy.ns.cloudflare.com",
        "osmar.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-07-22T10:42:33Z",
        "last changed": "2026-09-20T10:43:18Z",
        "registration": "2026-07-22T10:42:33Z",
        "registrar expiration": "2027-07-22T10:42:33Z",
        "last update of RDAP database": "2026-10-11T22:14:21Z"
    }
}
Separate source record · 7 malicious + 2 suspicious / 92 · 2026-10-11 22:07:08 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-11T22:07:08Z
fetched_at
2026-10-23T03:51:13Z
stats
{"timeout":0,"harmless":48,"malicious":7,"suspicious":2,"undetected":35}

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a06d2d-bfbe-77ec-bbcf-76c8ba36f59d

Final URL

https://t-prolg.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://t-prolg.com/
    From
    http://t-prolg.com/
    Status
    307

IP address

104.21.48.188

Contacted domains

  • webapi.t-proses.com
  • e001-img.oss-cn-hongkong.aliyuncs.com
  • storage.googleapis.com

Contacted IP addresses

  • 142.251.127.207
  • 47.79.64.187
  • 104.21.11.89
  • 104.21.48.188

Autonomous systems (ASN)

  • 15169
  • 45102
  • 13335

Server countries

  • US
  • HK

Document hash

36cd0476230b64eb5ac1f9cf87e3fbed4d45e07d1cdacf7a0a226333689534a7

Script hashes

  • bcee984fd52b4a82bd6b23543bb33f6472e076c125edbdd8756d29ca230628cb
  • 5e8dbaf177dea2ae04a4f9ddf8fa3e0c75aa4a9ef40f29f4142ede98a4247d23
  • f49f5a0ed02f7c3dbb9a0bf55e82a499556784d2c99355dbdd7a29ae4bc1c17f
  • f1b8d1b55a1e7c9554485f7fb8670e36a73e55960de0878c4614e68c92be432f
  • 980b4cd838841ae8051d404ab19237b97baf4ad96b9b9b9073e64ab35bc97f11
  • df268d4a93f2872f725a62a4af5c730d7b805af971a15320cb0eda38c9a0b517
  • b189d35d4860077e6e9ac919aaba964dd433c590b33b20aec82c52394afbfdeb
  • e3b98450c9d05eab23939602b6630cfae819f35fd8ca79374971908b2e350a1d
  • 29290bfa987b5cd369b3a5a417afd46b7f9abe9ae20dd3d81f5fffdfddb3d3a0
  • 90ccce7b3c29cfc63be01fda9a355768a23d56dfd4ae545ab424d8436051175a

JavaScript globals

  • TradingView
  • addLink
  • addMeta
  • lib
  • rem
  • dpr
  • __INTLIFY_PROD_DEVTOOLS__
  • __INTLIFY_JIT_COMPILATION__
  • __INTLIFY_DROP_MESSAGE_COMPILER__
  • PubSub
  • __VUE_INSTANCE_SETTERS__
  • __VUE_I18N_FULL_INSTALL__
  • __VUE_I18N_LEGACY_API__
  • __config
  • __theme
  • __VUE__
  • __vite_is_modern_browser

Browser storage keys

  • lastRefreshTime
  • dev_THEME
  • main
  • dev_LANGUAGE
  • user
  • hasLoadedApp

TLS session and certificate

Subject alternative names
  • t-prolg.com
  • *.t-prolg.com
Cipher
AES_128_GCM
Issuer
WE1
Subject
t-prolg.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

61

Registered domain age, days

61

Certificate age, days

44

Certificate validity, days

90

Page requests

104

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • cryptoscam
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Crypto Scam
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a06d2d-bfbe-77ec-bbcf-76c8ba36f59d
Final url
https://t-prolg.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://t-prolg.com/",
        "from": "http://t-prolg.com/",
        "status": 307
    }
]
Ip
104.21.48.188
Contacted domains
[
    "webapi.t-proses.com",
    "e001-img.oss-cn-hongkong.aliyuncs.com",
    "storage.googleapis.com"
]
Contacted IP addresses
[
    "142.251.127.207",
    "47.79.64.187",
    "104.21.11.89",
    "104.21.48.188"
]
Asns
[
    "15169",
    "45102",
    "13335"
]
Countries
[
    "US",
    "HK"
]
Document hash
36cd0476230b64eb5ac1f9cf87e3fbed4d45e07d1cdacf7a0a226333689534a7
Script hashes
[
    "bcee984fd52b4a82bd6b23543bb33f6472e076c125edbdd8756d29ca230628cb",
    "5e8dbaf177dea2ae04a4f9ddf8fa3e0c75aa4a9ef40f29f4142ede98a4247d23",
    "f49f5a0ed02f7c3dbb9a0bf55e82a499556784d2c99355dbdd7a29ae4bc1c17f",
    "f1b8d1b55a1e7c9554485f7fb8670e36a73e55960de0878c4614e68c92be432f",
    "980b4cd838841ae8051d404ab19237b97baf4ad96b9b9b9073e64ab35bc97f11",
    "df268d4a93f2872f725a62a4af5c730d7b805af971a15320cb0eda38c9a0b517",
    "b189d35d4860077e6e9ac919aaba964dd433c590b33b20aec82c52394afbfdeb",
    "e3b98450c9d05eab23939602b6630cfae819f35fd8ca79374971908b2e350a1d",
    "29290bfa987b5cd369b3a5a417afd46b7f9abe9ae20dd3d81f5fffdfddb3d3a0",
    "90ccce7b3c29cfc63be01fda9a355768a23d56dfd4ae545ab424d8436051175a"
]
Globals
[
    "TradingView",
    "addLink",
    "addMeta",
    "lib",
    "rem",
    "dpr",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "PubSub",
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "__config",
    "__theme",
    "__VUE__",
    "__vite_is_modern_browser"
]
Storage keys
[
    "lastRefreshTime",
    "dev_THEME",
    "main",
    "dev_LANGUAGE",
    "user",
    "hasLoadedApp"
]
Tls
{
    "san": [
        "t-prolg.com",
        "*.t-prolg.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "t-prolg.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-20T10:45:40Z",
    "valid_from": "2026-07-22T09:48:09Z"
}
Domain age days
61
Apex age days
61
Tls age days
44
Tls valid days
90
Requests
104
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "cryptoscam"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Crypto Scam"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}

URLQuery

checked — no detections recorded

Open report

OTX

5 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

a86ccebd-1f6d-4320-abde-58da16c9ba00

Final URL

https://t-prolg.com/pc/

HTTP response

200

Navigation history

  • URL
    https://t-prolg.com/
    Status
    200
  • URL
    https://t-prolg.com/pc/
    Status
    200

DOM structure hash

1a441cddfed452733f2cb9a435f1636ef988ab24df044a8842d31645a012556c

Document hash

4d593b0f9e7bb90453a860ef6c3aa3449fd76a371b49128772d7ca102d128c15

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    t-prolg.com
    Type
    A
    Value
    104.21.48.188
  • Name
    t-prolg.com
    Type
    A
    Value
    172.67.136.201
  • Name
    t-prolg.com
    Type
    AAAA
    Value
    2606:4700:3037::ac43:88c9
  • Name
    t-prolg.com
    Type
    AAAA
    Value
    2606:4700:3031::6815:30bc

DNSSEC valid

No

IP address

104.21.48.188

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Nameservers
  • dorthy.ns.cloudflare.com
  • osmar.ns.cloudflare.com
Original source fields · JSON
Uuid
a86ccebd-1f6d-4320-abde-58da16c9ba00
Final url
https://t-prolg.com/pc/
Status
200
History
[
    {
        "url": "https://t-prolg.com/",
        "status": 200
    },
    {
        "url": "https://t-prolg.com/pc/",
        "status": 200
    }
]
DOM structure hash
1a441cddfed452733f2cb9a435f1636ef988ab24df044a8842d31645a012556c
Document hash
4d593b0f9e7bb90453a860ef6c3aa3449fd76a371b49128772d7ca102d128c15
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "t-prolg.com",
        "type": "A",
        "value": "104.21.48.188"
    },
    {
        "name": "t-prolg.com",
        "type": "A",
        "value": "172.67.136.201"
    },
    {
        "name": "t-prolg.com",
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:88c9"
    },
    {
        "name": "t-prolg.com",
        "type": "AAAA",
        "value": "2606:4700:3031::6815:30bc"
    }
]
Dnssec valid
false
Ip
104.21.48.188
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2026-07-22T10:42:33Z",
    "updated": "2026-07-22T10:44:39Z",
    "expires": "2027-07-22T10:42:33Z",
    "nameservers": [
        "dorthy.ns.cloudflare.com",
        "osmar.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

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
t-prolg.com — T-Pro Impersonation Phishing
ai_description
t-prolg.com is an impersonation phishing page posing as T-Pro, flagged by MetaMask and SEAL, aimed at crypto users who may hand over logins or wallet access.
ai_generated_at
2026-10-19T10:23:02Z
ai_generated_by
threat-anthropic
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

Every stored field, with its source and date

Questions about t-prolg.com

Is t-prolg.com legit?

No. PhishDestroy classifies t-prolg.com as a MetaMask impersonation page (risk: critical, 100/100); it was first detected on 2026-09-04. VirusTotal: 7/90 engines flag it. Treat the site as unsafe.

Is t-prolg.com safe to connect a wallet?

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

What should I do if I used t-prolg.com?

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

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded
StateStored capture
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)
t-prolg.com: Crypto scam — Blocked by MetaMask, flagged by SEAL, 7/90 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card t-prolg.com: Crypto scam — Blocked by MetaMask, flagged by SEAL, 7/90 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 09c760d69cc1

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Realtime (Unknown)
Abuse contactrtr-security-threats@realtimeregister.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for t-prolg.com →
RegistrationCreated Jul 22, 2026 (96d) — Expires Jul 22, 2027
Time to First Unavailability 6 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 4, 2026
Submitted URLhttp://t-prolg.com/
Favicon Hash
Case ID
Observed page title
T-Pro
Automated brand references
MetaMask
TLS Certificate
Issued by Google Trust Services · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.48.188
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dorthy.ns.cloudflare.com
  • osmar.ns.cloudflare.com

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-07-22 09:48:09
Valid until
2026-10-20 10:45:40
Hostname coverage
Stored certificate dates valid
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint98ceab13c35fe75d3c925de1f2d424be6a20a38169ee1b0722cd21dc98f29e86
Certificate names · 2 SANs
  • t-prolg.com
  • *.t-prolg.com

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

viewdns.info · 104.21.48.188rapiddns.io

Latest Classified Outcome 2026-10-26 08:55:08 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-10-25 02:19:15 UTC
RDAP registration
Observed timeline last reachable: 2026-09-07 22:14:38 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-07 22:14:38 UTC → 2026-09-30 16:14:55 UTC · 546.00h midpoint estimate ≈ 2026-09-19 07:14:46 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 90 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
Kaspersky
SOCRadar
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of t-prolg.com · checked Sep 4, 2026

35
Poor
Performance
FCP
3.82 s
First Contentful Paint
LCP
20.67 s
Largest Contentful Paint
CLS
0.112
Cumulative Layout Shift
TBT
867 ms
Total Blocking Time
SI
10.43 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
546
Estimate basis
Bounded by observations
Estimate precision
Low

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

Check for cloaking

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

t-prolg.com
Saved result
Unreachable
Stored observation history16

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

  1. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

Earlier observations 11
  1. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  9. Domain monitor · Recorded state

    Reachable→Unavailable

  10. VirusTotal · Detection count

    2→3

    Engines added
    SOCRadar
    Engines removed
    None recorded
    Recorded vendor total
    3
  11. Domain monitor · First collection record

    Reachable

All retained availability observations63

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. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:55:08.299319
    Evidence SHA-256
    13f28561b631b5fd33d263e0928c535133998dacb1f2439d111465a53138d829
    Evidence timestamp as recorded
    2026-10-26 09:55:08.299319
  2. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:55:08.299319
    Evidence SHA-256
    13f28561b631b5fd33d263e0928c535133998dacb1f2439d111465a53138d829
    Evidence timestamp as recorded
    2026-10-26 09:55:08.299319
  3. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:55:07.418941
    Evidence SHA-256
    28c9fce2cda0b3805fe3edb2f460115a0d4f3a503f13c8d21a9dd825651c668d
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
  4. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:55:07.418941
    Evidence SHA-256
    28c9fce2cda0b3805fe3edb2f460115a0d4f3a503f13c8d21a9dd825651c668d
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
  5. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:19:15.000000
    Evidence SHA-256
    f9c7b063762609ed2c05eb471283439374114b4ba43f1ebd03fd3aae29c35000
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:19:15
    Evidence reason
    unavailable
  6. 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-10-25 03:19:15.000000
    Evidence SHA-256
    f9c7b063762609ed2c05eb471283439374114b4ba43f1ebd03fd3aae29c35000
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:19:15
    Evidence reason
    unavailable
  7. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 22:56:16.207510
    Evidence SHA-256
    ddef624cdce5282db1a2273985b80abd1ec51e870abcdd0fb132591c1b12f9f4
    Evidence timestamp as recorded
    2026-10-23 22:56:16.207510
  8. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 22:56:16.207510
    Evidence SHA-256
    ddef624cdce5282db1a2273985b80abd1ec51e870abcdd0fb132591c1b12f9f4
    Evidence timestamp as recorded
    2026-10-23 22:56:16.207510
  9. 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-10-23 03:23:15.000000
    Evidence SHA-256
    8bfe41c50bc8ce22b66cf655e216481146df7bb6c67182c19c60db8daa23ffa0
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 03:23:15
    Evidence reason
    unavailable
  10. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 22:55:15.888363
    Evidence SHA-256
    5d418eb51df9b8c6d74209546748b7668ac29b85ae9abdb2669a9f23e1c93ded
    Evidence timestamp as recorded
    2026-10-22 22:55:15.888363
  11. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-22 22:55:15.888363
    Evidence SHA-256
    5d418eb51df9b8c6d74209546748b7668ac29b85ae9abdb2669a9f23e1c93ded
    Evidence timestamp as recorded
    2026-10-22 22:55:15.888363
  12. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 16:53:36.928467
    Evidence SHA-256
    36ca6315e479e2f31971bf6d3b12cbcb489e1e5031060db2e4e3a77a1ec0d1bc
    Evidence timestamp as recorded
    2026-10-21 16:53:36.928467
  13. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 16:53:36.928467
    Evidence SHA-256
    36ca6315e479e2f31971bf6d3b12cbcb489e1e5031060db2e4e3a77a1ec0d1bc
    Evidence timestamp as recorded
    2026-10-21 16:53:36.928467
  14. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:14:00.000000
    Evidence SHA-256
    3693155b52b711a71f78f343e71edecb6ebb9d4a308a7e600c1f6b91d7ec1090
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 03:14:00
    Evidence reason
    unavailable
  15. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 10:21:37.183325
    Evidence SHA-256
    8655d910ad503411f6c3ac31ef6b690e07ccfd5345beff2ff6f27aa9c8d03cbd
    Evidence timestamp as recorded
    2026-10-20 10:21:37.183325
  16. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-20 10:21:37.183325
    Evidence SHA-256
    8655d910ad503411f6c3ac31ef6b690e07ccfd5345beff2ff6f27aa9c8d03cbd
    Evidence timestamp as recorded
    2026-10-20 10:21:37.183325
  17. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 10:21:20.392196
    Evidence SHA-256
    7d8542a9f4fb036625d678a1e5c8ef28cb2ea6da6d773887db2c13cba1884ebd
    Evidence timestamp as recorded
    2026-10-19 10:21:20.392196
  18. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 10:21:20.392196
    Evidence SHA-256
    7d8542a9f4fb036625d678a1e5c8ef28cb2ea6da6d773887db2c13cba1884ebd
    Evidence timestamp as recorded
    2026-10-19 10:21:20.392196
  19. 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-10-19 03:13:39.000000
    Evidence SHA-256
    e538e41c29956b64f1a80db8782d1c9c6e503067fd3a28053a4a7351c83a0fb2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 03:13:39
    Evidence reason
    unavailable
  20. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-18 10:21:15.144873
    Evidence SHA-256
    21008aa06e53c33a48b4f2d580bb5fa7bb89e69ad466a5eac0ecacc9b0d239aa
    Evidence timestamp as recorded
    2026-10-18 10:21:15.144873
  21. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-18 10:21:15.144873
    Evidence SHA-256
    21008aa06e53c33a48b4f2d580bb5fa7bb89e69ad466a5eac0ecacc9b0d239aa
    Evidence timestamp as recorded
    2026-10-18 10:21:15.144873
  22. 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-10-17 03:12:34.000000
    Evidence SHA-256
    47b26f519df3a183a68769be789ef4320f19ef3fe1082917f5e453437c3959c5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-17 03:12:34
    Evidence reason
    unavailable
  23. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NXDOMAIN
    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-17 03:12:34.000000
    Evidence SHA-256
    ba6943c2b566905df496d00da133b7acadbe07c5daeb19d6e44a279303d07998
    Evidence timestamp as recorded
    2026-10-17 03:12:34
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  24. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-16 22:22:38.733165
    Evidence SHA-256
    325ec20907621c35f6ce46e547e42140404642149567e6e93fddc33a8bd374af
    Evidence timestamp as recorded
    2026-10-16 22:22:38.733165
  25. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-16 22:22:38.733165
    Evidence SHA-256
    325ec20907621c35f6ce46e547e42140404642149567e6e93fddc33a8bd374af
    Evidence timestamp as recorded
    2026-10-16 22:22:38.733165
  26. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 22:22:19.692675
    Evidence SHA-256
    b57a186ff0227f88bef5c1c9196d29e5e1e46b108d002523d7103218bdbfa456
    Evidence timestamp as recorded
    2026-10-15 22:22:19.692675
  27. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 22:22:19.692675
    Evidence SHA-256
    b57a186ff0227f88bef5c1c9196d29e5e1e46b108d002523d7103218bdbfa456
    Evidence timestamp as recorded
    2026-10-15 22:22:19.692675
  28. 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-10-15 03:12:45.000000
    Evidence SHA-256
    2339e1a1c58731d44dc8687dfd8896ff3b486776d83b4e6c92b62e4a649c5386
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 03:12:45
    Evidence reason
    unavailable
  29. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-14 22:21:26.687207
    Evidence SHA-256
    7421cc6cc9ae2e2b542829ae29de0fec760f6f79917b5aecad74f6d6b76202c3
    Evidence timestamp as recorded
    2026-10-14 22:21:26.687207
  30. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-14 22:21:26.687207
    Evidence SHA-256
    7421cc6cc9ae2e2b542829ae29de0fec760f6f79917b5aecad74f6d6b76202c3
    Evidence timestamp as recorded
    2026-10-14 22:21:26.687207
  31. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 22:21:07.146269
    Evidence SHA-256
    e11aa72fb636ff77b21b69403f36401f9e4b9ee1bb373b7733ef0c35501ecfe7
    Evidence timestamp as recorded
    2026-10-13 22:21:07.146269
  32. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 22:21:07.146269
    Evidence SHA-256
    e11aa72fb636ff77b21b69403f36401f9e4b9ee1bb373b7733ef0c35501ecfe7
    Evidence timestamp as recorded
    2026-10-13 22:21:07.146269
  33. 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-10-13 03:15:30.000000
    Evidence SHA-256
    8527c40765913c21685f332cefaac27e72a3677be25f64168c28a9d4c7cde369
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 03:15:30
    Evidence reason
    unavailable
  34. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-12 22:20:57.953315
    Evidence SHA-256
    b51da1bffddd174f641115e0ee43debcbd98219ab5681a6bfa7c3c60f8e8a4dc
    Evidence timestamp as recorded
    2026-10-12 22:20:57.953315
  35. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-12 22:20:57.953315
    Evidence SHA-256
    b51da1bffddd174f641115e0ee43debcbd98219ab5681a6bfa7c3c60f8e8a4dc
    Evidence timestamp as recorded
    2026-10-12 22:20:57.953315
  36. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 22:20:50.151913
    Evidence SHA-256
    812c3e0613a5f83dcce46efc2ff89b2699babd528627f426f34ba02bb46ff502
    Evidence timestamp as recorded
    2026-10-11 22:20:50.151913
  37. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 22:20:50.151913
    Evidence SHA-256
    812c3e0613a5f83dcce46efc2ff89b2699babd528627f426f34ba02bb46ff502
    Evidence timestamp as recorded
    2026-10-11 22:20:50.151913
  38. 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-10-11 03:14:15.000000
    Evidence SHA-256
    db145c749a415ace8daf9afa429bc62be93a7902235131a6ab1e5eda946f94a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 03:14:15
    Evidence reason
    unavailable
  39. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-10 22:20:48.858561
    Evidence SHA-256
    e889a69e638e4b99f08646ff552e08a5e00e8c10757070b22974368774e37dce
    Evidence timestamp as recorded
    2026-10-10 22:20:48.858561
  40. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-10 22:20:48.858561
    Evidence SHA-256
    e889a69e638e4b99f08646ff552e08a5e00e8c10757070b22974368774e37dce
    Evidence timestamp as recorded
    2026-10-10 22:20:48.858561
  41. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 22:20:42.401113
    Evidence SHA-256
    4ba0c4f5e4344e3b8f573b980beedd63ce44b8a9e40e19356498f928d28b0f89
    Evidence timestamp as recorded
    2026-10-09 22:20:42.401113
  42. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 22:20:42.401113
    Evidence SHA-256
    4ba0c4f5e4344e3b8f573b980beedd63ce44b8a9e40e19356498f928d28b0f89
    Evidence timestamp as recorded
    2026-10-09 22:20:42.401113
  43. 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-10-09 03:24:57.000000
    Evidence SHA-256
    454f0e1936eaba71e01beab30c2a01c23abac7bc95c68703fb8860a402ef0aee
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 03:24:57
    Evidence reason
    unavailable
  44. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-08 22:20:32.448533
    Evidence SHA-256
    8edb3f7a2fc304b8a5177c3ded626d4b057bb928567328c50d7173ba35619249
    Evidence timestamp as recorded
    2026-10-08 22:20:32.448533
  45. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-08 22:20:32.448533
    Evidence SHA-256
    8edb3f7a2fc304b8a5177c3ded626d4b057bb928567328c50d7173ba35619249
    Evidence timestamp as recorded
    2026-10-08 22:20:32.448533
  46. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    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-07 03:43:21.000000
    Evidence SHA-256
    6fb8d219ef0658544157ee081f9fd65596594fc9d8b2b20c6359bb49f88c298c
    Evidence timestamp as recorded
    2026-10-07 03:43:21
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  47. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 03:43:21.000000
    Evidence SHA-256
    f93726c56094000803bf21eadc4c73979fb53359e14282466ab8ee223eba452e
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-07 03:43:21
    Evidence reason
    transient_502
  48. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 00:13:39.270476
    Evidence SHA-256
    784b7ecbfd4d1f5c1f16811db27561f9397cfd12df6afd2ebacc11549485492a
    Evidence timestamp as recorded
    2026-10-07 00:13:39.270476
  49. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 00:13:39.270476
    Evidence SHA-256
    784b7ecbfd4d1f5c1f16811db27561f9397cfd12df6afd2ebacc11549485492a
    Evidence timestamp as recorded
    2026-10-07 00:13:39.270476
  50. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-06 00:13:39.266033
    Evidence SHA-256
    6c7931c23b94bd542e1a363178918666093733143cd28bece59cd4213edf8d91
    Evidence timestamp as recorded
    2026-10-06 00:13:39.266033
  51. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-06 00:13:39.266033
    Evidence SHA-256
    6c7931c23b94bd542e1a363178918666093733143cd28bece59cd4213edf8d91
    Evidence timestamp as recorded
    2026-10-06 00:13:39.266033
  52. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-05 00:13:35.837561
    Evidence SHA-256
    77e7d9ba0185b6198093d9e0f352c4cbcd747488876781a08693a3c8bc5d549f
    Evidence timestamp as recorded
    2026-10-05 00:13:35.837561
  53. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-05 00:13:35.837561
    Evidence SHA-256
    77e7d9ba0185b6198093d9e0f352c4cbcd747488876781a08693a3c8bc5d549f
    Evidence timestamp as recorded
    2026-10-05 00:13:35.837561
  54. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 18:16:30.317188
    Evidence SHA-256
    840b924a67ca79486e792b172d1b87f62f62ee384d32bc16ba39337f2f879ec1
    Evidence timestamp as recorded
    2026-10-03 18:16:30.317188
  55. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 18:16:30.317188
    Evidence SHA-256
    840b924a67ca79486e792b172d1b87f62f62ee384d32bc16ba39337f2f879ec1
    Evidence timestamp as recorded
    2026-10-03 18:16:30.317188
  56. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:36:06.000000
    Evidence SHA-256
    0b0d7e50fb3af4845bd362ab2461b7a11eb48b68e174896b63ec251ad7401909
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-03 03:36:06
    Evidence reason
    transient_502
  57. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-02 18:16:28.238873
    Evidence SHA-256
    5d3ae438f1bd62165937c39e51256e63486d0beeebca7f3425c78ec172cf9bba
    Evidence timestamp as recorded
    2026-10-02 18:16:28.238873
  58. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-02 18:16:28.238873
    Evidence SHA-256
    5d3ae438f1bd62165937c39e51256e63486d0beeebca7f3425c78ec172cf9bba
    Evidence timestamp as recorded
    2026-10-02 18:16:28.238873
  59. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 18:16:25.663717
    Evidence SHA-256
    67a7ebe23fe91bf233b75e7e64aa2bb873758e1184964d313eba6317c44a07c3
    Evidence timestamp as recorded
    2026-10-01 18:16:25.663717
  60. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 18:16:25.663717
    Evidence SHA-256
    67a7ebe23fe91bf233b75e7e64aa2bb873758e1184964d313eba6317c44a07c3
    Evidence timestamp as recorded
    2026-10-01 18:16:25.663717
  61. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:38:19.000000
    Evidence SHA-256
    f8555ae63ae7729e3ea3e9cffcfde886b6e8e3fa3e4606d8c065ea0d6b749f53
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-01 03:38:19
    Evidence reason
    transient_502
  62. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-09-30 18:14:55.856480
    Evidence SHA-256
    8d401fea30db1fdd3ca5b1e77bd91eb7b500ba9ae52e090028f06cf68c951184
    Evidence timestamp as recorded
    2026-09-30 18:14:55.856480
  63. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-09-30 18:14:55.856480
    Evidence SHA-256
    8d401fea30db1fdd3ca5b1e77bd91eb7b500ba9ae52e090028f06cf68c951184
    Evidence timestamp as recorded
    2026-09-30 18:14:55.856480

Threat Response Pipeline

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

Recorded events: 16. 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
    t-prolg.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable · VirusTotal detections +1 Recorded: 11 of 11
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 7/90
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 5. References are not vendor verdicts and are excluded from the evidence score.
  • Brand Impersonation
    Automated brand label: MetaMask
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Content Observed Unavailable
    Monitoring recorded an unavailable response; the cause was not independently established.
  • VirusTotal detections +1
    New detections: +1 (2 → 3): SOCRadar
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Realtime Register B.V.. Abuse contacts: 1.
    • rtr-security-threats@realtimeregister.com
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability Recorded: 3 of 3
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 149

Recorded activity

5 entries
  1. VirusTotal

    7/90 engine detections

    View source
  2. AlienVault OTX

    5 community references

    View source
  3. Abuse report sent

    PD-20260904-7CB9CC · Receipt 65454

    rtr-security-threats@realtimeregister.com
  4. Added to PhishDestroy

    t-prolg.com

    View source
  5. URLScan

    Page captured

    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

Lookalike domains

79 stored lookalike domains

etamask.io omission Internal report A 185.66.140.182MX etamask.ioNS ns13.knownsrv.com meetamask.io repetition Internal report A 185.66.140.182MX meetamask.ioNS ns13.knownsrv.com megamask.io replacement Internal report A 66.96.162.138MX alt1.aspmx.l.google.comNS ns1.domain.com metam.ask.io subdomain Internal report A 15.197.162.184 metamaak.io replacement Internal report A 185.66.140.182MX metamaak.ioNS ns13.knownsrv.com metamadk.io replacement Internal report A 185.66.140.182MX metamadk.ioNS ns13.knownsrv.com metamaks.io transposition Internal report A 185.66.140.182MX metamaks.ioNS ns13.knownsrv.com metamassk.io insertion Internal report A 185.66.140.182MX metamassk.ioNS ns13.knownsrv.com metamsask.io insertion Internal report A 185.66.140.182MX metamsask.ioNS ns13.knownsrv.com metamssk.io replacement Internal report A 185.66.140.182MX metamssk.ioNS ns13.knownsrv.com metanask.io homoglyph Internal report A 185.66.140.182MX metanask.ioNS ns13.knownsrv.com metanmask.io homoglyph Internal report A 185.66.140.182MX metanmask.ioNS ns13.knownsrv.com
Show all (67)
metasmask.io insertion Internal report A 185.66.140.182MX metasmask.ioNS ns13.knownsrv.com metramask.io insertion Internal report A 185.66.140.182MX metramask.ioNS ns13.knownsrv.com mewtamask.io insertion Internal report A 185.66.140.182MX mewtamask.ioNS ns13.knownsrv.com mmetamask.io homoglyph Internal report A 185.66.140.182MX mmetamask.ioNS ns13.knownsrv.com mtamask.io omission Internal report A 185.66.140.182MX mtamask.ioNS ns13.knownsrv.com mwetamask.io insertion Internal report A 185.66.140.182MX mwetamask.ioNS ns13.knownsrv.com nmetamask.io homoglyph Internal report A 185.66.140.182MX nmetamask.ioNS ns13.knownsrv.com metamark.io bitsquatting Internal report A 13.248.213.45MX mx0.123-reg.co.ukNS ns45.domaincontrol.com metamaskj.io addition Internal report A 185.66.140.182MX metamaskj.ioNS ns13.knownsrv.com metammask.io homoglyph Internal report A 185.66.140.182MX metammask.ioNS ns13.knownsrv.com metamnask.io homoglyph Internal report A 185.66.140.182MX metamnask.ioNS ns13.knownsrv.com emtamask.io transposition A 185.66.140.182MX emtamask.ioNS ns13.knownsrv.com m-etamask.io hyphenation A 104.247.81.99NS ns1.parkingcrew.net meamask.io omission A 185.66.140.182MX meamask.ioNS ns13.knownsrv.com meatmask.io transposition A 185.66.140.182MX meatmask.ioNS ns13.knownsrv.com meramask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mertamask.io insertion A 185.66.140.182MX mertamask.ioNS ns13.knownsrv.com metaamask.io repetition A 185.66.140.182MX metaamask.ioNS ns13.knownsrv.com metaamsk.io transposition A 185.66.140.182MX metaamsk.ioNS ns13.knownsrv.com metaask.io omission A 185.66.140.182MX metaask.ioNS ns13.knownsrv.com metalmask.io insertion A 15.197.148.33NS ns37.domaincontrol.com metamaask.io insertion A 185.66.140.182MX metamaask.ioNS ns13.knownsrv.com metamadsk.io insertion A 185.66.140.182MX metamadsk.ioNS ns13.knownsrv.com metamaek.io replacement A 172.65.190.172NS expire1.gname-dns.com metamak.io omission A 185.66.140.182MX metamak.ioNS ns13.knownsrv.com metamas.io omission A 185.66.140.182MX metamas.ioNS ns13.knownsrv.com metamasak.io insertion A 185.66.140.182MX metamasak.ioNS ns13.knownsrv.com metamasdk.io insertion A 185.66.140.182MX metamasdk.ioNS ns13.knownsrv.com metamask-io.com various A 13.248.169.48NS ns1.afternic.com metamasl.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metamasm.io replacement A 91.195.240.94NS ns1cnb.name.com metamsak.io transposition A 185.66.140.182MX metamsak.ioNS ns13.knownsrv.com metamsk.io omission A 185.66.140.182MX metamsk.ioNS ns13.knownsrv.com metamusk.io vowel-swap A 59.149.253.82NS ns1cnb.name.com metamzsk.io replacement A 91.195.240.94NS ns1cnb.name.com metarnask.io homoglyph NS ns15.domaincontrol.com metmaask.io transposition A 185.66.140.182MX metmaask.ioNS ns13.knownsrv.com metmask.io omission A 207.246.78.75NS ns1.dnsowl.com metsamask.io insertion A 185.66.140.182MX metsamask.ioNS ns13.knownsrv.com metsmask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mettamask.io repetition A !ServFailNS !ServFail metwmask.io replacement A 44.230.85.241NS curitiba.ns.porkbun.com metyamask.io insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metzmask.io replacement A 91.195.240.94NS ns1cnb.name.com meyamask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com meytamask.io insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mitamask.io vowel-swap A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mnetamask.io homoglyph A 185.66.140.182MX mnetamask.ioNS ns13.knownsrv.com mretamask.io insertion A 185.66.140.182MX mretamask.ioNS ns13.knownsrv.com mrtamask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mstamask.io replacement A 44.230.85.241NS curitiba.ns.porkbun.com mteamask.io transposition A 185.66.140.182MX mteamask.ioNS ns13.knownsrv.com mwtamask.io replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com rnetamask.io homoglyph A 34.42.100.71NS ns-cloud-a1.googledomains.com matamask.io bitsquatting A 216.245.197.45NS ns1.badgerdns.com mdtamask.io bitsquatting A 91.195.240.94NS ns1cnb.name.com metamasi.io bitsquatting A 91.195.240.94NS ns1cnb.name.com metamasj.io bitsquatting A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metamaska.io addition A 198.185.159.145MX alt1.aspmx.l.google.comNS ns-cloud-e1.googledomains.com metamaskk.io addition A 185.66.140.182MX metamaskk.ioNS ns13.knownsrv.com metamaskl.io addition A 185.66.140.182MX metamaskl.ioNS ns13.knownsrv.com metamaso.io bitsquatting A 44.230.85.241NS curitiba.ns.porkbun.com metamesk.io bitsquatting A 77.247.179.91NS ns1.badgerdns.com metamqsk.io bitsquatting A 91.195.240.94NS ns1cnb.name.com metemask.io bitsquatting A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com netamask.io homoglyph A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com xn--metamas-bhb.io homoglyph A 109.69.20.213NS aldo.ns.cloudflare.com

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 7 det. ChainPatrol URLQuery Report stored Scamadviser 80 trust SSL Labs Stored certificate dates valid CF Radar Open report OTX 5 refs WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260904-7CB9CC Recipient: rtr-security-threats@realtimeregister.com
Page title stored with report: T-Pro
PDF notice generated
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?

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

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

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

What information should I collect for my report?

FBI guidelines

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

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

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

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

Embed This Report

Share this threat intelligence on your website or blog

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