Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
play-googles.app favicon

play-googles.app

In short

play-googles.app is a Google impersonation page detected by PhishDestroy on 2026-10-25.

“Ant Design Pro”

Review the evidence
Registrar
Name.com
Resolved IP
72.61.127.116
Registered
Oct 22, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored blocklist matches: 2 Automated brand label: Google Scam type: Impersonation Young domain: 3 days old
VirusTotal
0 / 92
engine detections ·
OTX
4
community references
Cloudflare Radar
suspicious
source verdict
Page captures
4
open gallery
Domain age
3 days
Reports sent
1
view timeline
OTX: 4 refs Oct 25, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

play-googles.app is a Google impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (90/100). Registrar: Name.com. Status: Last known active. Hosting: Sprint Communications. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
VirusTotal
0 / 92
OTX
4 community refs
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added play-googles.app to its blocklist on 2026-10-25 after an admin report noted the domain was three days old. The intake AI assessment on the same day recorded an “unknown” verdict because the page content was insufficient for analysis. The recorded page title was “Ant Design Pro” and the HTTP response returned a 302 redirect to /user/login/.

How the scam works

No specific malicious behavior was observed on this page, so the listing does not confirm a particular technique. Newly registered domains are often used to harvest credentials or serve as placeholders for future attacks, but the risk here is limited to the domain’s suspicious status.

Evidence

VirusTotal scanned the domain on 2026-10-25 and reported 0 detections out of 92 engines. Google Safe Browsing checked the same day and did not flag the site. urlscan.io captured the page on 2026-10-25; its machine‑learning engine gave a malicious score of 98, while the overall verdict was non‑malicious. OTX listed four pulses referencing the domain as of 2026-10-25. External blocklists MetaMask and SEAL also contained the domain, and PhishDestroy’s internal list marks it as blocked.

Infrastructure

The domain was registered on 2026-10-22 through Name.com, Inc. The recorded IP address was 72.61.127.116, which belongs to Sprint Communications in Malaysia. TLS was provided by Let’s Encrypt, issued on 2026-10-22 and valid until 2027-01-20. DNS records at the time of observation included an A record to that IP and a CNAME to dns.chuhai7.com; DNSSEC signatures were not present. Open ports observed were 22, 80 and 443.

What to do

Visitors should avoid entering any credentials on the site; if credentials were submitted, change the associated passwords immediately. No wallet‑related actions are required because no wallet interaction was observed. Defenders should block or closely monitor traffic to play-googles.app and review access logs for any activity targeting this exact domain.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotURLQuery screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 0 / 92 · OTX 4 references 9 sources

Cloudflare Radar

Suspicious

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

d2a0e00b-b033-42f3-a344-468d90ccf25e

Final URL

https://play-googles.app/user/login/

HTTP response

200

Redirect type

same-domain

Navigation history

  • URL
    https://play-googles.app/
    Status
    302
  • URL
    https://play-googles.app/user/login/
    Status
    200

DOM structure hash

179d0d71d8f80b4743d8e6266fdcd2747316a8a9e458bdf665a7c93395eaad3c

Document hash

4d162d130301ae345eb853a42502288d680031d97c1934c9fda38704dc1ae954

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    play-googles.app
    Type
    CNAME
    Value
    dns.chuhai7.com
  • Name
    play-googles.app
    Type
    CNAME
    Value
    dns.chuhai7.com

DNSSEC valid

No

IP address

72.61.127.116

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Nameservers
  • ns1cnb.name.com
  • ns2btz.name.com
  • ns3cna.name.com
  • ns4bfy.name.com
Original source fields · JSON
Uuid
d2a0e00b-b033-42f3-a344-468d90ccf25e
Final url
https://play-googles.app/user/login/
Status
200
Redirected
same-domain
History
[
    {
        "url": "https://play-googles.app/",
        "status": 302
    },
    {
        "url": "https://play-googles.app/user/login/",
        "status": 200
    }
]
DOM structure hash
179d0d71d8f80b4743d8e6266fdcd2747316a8a9e458bdf665a7c93395eaad3c
Document hash
4d162d130301ae345eb853a42502288d680031d97c1934c9fda38704dc1ae954
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "play-googles.app",
        "type": "CNAME",
        "value": "dns.chuhai7.com"
    },
    {
        "name": "play-googles.app",
        "type": "CNAME",
        "value": "dns.chuhai7.com"
    }
]
Dnssec valid
false
Ip
72.61.127.116
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-10-22T10:04:29Z",
    "updated": "2026-10-22T10:04:30Z",
    "expires": "2027-10-22T10:04:29Z",
    "nameservers": [
        "ns1cnb.name.com",
        "ns2btz.name.com",
        "ns3cna.name.com",
        "ns4bfy.name.com"
    ]
}

