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

otodom.kaishm.com

In short

PhishDestroy records that the otodom.kaishm.com capture returned a blank page, while its HTML title reads CRM.

“CRM”

Review the evidence
Registrar
SwedenName SRS AB
Resolved IP
United Kingdom188.114.97.1CloudFLARENET-EU · CDN
Registered
May 23, 2026
First observed
Nov 1, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Last known active Latest stored reachability observation
Risk signals
VirusTotal detections: 20/92 Spamhaus DBL: phishing domain
VirusTotal
20 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 21
Cloudflare Radar
Phishing
Page captures
3
open gallery
Domain age
162 days
registered 2026-05-23 according to WHOIS · source data differ
Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that the otodom.kaishm.com capture returned a blank page, while its HTML title reads CRM.

Critical
Status
Last known active
VirusTotal
20 / 92
Hosting
United Kingdom188.114.97.1CloudFLARENET-EU · CDN
Registrar
SwedenName SRS AB
Registered
May 23, 2026
Page captures
3
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for otodom.kaishm.com is blank: the screenshot shows an empty white area with no visible content, so no interaction could be observed. The HTML title reads "CRM", which conflicts with the empty capture and suggests a page that did not render its intended interface. Because the capture is blank, no logos, fields or controls can be confirmed from the screenshot, and the CRM title is metadata rather than visible page content.

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

Source evidenceVirusTotal 20 / 92 8 sources

VirusTotal

20 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
41
Malicious
17
Suspicious
3
Undetected
31

Vendor labels

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

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::6815:4234
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.156.251
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.66.52
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::ac43:9cfb

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.kaishm.com
  • kaishm.com
Issuer
Let's Encrypt / YE2
Serial
5a87d658073d23aa82510151939ecee87c1
SHA-256
21c51cd6f7eff31cd81d3b0de8203d352eeec0024bd876c82f55496a28521be7
Subject
kaishm.com
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 41,
    "malicious": 17,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "PREBYTES": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "SafeToOpen": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2026-05-23T00:00:00Z
