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

karamanozsahin.com

In short

PhishDestroy records that karamanozsahin.com returned a browser connection reset error instead of loading any page content.

“karamanozsahin.com - Berlin”

Registrar
Realtime
Resolved IP
Türkiye77.245.159.32Niobe Bilisim Ltd. Sti.
Registered
Jul 1, 2025
First observed
Oct 30, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
VirusTotal detections: 17/92
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 90
Page captures
open gallery
Domain age
registered 2025-07-01 according to WHOIS
OTX: 5 refs Oct 30, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records that karamanozsahin.com returned a browser connection reset error instead of loading any page content.

Critical
Status
Server error
VirusTotal
17 / 92
Hosting
Türkiye77.245.159.32Niobe Bilisim Ltd. Sti.
Registrar
Realtime
Registered
Jul 1, 2025
OTX
5 community refs
Page captures
4

PhishDestroy analysis, reviewed version

The captured page for karamanozsahin.com is a browser-generated error screen rather than a website. It displays the heading "This site can't be reached" with the explanation "The connection was reset" and the code ERR_CONNECTION_RESET, alongside suggestions to check the connection, proxy, or firewall. The only interactions offered are Details and Reload buttons, so no site content, branding, or form was reachable at capture time.

The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 17 / 92 · OTX 5 references 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
42
Malicious
14
Suspicious
3
Undetected
33

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
malware
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

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    77.245.159.32
  • TTL, seconds
    300
    Type
    MX
    Value
    mail.karamanozsahin.com
    Priority
    10
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 +a +mx include:_spf.hosting.com.tr -all
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    noc.hosting.com.tr
    Value
    ns1.hosting.com.tr
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.hosting.com.tr
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.hosting.com.tr

DNS records observed

JARM fingerprint

29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae

Certificate

Subject alternative names
  • autoconfig.karamanozsahin.com
  • autodiscover.karamanozsahin.com
  • cpanel.karamanozsahin.com
  • cpcalendars.karamanozsahin.com
  • cpcontacts.karamanozsahin.com
  • mail.karamanozsahin.com
  • webdisk.karamanozsahin.com
  • webmail.karamanozsahin.com
  • www.karamanozsahin.com