URLScan

Malicious · engine verdict · score 98

Open report
URLScanOriginal source recordObserved: 25 fields

Observed: · Retrieved:

Report ID

01a173ed-57b7-72df-8b0e-49fe3d1b5d15

Final URL

https://play-googles.app/user/login/

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://play-googles.app/
    From
    http://play-googles.app/
    Status
    307
  • To
    https://play-googles.app/user/login/
    From
    https://play-googles.app/
    Status
    302

IP address

72.61.127.116

Reverse DNS (PTR)

srv1154009.hstgr.cloud

Contacted domains

  • fonts.gstatic.com
  • accounts.google.com
  • images.chuhai7.com
  • fonts.googleapis.com
  • cdnjs.cloudflare.com
  • mdn.alipayobjects.com

Contacted IP addresses

  • 142.251.14.94
  • 142.251.127.84
  • 142.251.14.95
  • 104.17.24.14
  • 163.181.254.193
  • 172.67.71.60
  • 72.61.127.116

Autonomous systems (ASN)

  • 15169
  • 13335
  • 24429
  • 47583

Server countries

  • US
  • MY

Linked domains

  • chuhai7.com

Document hash

4d162d130301ae345eb853a42502288d680031d97c1934c9fda38704dc1ae954

Script hashes

  • 4ed563bb671d7583af6c5ce672bef5cafc572b21e9f2edb8b314de4360165dc1
  • a4e33a994b819d803519ff71c6e947d7f9708ee000c2f8982023f7740ae4358d
  • 66f048eb30872e53c44a864c4b580049ddf5c59ee19bed3cff06be7f04954ffb
  • 53938e9079bd62d96c03495468973b37bb04a0985ba4949ee3fc5f275adc6ba3
  • 80849a819ee2cec79bd5a727918e5fc5c13f1456e20c5c9cbe288fc2da7042d4
  • 4f568ff52ae86f55d123516a98bb3e733b36acaa280ac1fd80e96d771a07119f
  • 0f523dda780f49a6833ed71778299be9dcfc20f6936fd8e21439d217ccf0f836
  • 2e6b66bf3d6ce3d4e62234037f5417bd721d4b0e49e21fd47d1377ba9caed5de
  • 91bcb0576b259d88aecb4f012fd9ac81fd6df790df7eb99cb07692e9ce7c01e6

JavaScript globals

  • makoChunk_ant-design-pro
  • __mako_require_module__
  • __mako_chunk_load__
  • clearImmediate
  • setImmediate
  • regeneratorRuntime
  • __ANTD_STYLE_CACHE_MANAGER_FOR_SSR__
  • g_umi
  • jsonpCallback
  • INITIAL_STATE
  • default_gsi
  • _F_toggles_default_gsi
  • google
  • __G_ID_CLIENT__
  • closure_lm_474656
  • paper

Cookies

  • g_state

Browser storage keys

  • __sak

TLS session and certificate

Subject alternative names
  • play-googles.app
Cipher
AES_256_GCM
Issuer
YR2
Subject
play-googles.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

3

Certificate validity, days

89

Page requests