Updated
2026-05-23T00:00:00Z
First seen
2026-08-06T16:42:15Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::6815:4234"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.156.251"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.66.52"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:9cfb"
    }
]
Dns at
2026-10-26T20:07:37Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.kaishm.com",
        "kaishm.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5a87d658073d23aa82510151939ecee87c1",
    "sha256": "21c51cd6f7eff31cd81d3b0de8203d352eeec0024bd876c82f55496a28521be7",
    "subject": "kaishm.com",
    "valid_to": "2026-12-17T12:09:17Z",
    "valid_from": "2026-09-18T12:09:18Z"
}
Separate source record · 17 malicious + 3 suspicious / 92 · 2026-10-26 20:02:20 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-26T20:02:20Z
fetched_at
2026-11-01T14:38:34Z
stats
{"timeout":0,"harmless":41,"malicious":17,"suspicious":3,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

0a168cad-4884-479b-8952-fb54c9340f46

Final URL

https://otodom.kaishm.com/

HTTP response

200

Navigation history

  • URL
    https://otodom.kaishm.com/
    Status
    200

DOM structure hash

d263297a60b00faba4a45aaab04d09197189e89c9cff57b593c9dcdaadff01e8

Document hash

1562816148191a48aac48f198c73dcbff298bb7427a566d655358a4a77e6366c

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    otodom.kaishm.com
    Type
    A
    Value
    104.21.66.52
  • Name
    otodom.kaishm.com
    Type
    A
    Value
    172.67.156.251
  • Name
    otodom.kaishm.com
    Type
    AAAA
    Value
    2606:4700:3035::6815:4234
  • Name
    otodom.kaishm.com
    Type
    AAAA
    Value
    2606:4700:3036::ac43:9cfb

DNSSEC valid

No

IP address

127.0.1.15

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Name SRS AB
Registered
Updated
Expires
Nameservers
  • amalia.ns.cloudflare.com
  • garrett.ns.cloudflare.com
Original source fields · JSON
Uuid
0a168cad-4884-479b-8952-fb54c9340f46
Final url
https://otodom.kaishm.com/
Status
200
History
[
    {
        "url": "https://otodom.kaishm.com/",
        "status": 200
    }
]
DOM structure hash
d263297a60b00faba4a45aaab04d09197189e89c9cff57b593c9dcdaadff01e8
Document hash
1562816148191a48aac48f198c73dcbff298bb7427a566d655358a4a77e6366c
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "otodom.kaishm.com",
        "type": "A",
        "value": "104.21.66.52"
    },
    {
        "name": "otodom.kaishm.com",
        "type": "A",
        "value": "172.67.156.251"
    },
    {
        "name": "otodom.kaishm.com",
        "type": "AAAA",
        "value": "2606:4700:3035::6815:4234"
    },
    {
        "name": "otodom.kaishm.com",
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:9cfb"
    }
]
Dnssec valid
false
Ip
127.0.1.15

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Name SRS AB",
    "created": "2026-05-23T12:54:03Z",
    "updated": "2026-07-22T13:04:20Z",
    "expires": "2027-05-23T12:54:03Z",
    "nameservers": [
        "amalia.ns.cloudflare.com",
        "garrett.ns.cloudflare.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 21

SHA-256 5ef5858d40f83457ac3991614023dac8196bd616d47f4b4d6229c9da70f99dab

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

019fdaf3-f59f-7408-bd24-d11fec731c13

Final URL

https://otodom.kaishm.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://otodom.kaishm.com/
    From
    http://otodom.kaishm.com/
    Status
    307
  • To
    http://otodom.kaishm.com/
    From
    https://otodom.kaishm.com/
    Status
    307
  • To
    https://otodom.kaishm.com/
    From
    http://otodom.kaishm.com/
    Status
    307

IP address

188.114.96.3

Contacted domains

  • static.cloudflareinsights.com

Contacted IP addresses

  • 104.16.80.73
  • 188.114.96.3

Autonomous systems (ASN)

  • 13335

Document hash

5ef5858d40f83457ac3991614023dac8196bd616d47f4b4d6229c9da70f99dab

JavaScript globals

  • __cfBeacon

TLS session and certificate

Subject alternative names
  • *.kaishm.com
  • kaishm.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
kaishm.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Differs from the registration date in WHOIS (2026-05-23), which gives 76 days on the scan date 2026-08-07. The two sources disagree; both values are kept as recorded.

Registered domain age, days

75

Certificate age, days

16

Certificate validity, days

89

Page requests

5

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
X-powered-by
Express
Original source fields · JSON
Uuid
019fdaf3-f59f-7408-bd24-d11fec731c13
Final url
https://otodom.kaishm.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://otodom.kaishm.com/",
        "from": "http://otodom.kaishm.com/",
        "status": 307
    },
    {
        "to": "http://otodom.kaishm.com/",
        "from": "https://otodom.kaishm.com/",
        "status": 307
    },
    {
        "to": "https://otodom.kaishm.com/",
        "from": "http://otodom.kaishm.com/",
        "status": 307
    }
]
Ip
188.114.96.3
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.80.73",
    "188.114.96.3"
]
Asns
[
    "13335"
]
Document hash
5ef5858d40f83457ac3991614023dac8196bd616d47f4b4d6229c9da70f99dab
Globals
[
    "__cfBeacon"
]
Tls
{
    "san": [
        "*.kaishm.com",
        "kaishm.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "kaishm.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-19T11:31:44Z",
    "valid_from": "2026-07-21T11:31:45Z"
}
Domain age days
0

Differs from the registration date in WHOIS (2026-05-23), which gives 76 days on the scan date 2026-08-07. The two sources disagree; both values are kept as recorded.

Apex age days
75
Tls age days
16
Tls valid days
89
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 21,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "Express"
}
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
019fdaf3-f59f-7408-bd24-d11fec731c13
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-11-01T14:54:26Z

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-11-01T14:54:26Z
source_timestamp
2026-11-01 15:54:26
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
otodom.kaishm.com blank CRM page capture
ai_description
PhishDestroy records that the otodom.kaishm.com capture returned a blank page, while its HTML title reads CRM.
ai_summary
The captured page for otodom.kaishm.com is blank: the screenshot shows an empty white area with no visible content, so no interaction could be observed. The HTML title reads "CRM", which conflicts with the empty capture and suggests a page that did not render its intended interface. Because the capture is blank, no logos, fields or controls can be confirmed from the screenshot, and the CRM title is metadata rather than visible page content. The stored VirusTotal domain result reports 20 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 15:43:06
revision
6bd0e50b35b7764597ce3dafbb84c58d3ee78892fd1bdf259098b4eb299b126c
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: 21 fields

CAA records