Issuer
Let's Encrypt / YR2
Serial
5a1f32e5bea1df322ee0199b0f2bca79eb9
SHA-256
ab77cc51d639186abccd9e1415955747857158b094d409fa5099c4553e8e723d
Subject
webmail.karamanozsahin.com
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
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": 42,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "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
Created
2025-07-01T00:00:00Z
Updated
2025-07-01T00:00:00Z
First seen
2025-07-04T07:30:38Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "77.245.159.32"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mail.karamanozsahin.com",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 +a +mx include:_spf.hosting.com.tr -all"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "noc.hosting.com.tr",
        "value": "ns1.hosting.com.tr"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.hosting.com.tr"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.hosting.com.tr"
    }
]
Dns at
2026-10-27T13:21:48Z
Jarm
29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae
Certificate
{
    "san": [
        "autoconfig.karamanozsahin.com",
        "autodiscover.karamanozsahin.com",
        "cpanel.karamanozsahin.com",
        "cpcalendars.karamanozsahin.com",
        "cpcontacts.karamanozsahin.com",
        "mail.karamanozsahin.com",
        "webdisk.karamanozsahin.com",
        "webmail.karamanozsahin.com",
        "www.karamanozsahin.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5a1f32e5bea1df322ee0199b0f2bca79eb9",
    "sha256": "ab77cc51d639186abccd9e1415955747857158b094d409fa5099c4553e8e723d",
    "subject": "webmail.karamanozsahin.com",
    "valid_to": "2027-01-08T23:43:43Z",
    "valid_from": "2026-10-10T23:43:44Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-07-01T11:38:16Z",
        "last changed": "2026-06-27T05:00:47Z",
        "registration": "2025-07-01T11:38:16Z",
        "registrar expiration": "2027-07-01T11:38:16Z",
        "last update of RDAP database": "2026-10-27T13:21:47Z"
    },
    "registrar": "REALTIME REGISTER B.V.",
    "registrar_iana_id": "839"
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-27 13:16:15 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-27T13:16:15Z
fetched_at
2026-10-30T01:38:53Z
stats
{"timeout":0,"harmless":42,"malicious":14,"suspicious":3,"undetected":33}

URLScan

Malicious · engine verdict · score 90

SHA-256 e978014e4fb97edf813c882d8180e9f8fcdaaf42281ad8308417f4a4694bf280

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a18a57-71e5-739c-9013-0d8f840fcdfb

Final URL

https://karamanozsahin.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://karamanozsahin.com/
    From
    http://karamanozsahin.com/
    Status
    307

IP address

77.245.159.32

Reverse DNS (PTR)

hubble.wlsrv.com

Contacted IP addresses

  • 77.245.159.32

Autonomous systems (ASN)

  • 42868

Server countries

  • TR

Linked domains

  • www.facebook.com
  • www.instagram.com

Social media links

  • https://www.facebook.com
  • https://www.instagram.com

Document hash

04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

Script hashes

  • 5a57e63c2cf2ad7e32f9c425527980c3765d1a04d36ae496cb704902b76b2ffc
  • 978c43dd4cf30a18c05dbb24d4e5e78d6d439e971cd153ad0049d54061ae7a0c
  • b670e6d6aabf1d69ba6554d6a772984c2173572f0046cf00c2388c871279fcb8
  • d6090d98c7c30ae82ffd7902999ddbfa2cd634f9332d460606ba5f5752419ce0
  • 308286042373b2a407eadb094f5dd37dd29dc12e62a030f2405af91125ab5fb8
  • 6003c40cbb1494462fff333119e502690bdddff1f4ab2ff5214a9aed1c0ae72a
  • bd500764f50617e46687288dd3b3f7a623ab3692bde6d312be4f1872e67c230e

JavaScript globals

  • webcard
  • extraPath
  • webpackChunkcore_bundle
  • jQuery
  • $
  • Class
  • extendAvailable
  • cms
  • editor
  • __core-js_shared__
  • core
  • Animations
  • ElementBase
  • ElementAudio
  • ElementButton
  • ElementContainer
  • ElementDocument
  • ElementFacebook
  • ElementForm
  • ElementGallery
  • ElementGrid
  • ElementHeadline
  • ElementHtml
  • ElementIcon
  • ElementIframe
  • ElementSvg
  • ElementImage
  • ElementLogo
  • ElementMap
  • ElementMenu
  • ElementReference
  • ElementSection
  • ElementSeparator
  • ElementSlider
  • ElementContentSlider
  • ElementSpacer
  • ElementText
  • ElementVideo
  • ElementYoutube
  • ElementVimeo

Domain age, days

484

Registered domain age, days

484

Certificate age, days

19

Certificate validity, days

89

Page requests

56

Provider verdicts

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

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a18a57-71e5-739c-9013-0d8f840fcdfb
Final url
https://karamanozsahin.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://karamanozsahin.com/",
        "from": "http://karamanozsahin.com/",
        "status": 307
    }
]
Ip
77.245.159.32
Ptr
hubble.wlsrv.com
Contacted IP addresses
[
    "77.245.159.32"
]
Asns
[
    "42868"
]
Countries
[
    "TR"
]
Linked domains
[
    "www.facebook.com",
    "www.instagram.com"
]
Social
[
    "https://www.facebook.com",
    "https://www.instagram.com"
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Script hashes
[
    "5a57e63c2cf2ad7e32f9c425527980c3765d1a04d36ae496cb704902b76b2ffc",
    "978c43dd4cf30a18c05dbb24d4e5e78d6d439e971cd153ad0049d54061ae7a0c",
    "b670e6d6aabf1d69ba6554d6a772984c2173572f0046cf00c2388c871279fcb8",
    "d6090d98c7c30ae82ffd7902999ddbfa2cd634f9332d460606ba5f5752419ce0",
    "308286042373b2a407eadb094f5dd37dd29dc12e62a030f2405af91125ab5fb8",
    "6003c40cbb1494462fff333119e502690bdddff1f4ab2ff5214a9aed1c0ae72a",
    "bd500764f50617e46687288dd3b3f7a623ab3692bde6d312be4f1872e67c230e"
]
Globals
[
    "webcard",
    "extraPath",
    "webpackChunkcore_bundle",
    "jQuery",
    "$",
    "Class",
    "extendAvailable",
    "cms",
    "editor",
    "__core-js_shared__",
    "core",
    "Animations",
    "ElementBase",
    "ElementAudio",
    "ElementButton",
    "ElementContainer",
    "ElementDocument",
    "ElementFacebook",
    "ElementForm",
    "ElementGallery",
    "ElementGrid",
    "ElementHeadline",
    "ElementHtml",
    "ElementIcon",
    "ElementIframe",
    "ElementSvg",
    "ElementImage",
    "ElementLogo",
    "ElementMap",
    "ElementMenu",
    "ElementReference",
    "ElementSection",
    "ElementSeparator",
    "ElementSlider",
    "ElementContentSlider",
    "ElementSpacer",
    "ElementText",
    "ElementVideo",
    "ElementYoutube",
    "ElementVimeo"
]
Domain age days
484
Apex age days
484
Tls age days
19
Tls valid days
89
Requests
56
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 90,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}

