Skip to security report
Domain security and threat intelligence
ispsync.id favicon

ispsync.id

In short

ispsync.id is a Celer impersonation page detected by PhishDestroy on 2026-10-04. Risk: critical (100/100). Registrar: PT Cloud Hosting Indon…. Status: Last known active. Hosting: IDNIC-GOGIGA-AS-ID - PT Gogiga Media Teknologi, ID. PhishDestroy sent 1 abuse report. VirusTotal: 9/91 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“ISPSYNC — Enterprise Telecom & ISP Operations Platform”

Registrar
PT Cloud Hosting Indon…
Resolved IP
103.179.65.73
Registered
Sep 29, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 9/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Celer Young domain: 23 days old
OTX: 4 refs Oct 4, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 9. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is care@idcloudhost.co.id. The latest stored availability evidence still shows the domain reachable; 18 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
18 days
Reports sent
1
Latest case ID
PD-20261004-F36017
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 9 / 91 · OTX 4 references 7 sources

VirusTotal

9 / 91 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 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
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer: Let's Encrypt / YE2

Analysis

Critical
VirusTotal
9 / 91
OTX
4 community refs
Page captures
5

PhishDestroy threat report

Overview

ispsync.id presents itself as "ISPSYNC — Enterprise Telecom & ISP Operations Platform," but PhishDestroy classifies it as an impersonation phishing page. The page title describes a telecom management service, while our classification, backed by the MetaMask and SEAL blocklists, puts it in the phishing category. PhishDestroy first flagged the domain on 2026-10-04. As of 2026-10-19 the site was still online and serving live content.

How the scam works

Impersonation pages borrow the look and language of a legitimate-sounding business so that visitors trust the login, sign-up or connect prompts placed in front of them. Here the cover is an enterprise ISP operations dashboard, the kind of portal staff and partners log into without a second thought. Whatever a visitor submits, whether account credentials, contact details or a wallet connection and signature, goes to the operators. Credentials can be reused to break into real accounts. Signed wallet requests can hand over tokens.

Evidence

Nine of 91 VirusTotal engines flagged the domain in a check on 2026-10-06. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a modest count, but it comes from several unrelated vendors within days of the domain going live. Spamhaus lists it in its DBL with a phishing tag. Wallet-focused blocklists from MetaMask and SEAL also carry it, and four AlienVault OTX pulses reference it.

Infrastructure

The domain was registered on 2026-09-29 through PT Cloud Hosting Indonesia, just five days before PhishDestroy detected it. That short gap is typical of pages built to be used quickly. It is hosted in Indonesia on the PT Gogiga Media Teknologi network, matching the local .id country domain and a domestic registrar. The free Let's Encrypt certificate means the padlock in the browser proves only an encrypted connection, not a legitimate operator.

What to do

If you entered a password on ispsync.id, change it right away wherever you used it, and turn on app-based two-factor authentication. Then review recent sign-ins for activity you don't recognize. If you connected a crypto wallet or signed anything, use a token approval checker to revoke permissions granted during that session, and move remaining funds to a fresh wallet if you approved unfamiliar requests. Report the incident to your IT or security team if work credentials were involved. Defenders should block the domain at DNS and proxy level, search mail and web logs for visits since 2026-09-29, and reset credentials for any user who reached the page.

Collected source details

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

URLScan · 2026-10-04T05:38:36Z

Observed: · Retrieved:

Uuid
01a1056b-a126-7287-89ac-197b62b901df
Final url
https://ispsync.id/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://ispsync.id/",
        "from": "http://ispsync.id/",
        "status": 307
    }
]
Ip
103.179.65.73
Contacted IP addresses
[
    "103.179.65.73"
]
Asns
[
    "149335"
]
Countries
[
    "ID"
]
Linked domains
[
    "wa.me"
]
Social
[
    "https://wa.me/6281100000000"
]
Document hash
9eee2250d4244cfbb5fa5c7dfd1c42efa11428000fa6f088d5a31679bc3d59fe
Script hashes
[
    "d9840d6de414f19d28fbe08cc2ddd0aeb95cf379864950a506592a54f4996f31",
    "a4590375a64190f57d18b357bf576bf111bd5f02f3c93cad0f65fdf176689f46",
    "f71552684e86daa3e94faad9002fb69d4e8d308a997ca88fdde74e54b5191870",
    "1331a3ca0ed7616592f7a027fd92ee712dca2872aaea63d596d1faf7edc940bb",
    "dcf86145eddaab6e8942e186feccee2341a2278b36035f8f844f3b5c9db2190b",
    "70ab9f3a9680f69d2a2620a375d45db7480fef67c9d1559ab630809dcd8d5ca3",
    "589887d2f854a5d9e515aa34353677620eecd63938a7ee8debfa055089d4f90c"
]
Globals
[
    "TURBOPACK",
    "__next_f",
    "next",
    "__webpack_hash__"
]
Tls
{
    "san": [
        "ispsync.id"
    ],
    "cipher": "CHACHA20_POLY1305",
    "issuer": "YE2",
    "subject": "ispsync.id",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-28T15:49:57Z",
    "valid_from": "2026-09-29T15:49:58Z"
}
Domain age days
4
Apex age days
4
Tls age days
4
Tls valid days
89
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 75,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "permissions-policy": "camera=(), microphone=(), geolocation=()"
}
VirusTotal · 2026-10-09T06:40:04Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 10,
    "suspicious": 2,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-09-29T18:14:46Z