Domain
otodom.kaishm.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
CRM

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
6
TLS
43
Waiting
49
Connection
7
Download
0
Response time, ms
105

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
424
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    108.162.195.195
    Host
    garrett.ns.cloudflare.com
  • IP address
    172.64.34.94
    Host
    amalia.ns.cloudflare.com
DNS zone
kaishm.com

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
kaishm.com

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
AAAA
  • 2a06:98c1:3120::3
  • 2a06:98c1:3121::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://otodom.kaishm.com

Registration record

Registrar
Name SRS AB
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • amalia.ns.cloudflare.com
  • garrett.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
X-powered-by
Express
Original source fields · JSON
Caa records
{
    "domain": "otodom.kaishm.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "CRM"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 6,
        "tls": 43,
        "wait": 49,
        "connect": 7,
        "download": 0
    },
    "response_ms": 105
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 424,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.195",
            "host": "garrett.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.94",
            "host": "amalia.ns.cloudflare.com"
        }
    ],
    "zone": "kaishm.com"
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "kaishm.com"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "AAAA": [
        "2a06:98c1:3120::3",
        "2a06:98c1:3121::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://otodom.kaishm.com"
    ]
}
Registration record
{
    "registrar": "Name SRS AB",
    "created": "2026-05-23T12:54:03Z",
    "updated": "2026-07-22T13:04:20Z",
    "expires": "2027-05-23T12:54:03Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "amalia.ns.cloudflare.com",
        "garrett.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "x-powered-by": "Express"
    }
}

Questions about otodom.kaishm.com

Is otodom.kaishm.com legit?

PhishDestroy records that the otodom.kaishm.com capture returned a blank page, while its HTML title reads CRM.

Is otodom.kaishm.com safe to connect a wallet?

This report does not record which wallet requests otodom.kaishm.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 otodom.kaishm.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

Checked, no match

Last checked

Stored Capture · 3 captures

Cloudflare Radar 1 / 3 Used in the analysis Source file SHA-256: e474a175f992442a69e502e42d7748076f7b37bd4715cf7c03ed2b7ff55231c3 SHA-256 of the prepared copy given to the model: cbd7964afd4f4fe91d257f62cb637efc6d375d5ecf52307768f6bc30d044a66e
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://otodom.kaishm.com/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)

Domain details

Domain
IP Context United Kingdom188.114.97.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Name SRS AB SE(SE)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for kaishm.com →
Registration (base domain)kaishm.com · Created May 23, 2026 (162d) — Expires May 23, 2027
WHOIS statusok
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://otodom.kaishm.com/
Observed page title
CRM
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.97.1
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • amalia.ns.cloudflare.com
  • garrett.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-18 12:09:18
Valid until
2026-12-17 12:09:17
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint21c51cd6f7eff31cd81d3b0de8203d352eeec0024bd876c82f55496a28521be7
Certificate names · 2 SANs
  • *.kaishm.com
  • kaishm.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 · 188.114.97.1rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

20 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
PREBYTES
SafeToOpen
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
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://otodom.kaishm.com/
CRM
Response
HTTP 200
HTML body
424 B
Compressed
283 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
X-Powered-By: Express
Cache-Control: no-cache, no-store, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Cache-Control
no-cache, no-store, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a53ba91ebb69aed4-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 01 Nov 2026 14:41:29 GMT
Last-Modified
Fri, 30 Oct 2026 23:07:54 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2B2VJom%2BGEkhsdP0T%2BUgsEs3fvKNOEnEMGVX44Hd0AkVtyt6SY6D0W6P31fAyFbDSdIj6Fz%2BblIY%2Ba2ytxv0IGhDu0SvfFN74fT%2FTOw3KgGug8Z6ym%2FBLVcmlfQcTic4%2
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding
X-Powered-By
Express

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

Archived

Captured network requests

Network requests: 5 SHA-256 hashes: 3 URLScan scan:

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

Open this scan on URLScan 019fdaf3-f59f-7408-bd24-d11fec731c13 ↗

All retained availability observations1

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-11-01 15:38:43.736095
    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
    otodom.kaishm.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 21
  • 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: 20/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Wayback Machine

    Page archived

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Added to PhishDestroy

    otodom.kaishm.com

    View source
  4. VirusTotal

    20/92 engine detections

    View source
  5. URLScan

    Malicious · engine verdict · score 21

    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.

otodom.kaishm.com

Evidence & External Reports

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

Were You Affected by This Site?

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

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

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

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