OTX

5 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

d52ed373-86d5-44a4-b22f-aee9e8ccdf4c

Final URL

https://karamanozsahin.com/

Navigation history

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

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    karamanozsahin.com
    Type
    A
    Value
    77.245.159.32

DNSSEC valid

No

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Nameservers
  • ns1.hosting.com.tr
  • ns2.hosting.com.tr
Original source fields · JSON
Uuid
d52ed373-86d5-44a4-b22f-aee9e8ccdf4c
Final url
https://karamanozsahin.com/
History
[
    {
        "url": "https://karamanozsahin.com/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "karamanozsahin.com",
        "type": "A",
        "value": "77.245.159.32"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2025-07-01T11:38:16Z",
    "updated": "2025-07-01T11:38:17Z",
    "expires": "2027-07-01T11:38:16Z",
    "nameservers": [
        "ns1.hosting.com.tr",
        "ns2.hosting.com.tr"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
karamanozsahin.com — connection reset error page
ai_description
PhishDestroy records that karamanozsahin.com returned a browser connection reset error instead of loading any page content.
ai_summary
The captured page for karamanozsahin.com is a browser-generated error screen rather than a website. It displays the heading "This site can't be reached" with the explanation "The connection was reset" and the code ERR_CONNECTION_RESET, alongside suggestions to check the connection, proxy, or firewall. The only interactions offered are Details and Reload buttons, so no site content, branding, or form was reachable at capture time. The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 02:40:33
revision
4b666e43fc1c397147da28f6fe955ae1cce7141b897e9e54ed447c9f621ae455
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

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

Mail configuration

MX records
  • mail.karamanozsahin.com
SPF record
v=spf1 +a +mx include:_spf.hosting.com.tr -all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
3

CAA records

Domain
karamanozsahin.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
37566

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
  • 21
  • 25
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995

DNS servers

Nameservers
  • IP address
    77.245.156.176
    Host
    ns1.hosting.com.tr
  • IP address
    104.247.178.109
    Host
    ns2.hosting.com.tr
DNS zone
karamanozsahin.com

Location

IP address
77.245.159.32
ASN
42868
Organization
Niobe Bilisim Ltd. Sti.
City
Pendik
Country
TR

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
webmail.karamanozsahin.com

DNS records

A
  • 77.245.159.32
MX
  • Mail server
    mail.karamanozsahin.com
    Priority
    10
NS
  • ns2.hosting.com.tr
  • ns1.hosting.com.tr
SOA
Primary nameserver
ns1.hosting.com.tr
Hostmaster
noc.hosting.com.tr
Serial
2026102601
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
300
TXT
  • v=spf1 +a +mx include:_spf.hosting.com.tr -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
77.245.159.32
IP version
4

Subdomains

Count
9
Subdomains
  • autoconfig.karamanozsahin.com
  • autodiscover.karamanozsahin.com
  • cpanel.karamanozsahin.com
  • cpcalendars.karamanozsahin.com
  • cpcontacts.karamanozsahin.com
  • mail.karamanozsahin.com
  • webdisk.karamanozsahin.com
  • webmail.karamanozsahin.com
  • www.karamanozsahin.com

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.hosting.com.tr
  • ns2.hosting.com.tr
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mail.karamanozsahin.com"
    ],
    "spf": "v=spf1 +a +mx include:_spf.hosting.com.tr -all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 3
}
Caa records
{
    "domain": "karamanozsahin.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-15T20:54:58Z",
    "first": "2026-10-15T20:54:58Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 37566
}
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": [
        21,
        25,
        80,
        110,
        143,
        443,
        587,
        993,
        995
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "77.245.156.176",
            "host": "ns1.hosting.com.tr"
        },
        {
            "ip": "104.247.178.109",
            "host": "ns2.hosting.com.tr"
        }
    ],
    "zone": "karamanozsahin.com"
}
Location
{
    "ip": "77.245.159.32",
    "asn": "42868",
    "org": "Niobe Bilisim Ltd. Sti.",
    "city": "Pendik",
    "country": "TR"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "webmail.karamanozsahin.com"
}
DNS records
{
    "A": [
        "77.245.159.32"
    ],
    "MX": [
        "{\"exchange\": \"mail.karamanozsahin.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns2.hosting.com.tr",
        "ns1.hosting.com.tr"
    ],
    "SOA": "{\"nsname\": \"ns1.hosting.com.tr\", \"hostmaster\": \"noc.hosting.com.tr\", \"serial\": 2026102601, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 300}",
    "TXT": [
        "v=spf1 +a +mx include:_spf.hosting.com.tr -all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "77.245.159.32",
    "family": 4
}
Subdomains
{
    "count": 9,
    "subdomains": [
        "autoconfig.karamanozsahin.com",
        "autodiscover.karamanozsahin.com",
        "cpanel.karamanozsahin.com",
        "cpcalendars.karamanozsahin.com",
        "cpcontacts.karamanozsahin.com",
        "mail.karamanozsahin.com",
        "webdisk.karamanozsahin.com",
        "webmail.karamanozsahin.com",
        "www.karamanozsahin.com"
    ]
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2025-07-01T11:38:16Z",
    "updated": "2025-07-01T11:38:17Z",
    "expires": "2027-07-01T11:38:16Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.hosting.com.tr",
        "ns2.hosting.com.tr"
    ]
}