35

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a173ed-57b7-72df-8b0e-49fe3d1b5d15
Final url
https://play-googles.app/user/login/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://play-googles.app/",
        "from": "http://play-googles.app/",
        "status": 307
    },
    {
        "to": "https://play-googles.app/user/login/",
        "from": "https://play-googles.app/",
        "status": 302
    }
]
Ip
72.61.127.116
Ptr
srv1154009.hstgr.cloud
Contacted domains
[
    "fonts.gstatic.com",
    "accounts.google.com",
    "images.chuhai7.com",
    "fonts.googleapis.com",
    "cdnjs.cloudflare.com",
    "mdn.alipayobjects.com"
]
Contacted IP addresses
[
    "142.251.14.94",
    "142.251.127.84",
    "142.251.14.95",
    "104.17.24.14",
    "163.181.254.193",
    "172.67.71.60",
    "72.61.127.116"
]
Asns
[
    "15169",
    "13335",
    "24429",
    "47583"
]
Countries
[
    "US",
    "MY"
]
Linked domains
[
    "chuhai7.com"
]
Document hash
4d162d130301ae345eb853a42502288d680031d97c1934c9fda38704dc1ae954
Script hashes
[
    "4ed563bb671d7583af6c5ce672bef5cafc572b21e9f2edb8b314de4360165dc1",
    "a4e33a994b819d803519ff71c6e947d7f9708ee000c2f8982023f7740ae4358d",
    "66f048eb30872e53c44a864c4b580049ddf5c59ee19bed3cff06be7f04954ffb",
    "53938e9079bd62d96c03495468973b37bb04a0985ba4949ee3fc5f275adc6ba3",
    "80849a819ee2cec79bd5a727918e5fc5c13f1456e20c5c9cbe288fc2da7042d4",
    "4f568ff52ae86f55d123516a98bb3e733b36acaa280ac1fd80e96d771a07119f",
    "0f523dda780f49a6833ed71778299be9dcfc20f6936fd8e21439d217ccf0f836",
    "2e6b66bf3d6ce3d4e62234037f5417bd721d4b0e49e21fd47d1377ba9caed5de",
    "91bcb0576b259d88aecb4f012fd9ac81fd6df790df7eb99cb07692e9ce7c01e6"
]
Globals
[
    "makoChunk_ant-design-pro",
    "__mako_require_module__",
    "__mako_chunk_load__",
    "clearImmediate",
    "setImmediate",
    "regeneratorRuntime",
    "__ANTD_STYLE_CACHE_MANAGER_FOR_SSR__",
    "g_umi",
    "jsonpCallback",
    "INITIAL_STATE",
    "default_gsi",
    "_F_toggles_default_gsi",
    "google",
    "__G_ID_CLIENT__",
    "closure_lm_474656",
    "paper"
]
Cookies
[
    "g_state"
]
Storage keys
[
    "__sak"
]
Tls
{
    "san": [
        "play-googles.app"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "play-googles.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-20T09:10:31Z",
    "valid_from": "2026-10-22T09:10:32Z"
}
Domain age days
1
Apex age days
1
Tls age days
3
Tls valid days
89
Requests
35
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}
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
01a173ed-57b7-72df-8b0e-49fe3d1b5d15
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

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

First seen

DNS records

  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    hostmaster.nsone.net
    Value
    ns1.name.com
  • TTL, seconds
    300
    Type
    A
    Value
    72.61.127.116
  • TTL, seconds
    300
    Type
    CNAME
    Value
    dns.chuhai7.com

DNS records observed

JARM fingerprint

3fd3fd0003fd3fd21c42d42d000000bdfc58c9a46434368cf60aa440385763

Certificate

Subject alternative names
  • play-googles.app
