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

diyetisyenhasret.com

In short

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

“Redirecting...”

Review the evidence
Registrar
Realtime
Resolved IP
United States162.4.84.255ParkLogic Pty Ltd
Registered
Sep 29, 2025
First observed
Oct 25, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 16/92
VirusTotal
16 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 40
Page captures
2
open gallery
Domain age
393 days
OTX: 3 refs Oct 25, 2026
X Telegram API

Analysis

Domain summary

diyetisyenhasret.com is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Realtime. Status: Last known active. Hosting: ParkLogic Pty Ltd. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
16 / 92
Hosting
United States162.4.84.255ParkLogic Pty Ltd
Registrar
Realtime
Registered
Sep 29, 2025
OTX
3 community refs
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed diyetisyenhasret.com as a suspicious domain based on automated analysis. The page fetched on 2026-10-25 returned HTTP 200 and displayed the title “Redirecting…”. The domain first appeared in PhishDestroy's feed on 2026-10-25.

How the scam works

The detections suggest the site could be used for phishing, fraud or malware distribution, but no specific malicious payload or credential‑stealing form was observed on the page. Such domains typically lure users with redirects or deceptive content to capture personal data or deliver malicious code.

Evidence

VirusTotal scanned the domain on 2026-10-20 and flagged it as malicious by 13 vendors and suspicious by 3, out of 92 engines (16 total detections). Google Safe Browsing checked on 2026-10-25 reported no warning. urlscan captured the site on 2026-08-11 and gave a clean overall verdict, though its engine score marked it as potentially malicious. OTX listed three pulses mentioning the domain, and PhishDestroy's internal blocklist marked it as blocked while no external blocklists reported it.

Infrastructure

The domain was registered on 2025-09-29 through Realtime Register B.V. and is hosted on IP 162.4.84.255, belonging to ParkLogic Pty Ltd in the United States. TLS is provided by a Let's Encrypt certificate valid from 2026-10-03 to 2027-01-01. Authoritative nameservers are ns1.rr585.parklogic.com and ns2.rr585.parklogic.com.

What to do

If you visited the site and entered any credentials, change those passwords immediately and enable multi‑factor authentication where possible. Monitor your accounts for unexpected activity and consider blocking the domain at the network perimeter. Security teams should add the domain to blocklists, review logs for connections to the recorded IP, and keep the TLS certificate details for future reference.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T08:35:47Z)VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 16 / 92 · OTX 3 references 8 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
13
Suspicious
3
Undetected
30

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Created

Updated

First seen

DNS records

  • TTL, seconds
    14400
    Type
    TXT
    Value
    v=spf1 -all
  • TTL, seconds
    14400
    Type
    A
    Value
    172.236.114.219
  • TTL, seconds
    14400
    Type
    A
    Value
    172.238.170.106
  • TTL, seconds
    14400
    Type
    MX
    Value
    mx156.hostedmxserver.com
    Priority
    130
  • TTL, seconds
    14400
    Type
    NS
    Value
    ns2.parklogic.com
  • TTL, seconds
    14400
    Type
    A
    Value
    172.239.193.33
  • TTL, seconds
    14400
    Type
    NS
    Value
    ns1.parklogic.com
  • TTL, seconds
    14400
    Type
    SOA
    Responsible mailbox
    hostmaster.diyetisyenhasret.com
    Value
    ns1.parklogic.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5

Certificate

Subject alternative names
  • diyetisyenhasret.com
Issuer
Let's Encrypt / YE2
Serial
640cb928b972c1924b301b719e40cfb14ee
SHA-256
a29fc4fd28d92d4e8ddc17d252ee3743182e01344c630ccffe5e90b9bca4f515
Subject
diyetisyenhasret.com
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
  • pending delete
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
REALTIME REGISTER B.V.
Registrar IANA ID
839
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Created
2025-09-29T00:00:00Z
Updated
2025-09-29T00:00:00Z
First seen
2025-10-02T16:04:15Z
DNS records
[
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 -all"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "172.236.114.219"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "172.238.170.106"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "mx156.hostedmxserver.com",
        "priority": 130
    },
    {
        "ttl": 14400,
        "type": "NS",
        "value": "ns2.parklogic.com"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "172.239.193.33"
    },
    {
        "ttl": 14400,
        "type": "NS",
        "value": "ns1.parklogic.com"
    },
    {
        "ttl": 14400,
        "type": "SOA",
        "rname": "hostmaster.diyetisyenhasret.com",
        "value": "ns1.parklogic.com"
    }
]
Dns at
2026-10-19T23:32:12Z
Jarm
27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5
Certificate
{
    "san": [
        "diyetisyenhasret.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "640cb928b972c1924b301b719e40cfb14ee",
    "sha256": "a29fc4fd28d92d4e8ddc17d252ee3743182e01344c630ccffe5e90b9bca4f515",
    "subject": "diyetisyenhasret.com",
    "valid_to": "2027-01-01T20:51:23Z",
    "valid_from": "2026-10-03T20:51:24Z"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "pending delete"
    ],
    "events": {
        "expiration": "2026-09-29T08:27:55Z",
        "last changed": "2026-09-29T08:30:15Z",
        "registration": "2025-09-29T08:27:55Z",
        "registrar expiration": "2026-09-29T08:27:55Z",
        "last update of RDAP database": "2026-10-19T23:32:02Z"
    },
    "registrar": "REALTIME REGISTER B.V.",
    "registrar_iana_id": "839"
}
Separate source record · 13 malicious + 3 suspicious / 92 · 2026-10-19 23:31:48 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-19T23:31:48Z
fetched_at
2026-10-25T09:13:52Z
stats
{"timeout":0,"harmless":46,"malicious":13,"suspicious":3,"undetected":30}

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

