VirusTotal
11 / 92 engine detections
Open reportlayanan11all.my.id is a TikTok impersonation page detected by PhishDestroy on 2026-10-10. Risk: critical (88/100). Registrar: PT Exabytes Network In…. Hosting: ANYM-NET PT Anym Network Indonesia, ID. PhishDestroy sent 1 abuse report. VirusTotal: 11/92 engines flag it. Do not enter credentials or connect a wallet.
“Index of /”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@anymhost.co.id.
The latest stored availability evidence still shows the domain reachable; 12 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.
11 / 92 engine detections
Open report2 det.
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
layanan11all.my.id is an impersonation phishing site on Indonesia's .my.id namespace. Its name is built on "layanan", Indonesian for "service", which points to Indonesian-speaking users looking for an official support or service page. PhishDestroy first flagged it on 2026-10-10. As of 2026-10-19 the server still responded, but the domain's DNS was inactive, so the page was no longer reachable by name.
Impersonation pages copy the look and wording of a trusted service, then ask visitors to log in, verify an account or submit personal details. Anything typed in, including usernames, passwords, phone numbers and one-time codes, goes straight to the operators, who use it to take over the real account. At the time of checking, the page title read "Index of /", a bare directory listing rather than a branded login screen, which differs from the impersonation classification.
Eleven of 92 VirusTotal engines flagged the domain on 2026-10-10, including BitDefender, Kaspersky, Fortinet, G-Data, alphaMountain.ai, CRDF, DNS8 and LevelBlue. Agreement among several unrelated vendors, both established antivirus labs and DNS-filtering services, carries more weight than one isolated hit. Among public blocklists, only PhishDestroy lists it so far.
The domain was registered on 2026-08-06 through PT Exabytes Network Indonesia, about two months before it was detected. It is hosted on ANYM-NET (PT Anym Network Indonesia) in Indonesia. The registrar, the hosting network and the .my.id extension are all Indonesian, which fits a campaign aimed at a local audience.
If you entered a password on this site, change it right away on the real service and on any other account that shares it, then turn on two-factor authentication. If you gave a one-time code, phone number or ID details, contact the genuine provider through its official app or number to secure the account, and watch for follow-up calls or messages pretending to be support. Defenders should block the domain and its hosting IP at DNS and proxy level, and check logs for users who visited after 2026-08-06.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a12620-bc41-7048-9880-8d682cd0c692 |
|---|---|
| Final url | https://layanan11all.my.id/login-tiktok/ |
| Status | 200 |
| Redirected | same-domain |
| Redirects | [
{
"to": "https://layanan11all.my.id/login-tiktok",
"from": "http://layanan11all.my.id/login-tiktok",
"status": 307
},
{
"to": "https://layanan11all.my.id/login-tiktok/",
"from": "https://layanan11all.my.id/login-tiktok",
"status": 301
}
] |
| Ip | 163.223.227.44 |
| Contacted domains | [
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"192.178.183.95",
"163.223.227.44"
] |
| Asns | [
"15169",
"199695"
] |
| Countries | [
"US",
"ID"
] |
| Document hash | 3a08b1bc286341949fb2720e17396e5d1d7af127358b71adb3c2618965221eb9 |
| Globals | [
"tutupPopup"
] |
| Tls | {
"san": [
"*.layanan11all.my.id",
"layanan11all.my.id"
],
"cipher": "AES_128_GCM",
"issuer": "YR2",
"subject": "*.layanan11all.my.id",
"protocol": "TLS 1.3",
"valid_to": "2027-01-04T10:57:35Z",
"valid_from": "2026-10-06T10:57:36Z"
} |
| Domain age days | 65 |
| Apex age days | 65 |
| Tls age days | 4 |
| Tls valid days | 89 |
| Requests | 8 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 97,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | 08b60904-ff6f-45f2-a676-ef57a04db430 |
|---|---|
| Final url | https://layanan11all.my.id/ |
| Status | 200 |
| History | [
{
"url": "https://layanan11all.my.id/",
"status": 200
}
] |
| DOM structure hash | 829e52fc7e075b4ae3a4c6f5ac8a0edd47a7b97a28f74af361c37195093e9aae |
| Document hash | 96edb14212ae16b05ee2549674becbd183ee4e5a86ccf503434df0a11ddba418 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "layanan11all.my.id",
"type": "A",
"value": "163.223.227.44"
}
] |
| Dnssec valid | false |
| Ip | 163.223.227.44 |
| Registration record | {
"registrar": "PT Exabytes Network Indonesia",
"nameservers": [
"dns1.anymhost.id",
"dns2.anymhost.id"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 16,
"suspicious": 1,
"undetected": 31
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"DNS8": "phishing",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"URLQuery": "suspicious",
"Kaspersky": "phishing",
"LevelBlue": "phishing",
"Gridinsoft": "phishing",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Categories | {
"alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
} |
| First seen | 2026-08-06T12:29:15Z |
| DNS records | [
{
"ttl": 14053,
"type": "TXT",
"value": "v=spf1 +a +mx +ip4:163.223.227.43 include:relay.mailbaby.net ~all"
},
{
"ttl": 15980,
"type": "NS",
"value": "dns3.anymhost.net"
},
{
"ttl": 14400,
"type": "A",
"value": "163.223.227.44"
},
{
"ttl": 15980,
"type": "NS",
"value": "dns2.anymhost.id"
},
{
"ttl": 21600,
"type": "SOA",
"rname": "support.anymhost.id",
"value": "dns1.anymhost.id"
},
{
"ttl": 14400,
"type": "MX",
"value": "layanan11all.my.id",
"priority": 0
},
{
"ttl": 15980,
"type": "NS",
"value": "dns1.anymhost.id"
},
{
"ttl": 15980,
"type": "NS",
"value": "dns4.anymhost.net"
}
] |
| Dns at | 2026-10-10T16:37:36Z |
| Jarm | 29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae |
| Certificate | {
"san": [
"*.layanan11all.my.id",
"layanan11all.my.id"
],
"issuer": "Let's Encrypt / YR2",
"serial": "6d1af072d91babf5b7c25ef584048a040f7",
"sha256": "03e21584b61e9a2d427c6c58a0f7681cc75340b1c629d9487c285fb131eeb9c9",
"subject": "*.layanan11all.my.id",
"valid_to": "2027-01-04T10:57:35Z",
"valid_from": "2026-10-06T10:57:36Z"
} |
No. PhishDestroy classifies layanan11all.my.id as a TikTok impersonation page (risk: critical, 88/100); it was first detected on 2026-10-10. VirusTotal: 11/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on layanan11all.my.id. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
dns1.anymhost.iddns2.anymhost.iddns3.anymhost.netdns4.anymhost.netlayanan11all.my.idpriority 0Location describes the IP network.
03e21584b61e9a2d427c6c58a0f7681cc75340b1c629d9487c285fb131eeb9c9*.layanan11all.my.idlayanan11all.my.idSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of layanan11all.my.id · checked Oct 10, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→live_content
content_served
Reachable
No threat flag
View sourcePD-20261010-2106CA
Page captured
View source11/92 engine detections
View sourcelayanan11all.my.id
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
layanan11all.my.id
PD-20261010-2106CA Recipient: abuse@anymhost.co.id If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
layanan11all.my.id)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.