Issuer
Let's Encrypt / YR2
Serial
5ba0fdf3b802a5a07fa25f02d3e3fc5aaee
SHA-256
ad1e4c7ada26b38bfb8513ebb593bab4dba5ef509b129ac04e2756a060c674fe
Subject
play-googles.app
Valid until
Valid from

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
Name.com, Inc
Registrar IANA ID
625
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
First seen
2026-10-22T10:16:53Z
DNS records
[
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "hostmaster.nsone.net",
        "value": "ns1.name.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "72.61.127.116"
    },
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "dns.chuhai7.com"
    }
]
Dns at
2026-10-25T16:57:13Z
Jarm
3fd3fd0003fd3fd21c42d42d000000bdfc58c9a46434368cf60aa440385763
Certificate
{
    "san": [
        "play-googles.app"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "5ba0fdf3b802a5a07fa25f02d3e3fc5aaee",
    "sha256": "ad1e4c7ada26b38bfb8513ebb593bab4dba5ef509b129ac04e2756a060c674fe",
    "subject": "play-googles.app",
    "valid_to": "2027-01-20T09:10:31Z",
    "valid_from": "2026-10-22T09:10:32Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-22T10:04:29Z",
        "last changed": "2026-10-22T10:04:30Z",
        "registration": "2026-10-22T10:04:29Z",
        "registrar expiration": "2027-10-22T10:04:29Z",
        "last update of RDAP database": "2026-10-22T10:04:30Z"
    },
    "registrar": "Name.com, Inc",
    "registrar_iana_id": "625"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-25 16:51:54 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-25T16:51:54Z
fetched_at
2026-10-25T17:13:44Z
stats
{"timeout":0,"harmless":55,"malicious":0,"suspicious":0,"undetected":37}

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

90 / 100 · heuristic score · 1 brand references · 1 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-25T17:20:20Z

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
10
analyzed_at
2026-10-25T17:20:20Z
source_timestamp
2026-10-25 18:20:20
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
play-googles.app — Suspicious Domain
ai_description
PhishDestroy lists play-googles.app as suspicious; the site presents an Ant Design Pro login page and received mixed scanner verdicts.
ai_generated_at
2026-10-25T17:17:20Z
ai_generated_by
threat-v3-mistral
interpretation
Narrative generation metadata, separate from provider 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: 19 fields

Mail configuration

SPF lookups
0

CAA records

Domain
play-googles.app

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Sitemap

Present
Yes
URL count
33

Page title and metadata

Page title
Ant Design Pro

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
60
TLS
168
Waiting
168
Connection
167
Download
0
Response time, ms
563

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
1560
CO₂, grams
0.0001
Cleaner than, %
95

Location

IP address
72.61.127.116
ASN
47583
Organization
Sprint Communications
City
Kuala Lumpur
Country
MY

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
play-googles.app

DNS records

A
  • 72.61.127.116
CNAME
  • dns.chuhai7.com

DNSSEC

DS record
No
RRSIG
No
DNSKEY
Yes

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

IP lookup

IP address
72.61.127.116
IP version
4

Redirects

Redirect chain
  • https://play-googles.app
  • /user/login/
Count
1

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "play-googles.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Sitemap
{
    "present": true,
    "url_count": 33
}
Page title and metadata
{
    "title": "Ant Design Pro"
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 302,
    "timings": {
        "dns": 60,
        "tls": 168,
        "wait": 168,
        "connect": 167,
        "download": 0
    },
    "response_ms": 563
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 1560,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Location
{
    "ip": "72.61.127.116",
    "asn": "47583",
    "org": "Sprint Communications",
    "city": "Kuala Lumpur",
    "country": "MY"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "play-googles.app"
}
DNS records
{
    "A": [
        "72.61.127.116"
    ],
    "CNAME": [
        "dns.chuhai7.com"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": true
}
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
}
Get ip
{
    "ip": "72.61.127.116",
    "family": 4
}
Redirects
{
    "chain": [
        "https://play-googles.app",
        "/user/login/"
    ],
    "count": 1
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about play-googles.app

Is play-googles.app legit?

No. PhishDestroy classifies play-googles.app as a Google impersonation page (risk: critical, 90/100); it was first detected on 2026-10-25. Treat the site as unsafe.

Is play-googles.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on play-googles.app. 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 play-googles.app?

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 · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
Observed page title
Ant Design Pro
Automated brand references
Google
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 86 days

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Name.com SE(SE)
Abuse contactabuse@hostinger.com, abuse@name.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for play-googles.app →
RegistrationCreated Oct 22, 2026 (3d · Brand New!) — Expires Oct 22, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 90/1001 brand signal
Submitted URLhttp://play-googles.app/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
72.61.127.116
Network ASN
AS47583
Organization
Sprint Communications
Observed location
Kuala Lumpur, MY
Server header
nginx

Nameservers 4

  • ns1cnb.name.com
  • ns2btz.name.com
  • ns3cna.name.com
  • ns4bfy.name.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-22 09:10:32
Valid until
2027-01-20 09:10:31
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-25 17:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintad1e4c7ada26b38bfb8513ebb593bab4dba5ef509b129ac04e2756a060c674fe
Certificate names · 1 SAN
  • play-googles.app

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

viewdns.info · 72.61.127.116rapiddns.io
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of play-googles.app · checked Oct 25, 2026

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

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

Archived HTTP response HTTP 200
Requested URL: http://play-googles.app/
Final URL: http://play-googles.app/user/login/
Ant Design Pro
Response
HTTP 200
HTML body
1.5 KB
Compressed
805 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 14
Access-Control-Allow-Credentials
true
Access-Control-Allow-Headers
Origin, Content-Type, Authorization, Accept, X-System-Verification
Access-Control-Allow-Methods
GET, POST, PUT, PATCH, DELETE, OPTIONS
Access-Control-Allow-Origin
*
Access-Control-Max-Age
86400
Cache-Control
no-cache
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 16:40:13 GMT
Last-Modified
Sun, 25 Oct 2026 12:32:59 GMT
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    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-10-25 17:39:39.000000
    Evidence SHA-256
    041657246ea3217d868bcea5c088d0591f8420528b19b9fcb65a590c16db1e17
    Evidence timestamp as recorded
    2026-10-25 17:39:39
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    false
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    legacy_alive_unverified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    15
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 17:39:39.000000
    Evidence SHA-256
    8a8a51c13b36ac3668fccedd3c947ab442f53f82f1a105f1425bee86f91b5996
    Evidence timestamp as recorded
    2026-10-25 17:39:39

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. Abuse report sent

    PD-20261025-5EAB3D

    abuse@name.com
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    play-googles.app

    View source
  6. URLScan

    Page captured

    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.

play-googles.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-5EAB3D Recipient: abuse@name.com
PDF notice generated
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?

5 evidence signal groups linked 1 stored notification records 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.

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

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 →.

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.

  • 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 play-googles.app)
  • 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/play-googles.app"
  title="PhishDestroy threat report for play-googles.app"
  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>