176cc9e6-b725-4d6b-8b52-836be5826703

Final URL

https://diyetisyenhasret.com/

Navigation history

  • URL
    https://diyetisyenhasret.com/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    diyetisyenhasret.com
    Type
    A
    Value
    162.4.84.255

DNSSEC valid

No

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Nameservers
  • ns1.rr585.parklogic.com
  • ns2.rr585.parklogic.com
Original source fields · JSON
Uuid
176cc9e6-b725-4d6b-8b52-836be5826703
Final url
https://diyetisyenhasret.com/
History
[
    {
        "url": "https://diyetisyenhasret.com/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "diyetisyenhasret.com",
        "type": "A",
        "value": "162.4.84.255"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2025-09-29T08:27:55Z",
    "updated": "2026-09-30T08:09:41Z",
    "expires": "2027-09-29T08:27:55Z",
    "nameservers": [
        "ns1.rr585.parklogic.com",
        "ns2.rr585.parklogic.com"
    ]
}

URLScan

Malicious · engine verdict · score 40

Open report
URLScanOriginal source recordObserved: 7 fields

Observed: · Retrieved:

Report ID

019ff16b-029c-727e-be7f-9d8e54eb7a74

Final URL

https://diyetisyenhasret.com/

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

315

Registered domain age, days

315

Page requests

5

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
40
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
019ff16b-029c-727e-be7f-9d8e54eb7a74
Final url
https://diyetisyenhasret.com/
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
315
Apex age days
315
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 40,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
019ff16b-029c-727e-be7f-9d8e54eb7a74
score
null
malicious
null
result_at
null
enriched_at
2026-10-25T09:10:48Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-25 10:10:48"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T09:20:42Z

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

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

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
diyetisyenhasret.com — Suspicious Domain
ai_description
PhishDestroy flagged diyetisyenhasret.com as suspicious after VirusTotal recorded 13 malicious and 3 suspicious detections; urlscan reported a clean verdict.
ai_generated_at
2026-10-25T09:20:11Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

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

Mail configuration

MX records
  • mx156.hostedmxserver.com
SPF record
v=spf1 -all
SPF lookups
0

CAA records

Count
1
Domain
diyetisyenhasret.com
Allowed issuers
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Trackers

Requests
2

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    45.79.197.241
    Host
    ns2.parklogic.com
  • IP address
    69.39.238.36
    Host
    ns1.parklogic.com
DNS zone
diyetisyenhasret.com

Location

IP address
162.4.84.255
ASN
154653
Organization
ParkLogic Pty Ltd
City
Los Angeles
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
diyetisyenhasret.com

DNS records

A
  • 162.4.84.255
MX
  • Mail server
    mx156.hostedmxserver.com
    Priority
    10
NS
  • ns1.parklogic.com
  • ns2.parklogic.com
SOA
Primary nameserver
ns1.parklogic.com
Hostmaster
hostmaster.parklogic.com
Serial
1
Refresh, seconds
86400
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
300
TXT
  • v=spf1 -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
162.4.84.255
IP version
4

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.rr585.parklogic.com
  • ns2.rr585.parklogic.com
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mx156.hostedmxserver.com"
    ],
    "spf": "v=spf1 -all",
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "diyetisyenhasret.com",
    "issuers": [
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Trackers
{
    "requests": 2
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "45.79.197.241",
            "host": "ns2.parklogic.com"
        },
        {
            "ip": "69.39.238.36",
            "host": "ns1.parklogic.com"
        }
    ],
    "zone": "diyetisyenhasret.com"
}
Location
{
    "ip": "162.4.84.255",
    "asn": "154653",
    "org": "ParkLogic Pty Ltd",
    "city": "Los Angeles",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "diyetisyenhasret.com"
}
DNS records
{
    "A": [
        "162.4.84.255"
    ],
    "MX": [
        "{\"exchange\": \"mx156.hostedmxserver.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns1.parklogic.com",
        "ns2.parklogic.com"
    ],
    "SOA": "{\"nsname\": \"ns1.parklogic.com\", \"hostmaster\": \"hostmaster.parklogic.com\", \"serial\": 1, \"refresh\": 86400, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 300}",
    "TXT": [
        "v=spf1 -all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "162.4.84.255",
    "family": 4
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2025-09-29T08:27:55Z",
    "updated": "2026-09-30T08:09:41Z",
    "expires": "2027-09-29T08:27:55Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.rr585.parklogic.com",
        "ns2.rr585.parklogic.com"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Malware Security threats
View full Cloudflare Radar report

Questions about diyetisyenhasret.com

Is diyetisyenhasret.com legit?

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

Is diyetisyenhasret.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on diyetisyenhasret.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 diyetisyenhasret.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 matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded
StateStored capture
Final URLhttps://diyetisyenhasret.com/
Position1 / 2
Open capture Wayback Download
All capture links and hashes (2)
diyetisyenhasret.com: caution — 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card diyetisyenhasret.com: caution — 16/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 16a761d21f04

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 40 report ↗
IP Reputation United States162.4.84.255 abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Realtime
Abuse contact["rtr-security-threats@realtimeregister.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for diyetisyenhasret.com →
RegistrationCreated Sep 29, 2025 — Expires Sep 29, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 98/100
Submitted URLhttp://diyetisyenhasret.com/
Favicon Hash
Observed page title
Redirecting...
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 65 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States162.4.84.255
Network ASN
AS154653
Organization
ParkLogic Pty Ltd
Observed location
United StatesLos Angeles, US
Server header
openresty

Nameservers 2

  • ns1.rr585.parklogic.com
  • ns2.rr585.parklogic.com

SOA

  • nsname: ns1.parklogic.com
  • hostmaster: hostmaster.parklogic.com
  • serial: 1
  • refresh: 86400
  • retry: 7200
  • expire: 1209600
  • minttl: 300

Mail routing 1 MX record

  • mx156.hostedmxserver.compriority 130

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-03 20:51:24
Valid until
2027-01-01 20:51:23
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta29fc4fd28d92d4e8ddc17d252ee3743182e01344c630ccffe5e90b9bca4f515
Certificate names · 1 SAN
  • diyetisyenhasret.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 · 162.4.84.255rapiddns.io

Latest Classified Outcome 2026-10-27 11:05:00 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-27 11:05:00 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:00:27 UTC last content: 2026-10-25 23:00:27 UTC
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.
Recorded subdomains7

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

  • autodiscover.diyetisyenhasret.comDomain record
  • cpanel.diyetisyenhasret.comDomain record
  • cpcalendars.diyetisyenhasret.comDomain record
  • cpcontacts.diyetisyenhasret.comDomain record
  • webdisk.diyetisyenhasret.comDomain record
  • webmail.diyetisyenhasret.comDomain record
  • www.diyetisyenhasret.comDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

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

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

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

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. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations9

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

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:05:00.000000
    Evidence SHA-256
    1df602c3fde24bf072e4a9467631b83d9f8f62b0c0c01eee02417fb42367bcf9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:05:00
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:05:00.000000
    Evidence SHA-256
    1df602c3fde24bf072e4a9467631b83d9f8f62b0c0c01eee02417fb42367bcf9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:05:00
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:00:24.000000
    Evidence SHA-256
    f687be474b50713e18bd1325757c1ce90d5e8a7443f9a458d48d0e1055be2043
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:00:24
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:00:24.000000
    Evidence SHA-256
    f687be474b50713e18bd1325757c1ce90d5e8a7443f9a458d48d0e1055be2043
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:00:24
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:27.000000
    Evidence SHA-256
    181a6d5c691dd8a9868411bfe8a19b59f9b46f96910393e2b090593e88763a49
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:27
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:27.000000
    Evidence SHA-256
    181a6d5c691dd8a9868411bfe8a19b59f9b46f96910393e2b090593e88763a49
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:27
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:26.000000
    Evidence SHA-256
    4112101dc0de27b5fdfbe325ce436fa96ac9b69303bfb0f0c460d6a9307430bd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:26
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:26.000000
    Evidence SHA-256
    4112101dc0de27b5fdfbe325ce436fa96ac9b69303bfb0f0c460d6a9307430bd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:26
    Evidence reason
    alive_content
  9. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:45:30.128672
    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
    diyetisyenhasret.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · 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: 40
  • 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: 16/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as malware, Security threats
  • 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

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    16/92 engine detections

    View source
  3. Added to PhishDestroy

    diyetisyenhasret.com

    View source
  4. URLScan

    Malicious · engine verdict · score 40

    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.

diyetisyenhasret.com

Evidence & External Reports

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

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 diyetisyenhasret.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/diyetisyenhasret.com"
  title="PhishDestroy threat report for diyetisyenhasret.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>