Skip to security report
Analytics Dashboard
Domain security and threat intelligence
otodom.1843verify.my.id favicon

otodom.1843verify.my.id

In short

otodom.1843verify.my.id is a Google impersonation page detected by PhishDestroy on 2026-10-11. Risk: critical (100/100). Status: Last known active. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. VirusTotal: 18/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“CRM”

Resolved IP
188.114.96.3
Registered
Jul 12, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 18/92 Spamhaus DBL: DBL_PHISH Automated brand label: Google
Oct 11, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
18 / 92
engine detections
Google Safe Browsing
No threat flag
Page captures
5
open gallery
Domain age
102 days
Source evidenceVirusTotal 18 / 92 6 sources

VirusTotal

18 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Malware Security threats
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
18 / 92
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

otodom.1843verify.my.id is an impersonation phishing page that puts the Otodom property-listings brand in front of a "verify" hostname to look like an official confirmation step. It targets people buying, selling or renting through classified ads, who may be sent the link during a conversation about a listing. PhishDestroy first flagged it on 2026-10-11. It was still online and serving content on 2026-10-19.

How the scam works

Schemes built on a listings brand usually start in chat. A fake buyer or landlord sends a link that claims a payment, deposit or account needs "verification" through the platform. The page then asks for card details, banking logins or one-time codes, and those are used to drain the victim's account rather than deliver money to it. The browser tab reads "CRM" instead of anything Otodom-branded, while we classify the site as Otodom impersonation.

Evidence

On 2026-10-12, 18 of 92 VirusTotal engines marked the hostname as malicious. They included BitDefender, ESET, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar, DNS8 and Chong Lua Dao, the Vietnamese anti-phishing project. Spamhaus lists the domain in its DBL with a phishing code, so mail filters and resolvers that use that list can block it. The site is also on the PhishDestroy blocklist.

Infrastructure

The registration date is 2013-09-09, roughly thirteen years before we detected the site. The "verify" label is a subdomain sitting under that older name. Traffic passes through Cloudflare (AS13335, US), which hides the real origin server behind a shared proxy address. The HTTPS certificate comes from Google Trust Services (WE1), an automated issuer, so the padlock says nothing about who runs the page.

What to do

If you entered card numbers or banking credentials, call your bank right away to block the card and dispute any charges. Change your online-banking password, and never share SMS or app confirmation codes with anyone. If you reached the page through a chat about a listing, stop contacting that person, report the conversation to the platform, and keep the messages as evidence. Defenders should block the hostname and the 1843verify.my.id parent, and warn staff and customers about verification links shared in listing chats.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-11T11:18:19Z

Observed: · Retrieved:

Uuid
01a12aaf-4ef2-74cb-94c4-6ac3e2a77471
Final url
https://otodom.1843verify.my.id/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://otodom.1843verify.my.id/",
        "from": "http://otodom.1843verify.my.id/",
        "status": 307
    }
]
Ip
188.114.97.3
Contacted IP addresses
[
    "188.114.97.3"
]
Asns
[
    "13335"
]
Document hash
503e31b76641627761649126f8ad120906b8262e64aba5bb76709d8f68bc3eb5
Tls
{
    "san": [
        "1843verify.my.id",
        "*.1843verify.my.id"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "1843verify.my.id",
    "protocol": "QUIC",
    "valid_to": "2026-12-01T16:33:46Z",
    "valid_from": "2026-09-02T15:34:59Z"
}
Domain age days
65
Apex age days
90
Tls age days
38
Tls valid days
90
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 77,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "Express"
}
Cloudflare Radar · 2026-10-12T10:16:38Z

Observed: · Retrieved:

Uuid
80b18a43-2d1b-4122-95d9-5410defb1aa1
Final url
https://otodom.1843verify.my.id/
Status
200
History
[
    {
        "url": "https://otodom.1843verify.my.id/",
        "status": 200
    }
]
DOM structure hash
d263297a60b00faba4a45aaab04d09197189e89c9cff57b593c9dcdaadff01e8
Document hash
a24a50d010645420ea2c3923b0305e70394020f70ddf7aa6eb6ef9a890a7e99d
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "otodom.1843verify.my.id",
        "type": "A",
        "value": "172.67.194.120"
    },
    {
        "name": "otodom.1843verify.my.id",
        "type": "A",
        "value": "104.21.20.212"
    },
    {
        "name": "otodom.1843verify.my.id",
        "type": "AAAA",
        "value": "2606:4700:3033::6815:14d4"
    },
    {
        "name": "otodom.1843verify.my.id",
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:c278"
    }
]
Dnssec valid
false
Ip
172.67.194.120
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "PT Jagoan Hosting Indonesia",
    "nameservers": [
        "brett.ns.cloudflare.com",
        "priscilla.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-18T13:41:31Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 16,
    "suspicious": 2,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "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": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-08-06T11:07:36Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:c278"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.20.212"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.194.120"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::6815:14d4"
    }
]
Dns at
2026-10-18T13:46:47Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "1843verify.my.id",
        "*.1843verify.my.id"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "8fbb6340dbfb3cba0e8288da846e8c05",
    "sha256": "8269baa9c5854f61fae6b828bb2d282e94fa975c4b6f99b15c016b60f971d743",
    "subject": "1843verify.my.id",
    "valid_to": "2026-12-01T16:33:46Z",
    "valid_from": "2026-09-02T15:34:59Z"
}

Questions about otodom.1843verify.my.id

Is otodom.1843verify.my.id legit?

No. PhishDestroy classifies otodom.1843verify.my.id as a Google impersonation page (risk: critical, 100/100); it was first detected on 2026-10-11. VirusTotal: 18/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is otodom.1843verify.my.id safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on otodom.1843verify.my.id. 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 otodom.1843verify.my.id?

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 1
PhishDestroy PhishDestroy list View source

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-10-11 11:20 UTC
StateStored capture
Position1 / 5
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registration (base domain)1843verify.my.id · Created Jul 12, 2026 (102d)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 11, 2026score 88/100
Submitted URLhttp://otodom.1843verify.my.id/
Favicon Hash
Observed page title
CRM
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 39 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-02 15:34:59
Valid until
2026-12-01 16:33:46
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 13:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8269baa9c5854f61fae6b828bb2d282e94fa975c4b6f99b15c016b60f971d743
Certificate names · 1 SAN
  • 1843verify.my.id

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.96.3rapiddns.io

Latest Classified Outcome 2026-10-22 10:38:20 UTC

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: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 10:38:20 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:38:20 UTC last content: 2026-10-22 10:38:20 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.
Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

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

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
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 history10

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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 5
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    18/92 engine detections

    View source
  3. Added to PhishDestroy

    otodom.1843verify.my.id

    View source
  4. URLScan

    Page captured

    View source

Check for cloaking

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

otodom.1843verify.my.id

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 18 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious 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 Archived
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 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

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

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 otodom.1843verify.my.id)
  • 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

Live Threat Feed Appeal This Listing
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.1843verify.my.id"
  title="PhishDestroy threat report for otodom.1843verify.my.id"
  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>