DNS records
[
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.ispsync.id"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "hostmaster.ispsync.id",
        "value": "ns1.ispsync.id"
    },
    {
        "ttl": 60,
        "type": "AAAA",
        "value": "2001:df1:1cc0:65::73"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "103.179.65.73"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.ispsync.id"
    }
]
Dns at
2026-10-09T06:41:02Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "ispsync.id"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6347a160f53274356db67df26d68f493868",
    "sha256": "cb3ec1aec9a8a23007dca308f1e982276b7cabac72f908b57a831e3a92e9fbfb",
    "subject": "ispsync.id",
    "valid_to": "2026-12-28T15:49:57Z",
    "valid_from": "2026-09-29T15:49:58Z"
}

Questions about ispsync.id

Is ispsync.id legit?

No. PhishDestroy classifies ispsync.id as a Celer impersonation page (risk: critical, 100/100); it was first detected on 2026-10-04. VirusTotal: 9/91 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is ispsync.id safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on ispsync.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 ispsync.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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 5 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 5, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar PT Cloud Hosting Indon… (Unknown)
RegistrationCreated Sep 29, 2026 (23d · Very New!) — Expires Sep 29, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 4, 2026
DOM Analysisanalyzed Oct 9, 2026score 100/1007 brand signals
Submitted URLhttp://ispsync.id/
Favicon Hash
Case ID
Observed page title
ISPSYNC — Enterprise Telecom & ISP Operations Platform
Automated brand references
Celer Ledger Mastercard PayPal Stripe Visa WhatsApp
TLS Certificate
Issued by Let's Encrypt / YE2

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
103.179.65.73
Network ASN
AS149335
Organization
PT Gogiga Media Teknologi
Observed location
Payakumbuh, ID

Nameservers 2

  • ns1.ispsync.id
  • ns2.ispsync.id

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-29 15:49:58
Valid until
2026-12-28 15:49:57
Hostname coverage
Stored certificate expired or unverified
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:46 UTC
Collection source
PhishDestroy collector
Certificate fingerprintcb3ec1aec9a8a23007dca308f1e982276b7cabac72f908b57a831e3a92e9fbfb
Certificate names · 1 SAN
  • ispsync.id

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

Latest Classified Outcome 2026-10-22 10:37:26 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:37:26 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:37:26 UTC last content: 2026-10-22 10:37:26 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains19

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

  • api.ispsync.idDomain record
  • billing.ispku.ispsync.idDomain record
  • billing.ispsync.idDomain record
  • cms.dev.ispsync.idDomain record
  • cms.ispsync.idDomain record
  • cmsispmu.ispsync.idDomain record
  • dev.ispsync.idDomain record
  • dr-f614c49a6746396c0b269a16f8e3f8f7.ispsync.idDomain record
  • fibergrid.ispsync.idDomain record
  • fttx.dev.ispsync.idDomain record
  • hotspot.ispsync.idDomain record
  • ispku.ispsync.idDomain record
  • ledger.dev.ispsync.idDomain record
  • nexus.dev.ispsync.idDomain record
  • passpoint.dev.ispsync.idDomain record
  • portal.dev.ispsync.idDomain record
  • www.cmsispmu.ispsync.idDomain record
  • www.portal.dev.ispsync.idDomain record
  • www.www.cms.dev.ispsync.idDomain record

The original observation time is not recorded for these hostnames.

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 9 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ispsync.id · checked Oct 5, 2026

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

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history16

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

  1. Availability monitor · Recorded state

    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 11
  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

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    9/91 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20261004-F36017

    care@idcloudhost.co.id
  5. Added to PhishDestroy

    ispsync.id

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

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

ispsync.id

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261004-F36017 Recipient: care@idcloudhost.co.id
Page title stored with report: ISPSYNC — Enterprise Telecom & ISP Operations Platform
Blocklist hits included with submission: MetaMask, SEAL
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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.

Official reporting routes

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 ispsync.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

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.

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