Questions about karamanozsahin.com

Is karamanozsahin.com legit?

PhishDestroy records that karamanozsahin.com returned a browser connection reset error instead of loading any page content.

Is karamanozsahin.com safe to connect a wallet?

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

What should I do if I used karamanozsahin.com?

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

Explore

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

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)
karamanozsahin.com: caution — 17/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card karamanozsahin.com: caution — 17/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v bb621f8f4d17

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 90 report ↗
IP Reputation Türkiye77.245.159.32 abuse score 0/100 0 reports checked Oct 30, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Hosting abuse contact abuse@hosting.com.tr Niobe Bilisim Ltd. Sti. · AS42868
RegistrationCreated Jul 1, 2025 — Expires Jul 1, 2027
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 30, 2026
DOM Analysisanalyzed Oct 30, 2026score 10/1003 brand signals
Submitted URLhttp://karamanozsahin.com/
Favicon Hash
Observed page title
karamanozsahin.com - Berlin
Automated brand references
Celer Facebook Instagram
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 70 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Türkiye77.245.159.32
Network ASN
AS42868
Organization
Niobe Bilisim Ltd. Sti.
Observed location
TürkiyePendik, TR

Nameservers 2

  • ns1.hosting.com.tr
  • ns2.hosting.com.tr

SOA

  • nsname: ns1.hosting.com.tr
  • hostmaster: noc.hosting.com.tr
  • serial: 2026102601
  • refresh: 3600
  • retry: 1800
  • expire: 1209600
  • minttl: 300

Mail routing 1 MX record

  • mail.karamanozsahin.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-10 23:43:44
Valid until
2027-01-08 23:43:43
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintab77cc51d639186abccd9e1415955747857158b094d409fa5099c4553e8e723d
Certificate names · 9 SANs
  • autoconfig.karamanozsahin.com
  • autodiscover.karamanozsahin.com
  • cpanel.karamanozsahin.com
  • cpcalendars.karamanozsahin.com
  • cpcontacts.karamanozsahin.com
  • mail.karamanozsahin.com
  • webdisk.karamanozsahin.com
  • webmail.karamanozsahin.com
  • www.karamanozsahin.com

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

Recorded subdomains9

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

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

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of karamanozsahin.com · checked Oct 30, 2026

80
Needs Work
Performance
FCP
1.81 s
First Contentful Paint
LCP
2.82 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
456 ms
Total Blocking Time
SI
4.82 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://karamanozsahin.com/
karamanozsahin.com - Berlin
karamanozsahin.com
Response
HTTP 200
HTML body
281.3 KB
Compressed
35.0 KB
Links
165 internal · 2 external
Selected response headers
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: karamanozsahin.com - Berlin
Open Graph description: karamanozsahin.com
Saved response-header values · 9
Accept-Ranges
bytes
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
36947
Content-Type
text/html
Date
Fri, 30 Oct 2026 01:08:27 GMT
Keep-Alive
timeout=5, max=100
Last-Modified
Mon, 24 Aug 2026 14:06:57 GMT
Vary
Accept-Encoding

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

Registration & observation details1

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 56 SHA-256 hashes: 55 URLScan scan:

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

Open this scan on URLScan 01a18a57-71e5-739c-9013-0d8f840fcdfb ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-30 02:07:33.000000
    Evidence SHA-256
    2e80675356023a2936218006ba8dcca5fadfb5881f03fe0fbbdc315c82b73467
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 02:07:33
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 02:07:33.000000
    Evidence SHA-256
    2e80675356023a2936218006ba8dcca5fadfb5881f03fe0fbbdc315c82b73467
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 02:07:33
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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
    karamanozsahin.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Automated brand label: Celer · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 90
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 5. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: Celer
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

5 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Added to PhishDestroy

    karamanozsahin.com

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    17/92 engine detections

    View source
  5. Wayback Machine

    Page archived

    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.

Check for cloaking

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

karamanozsahin.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

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

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

Official reporting routes

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.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

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

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

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including karamanozsahin.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

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.

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