Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-26T15:09:21Z. Retrieved (as stored): 2026-10-26T19:53:16Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
g0gle.hh-meet.com favicon

g0gle.hh-meet.com

In short

PhishDestroy first recorded g0gle.hh-meet.com on 2026-10-26. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-26T15:09:21Z. Retrieved (as stored): 2026-10-26T19:53:16Z.

“Zoom Client Update”

Review the evidence
Registrar
United StatesOwnRegistrar
Resolved IP
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registered
Jun 8, 2026
First observed
Oct 26, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 3/92
VirusTotal
3 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 60
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
147 days
registered 2026-06-08 according to WHOIS · source data differ
Reports sent
1
view timeline
Oct 26, 2026 1 Report Sent CDN
X Telegram API
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 abuse@ownregistrar.com. The latest stored availability evidence still shows the domain reachable; 7 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
7 days
Reports sent
1
Latest case ID
PD-20261026-702AC3
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded g0gle.hh-meet.com on 2026-10-26. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-26T15:09:21Z. Retrieved (as stored): 2026-10-26T19:53:16Z. Risk: critical (100/100). Registrar: OwnRegistrar. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
3 / 92
Scam type (automated label)
Impersonation
Hosting
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registrar
United StatesOwnRegistrar
Registered
Jun 8, 2026
Page captures
8
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for g0gle.hh-meet.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 3 / 92 8 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
3
Suspicious
0
Undetected
35

Vendor labels

CRDF
malicious
SOCRadar
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

OwnRegistrar, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::ac43:89ea
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.62.180
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.137.234
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::6815:3eb4

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • hh-meet.com
  • *.hh-meet.com
Issuer
Google Trust Services / WE1
Serial
b87edec8423461c11313d3d28da5bffd
SHA-256
81ec61b1d0f0157492fab94de8d0c256eeb54603de31a67e005831b19378e283
Subject
hh-meet.com
Valid until
Valid from

Registration record

Registrar
OwnRegistrar, Inc.
Registrar IANA ID
1250
Registrar URL
http://www.ownregistrar.com
Registered
Updated
Expires
Status
  • ok
Nameservers
  • kareem.ns.cloudflare.com
  • lila.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
OwnRegistrar, Inc.
Created
2026-06-08T14:04:32Z
Expires
2027-06-08T14:04:32Z
Updated
2026-06-08T14:04:32Z
First seen
2026-10-14T19:13:54Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:89ea"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.62.180"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.137.234"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::6815:3eb4"
    }
]
Dns at
2026-10-26T15:09:47Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "hh-meet.com",
        "*.hh-meet.com"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "b87edec8423461c11313d3d28da5bffd",
    "sha256": "81ec61b1d0f0157492fab94de8d0c256eeb54603de31a67e005831b19378e283",
    "subject": "hh-meet.com",
    "valid_to": "2027-01-02T19:06:59Z",
    "valid_from": "2026-10-04T18:07:10Z"
}
Registration record
{
    "registrar": "OwnRegistrar, Inc.",
    "registrar_iana_id": "1250",
    "registrar_url": "http://www.ownregistrar.com",
    "created": "2026-06-08T14:04:32Z",
    "updated": "2026-06-08T14:04:32Z",
    "expires": "2027-06-08T14:04:32Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "kareem.ns.cloudflare.com",
        "lila.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
20
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","ESET","Emsisoft","Forcepoint ThreatSeeker","Fortinet","G-Data","Kaspersky","LevelBlue","Lionic","MalwareURL","Netcraft","PrecisionSec","Seclookup","SOCRadar","Sophos","URLQuery","VIPRE","Webroot"]
observed_at
null
checked_at
2026-10-30 04:02:28
fetched_at
2026-10-30 03:02:28
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

6e790173-2720-4b30-986a-6c393a93bb6d

Final URL

https://g0gle.hh-meet.com/Windows/invite.php

HTTP response

200

Navigation history

  • URL
    https://g0gle.hh-meet.com/
    Status
    200
  • URL
    https://g0gle.hh-meet.com/Windows/
    Status
    302
  • URL
    https://g0gle.hh-meet.com/Windows/invite.php
    Status
    200

DOM structure hash

b0a19403907f52ab07d5a87f2bc1fdefefb567ff23422e17661c02603f227eeb

Document hash

7fd3d2956d216c23e560f747d2ea30fb469986fac634ddc483e38bcca49bdd95

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    g0gle.hh-meet.com
    Type
    A
    Value
    104.21.62.180
  • Name
    g0gle.hh-meet.com
    Type
    A
    Value
    172.67.137.234
  • Name
    g0gle.hh-meet.com
    Type
    AAAA
    Value
    2606:4700:3033::6815:3eb4
  • Name
    g0gle.hh-meet.com
    Type
    AAAA
    Value
    2606:4700:3031::ac43:89ea

DNSSEC valid

No

IP address

104.21.62.180

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
OwnRegistrar, Inc.
Registered
Updated
Expires
Nameservers
  • kareem.ns.cloudflare.com
  • lila.ns.cloudflare.com
Original source fields · JSON
Uuid
6e790173-2720-4b30-986a-6c393a93bb6d
Final url
https://g0gle.hh-meet.com/Windows/invite.php
Status
200
History
[
    {
        "url": "https://g0gle.hh-meet.com/",
        "status": 200
    },
    {
        "url": "https://g0gle.hh-meet.com/Windows/",
        "status": 302
    },
    {
        "url": "https://g0gle.hh-meet.com/Windows/invite.php",
        "status": 200
    }
]
DOM structure hash
b0a19403907f52ab07d5a87f2bc1fdefefb567ff23422e17661c02603f227eeb
Document hash
7fd3d2956d216c23e560f747d2ea30fb469986fac634ddc483e38bcca49bdd95
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "g0gle.hh-meet.com",
        "type": "A",
        "value": "104.21.62.180"
    },
    {
        "name": "g0gle.hh-meet.com",
        "type": "A",
        "value": "172.67.137.234"
    },
    {
        "name": "g0gle.hh-meet.com",
        "type": "AAAA",
        "value": "2606:4700:3033::6815:3eb4"
    },
    {
        "name": "g0gle.hh-meet.com",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:89ea"
    }
]
Dnssec valid
false
Ip
104.21.62.180
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "OwnRegistrar, Inc.",
    "created": "2026-06-08T14:04:32Z",
    "updated": "2026-06-08T14:04:32Z",
    "expires": "2027-06-08T14:04:32Z",
    "nameservers": [
        "kareem.ns.cloudflare.com",
        "lila.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 60

SHA-256 5578f06c4838c546a89c4469314249dd8428118d1a56d822ca69c2ec8a3eb131

Open report
URLScanOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

01a17917-f94c-72cb-bf23-21fdb61135da

Final URL

http://g0gle.hh-meet.com/

Redirects

  • To
    https://g0gle.hh-meet.com/
    From
    http://g0gle.hh-meet.com/
    Status
    307
  • To
    http://g0gle.hh-meet.com/
    From
    https://g0gle.hh-meet.com/
    Status
    307
  • To
    https://g0gle.hh-meet.com/
    From
    http://g0gle.hh-meet.com/
    Status
    307
  • To
    https://g0gle.hh-meet.com/
    From
    https://g0gle.hh-meet.com/

Document hash

04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

11

Differs from the registration date in WHOIS (2026-06-08), which gives 140 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Registered domain age, days

140

Page requests

12

Provider verdicts

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

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a17917-f94c-72cb-bf23-21fdb61135da
Final url
http://g0gle.hh-meet.com/
Redirects
[
    {
        "to": "https://g0gle.hh-meet.com/",
        "from": "http://g0gle.hh-meet.com/",
        "status": 307
    },
    {
        "to": "http://g0gle.hh-meet.com/",
        "from": "https://g0gle.hh-meet.com/",
        "status": 307
    },
    {
        "to": "https://g0gle.hh-meet.com/",
        "from": "http://g0gle.hh-meet.com/",
        "status": 307
    },
    {
        "to": "https://g0gle.hh-meet.com/",
        "from": "https://g0gle.hh-meet.com/"
    }
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
11

Differs from the registration date in WHOIS (2026-06-08), which gives 140 days on the scan date 2026-10-26. The two sources disagree; both values are kept as recorded.

Apex age days
140
Requests
12
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 60,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
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
01a1784e-2695-70ad-8573-80278e7a06e5
score
null
malicious
null
result_at
null
enriched_at
2026-10-27T09:20:18Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-27 10:20:18"}
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

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

71 / 100 · heuristic score · 0 brand references · 1 classification

Open report

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: 22 fields

CAA records

Domain
g0gle.hh-meet.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
1147

Trackers

Requests
5
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    WikiMedia
    Company
    Wikimedia Foundation
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
12
TLS
36
Waiting
120
Connection
8
Download
0
Response time, ms
176

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
44
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    162.159.44.22
    Host
    kareem.ns.cloudflare.com
  • IP address
    108.162.192.186
    Host
    lila.ns.cloudflare.com
DNS zone
hh-meet.com

Cookies

Cookies
  • Name
    WMF-Uniq
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

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

TLS certificate

Issuer
Google Trust Services / WE1
Subject
hh-meet.com

DNS records

A
  • 188.114.96.3
  • 188.114.97.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://g0gle.hh-meet.com

Registration record

Registrar
OwnRegistrar, Inc.
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • kareem.ns.cloudflare.com
  • lila.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Caa records
{
    "domain": "g0gle.hh-meet.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-26T16:17:26Z",
    "first": "2026-10-26T16:17:26Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1147
}
Trackers
{
    "requests": 5,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "WikiMedia",
            "company": "Wikimedia Foundation",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 12,
        "tls": 36,
        "wait": 120,
        "connect": 8,
        "download": 0
    },
    "response_ms": 176
}
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": 44,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.22",
            "host": "kareem.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.186",
            "host": "lila.ns.cloudflare.com"
        }
    ],
    "zone": "hh-meet.com"
}
Cookies
{
    "cookies": [
        {
            "name": "WMF-Uniq",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "hh-meet.com"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.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://g0gle.hh-meet.com"
    ]
}
Registration record
{
    "registrar": "OwnRegistrar, Inc.",
    "created": "2026-06-08T14:04:32Z",
    "updated": "2026-06-08T14:04:32Z",
    "expires": "2027-06-08T14:04:32Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "kareem.ns.cloudflare.com",
        "lila.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about g0gle.hh-meet.com

Is g0gle.hh-meet.com legit?

PhishDestroy rates g0gle.hh-meet.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-26T15:09:21Z. Retrieved (as stored): 2026-10-26T19:53:16Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is g0gle.hh-meet.com safe to connect a wallet?

This report does not record which wallet requests g0gle.hh-meet.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 g0gle.hh-meet.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 · 8 captures

Stored capture 1 / 8
SourceStored capture
Recorded
StateStored capture
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)
g0gle.hh-meet.com: caution — 20/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card g0gle.hh-meet.com: caution — 20/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 39f40046398c

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 60 report ↗
IP Context United Kingdom188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) OwnRegistrar US(US)
Abuse contactabuse@ownregistrar.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for hh-meet.com →
Registration (base domain)hh-meet.com · Created Jun 8, 2026 (147d) — Expires Jun 8, 2027
WHOIS statusok
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 71/100
Submitted URLhttp://g0gle.hh-meet.com/
Favicon Hash
Case ID
Observed page title
Zoom Client Update
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 60 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • kareem.ns.cloudflare.com
  • lila.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-04 18:07:10
Valid until
2027-01-02 19:06:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint81ec61b1d0f0157492fab94de8d0c256eeb54603de31a67e005831b19378e283
Certificate names · 2 SANs
  • hh-meet.com
  • *.hh-meet.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.96.3rapiddns.io

Latest Classified Outcome 2026-11-02 11:31:02 UTC

The site was serving its pages at the latest check.

Technical details
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-11-02 11:31:02 UTC
RDAP registration
Observed timeline last reachable: 2026-11-02 11:31:02 UTC last content: 2026-11-02 11:31:02 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 subdomains1

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

  • www.g0gle.hh-meet.comDomain record
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
CRDF
SOCRadar
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of g0gle.hh-meet.com · checked Oct 26, 2026

91
Good
Performance
FCP
2.76 s
First Contentful Paint
LCP
2.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.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://g0gle.hh-meet.com/
Final URL: https://g0gle.hh-meet.com/Iphone/invite.php
Zoom Client Update
Response
HTTP 200
HTML body
5.8 KB
Compressed
2.2 KB
Links
0 internal · 2 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a50ac5703b36a31a-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Mon, 26 Oct 2026 16:17:27 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=3EizGzC9u%2BOdXTHJEaQzCSV8Oc90F2CCBYlo0ULBFVe5qANfGAK%2FbgwWEL3ATbzlU3b8B1K1UAbwZsHZ0%2F7cxWE5F7YQvjIjz7PKcm6A5TVMNNTmmWCW1ricQhwzYEllO7Ll7Q%3D
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-turbo-charged-by
LiteSpeed

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

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

Captured network requests

Network requests: 12 SHA-256 hashes: 9 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-10-29 01:56 UTC.

Open this scan on URLScan 01a17917-f94c-72cb-bf23-21fdb61135da ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Zoom Client Update
Crawler
Index of /
g0gle.hh-meet.com
Stored observation history7

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    redirected→live_content

    content_served

Earlier observations 2
  1. Availability monitor · Recorded state

    redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected

    http_redirect

All retained availability observations36

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:02.000000
    Evidence SHA-256
    d45fefd8a47e83a481967c25d0cfcbd0b0d9db633f5ca86367e4891ec6a6a46a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:02
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:02.000000
    Evidence SHA-256
    d45fefd8a47e83a481967c25d0cfcbd0b0d9db633f5ca86367e4891ec6a6a46a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:02
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 11:20:40.834886
    Evidence SHA-256
    6b72dd67b3184766be6163de1e7b9604e36c85641b1d2618e2bdbe21069459a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 11:20:40.834886
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:33:51.000000
    Evidence SHA-256
    070d627177610afb94ddee4232c00ad0f7b3307957576fd17dd9f43683a9496e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:33:51
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:33:51.000000
    Evidence SHA-256
    070d627177610afb94ddee4232c00ad0f7b3307957576fd17dd9f43683a9496e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:33:51
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:35:46.000000
    Evidence SHA-256
    7143d20131fe64fa2c83827bf5fd26634a0fa223936741661be3b115ced2f544
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:35:46
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:35:46.000000
    Evidence SHA-256
    7143d20131fe64fa2c83827bf5fd26634a0fa223936741661be3b115ced2f544
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:35:46
    Evidence reason
    alive_content
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 11:20:10.198716
    Evidence SHA-256
    b2987bb7a7acc32f1f9011b7a56a5a9a8539c203c0dded9abde43c0e22a9adeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 11:20:10.198716
    Evidence reason
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:23:26.000000
    Evidence SHA-256
    3b10dac3167ad1e10c51b584209e0a305e38ca9035c5c79c9c54a44172db346f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:26
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 04:23:26.000000
    Evidence SHA-256
    3b10dac3167ad1e10c51b584209e0a305e38ca9035c5c79c9c54a44172db346f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:26
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:35:39.000000
    Evidence SHA-256
    21ec4422d80c8d0e7e3bb78e291a8d8a207f6f1a3ccc4a0784ee1b6ef0f96e59
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:35:39
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:35:39.000000
    Evidence SHA-256
    21ec4422d80c8d0e7e3bb78e291a8d8a207f6f1a3ccc4a0784ee1b6ef0f96e59
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:35:39
    Evidence reason
    alive_content
  13. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:55:48.000000
    Evidence SHA-256
    4f541fe1efd1a8d03f03197b5281d72ad6b2b8277e610ac1b8e2c264f2c3a843
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:55:48
    Evidence reason
    alive_content
  15. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:55:48.000000
    Evidence SHA-256
    4f541fe1efd1a8d03f03197b5281d72ad6b2b8277e610ac1b8e2c264f2c3a843
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:55:48
    Evidence reason
    alive_content
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:08:39.000000
    Evidence SHA-256
    f479a81821f047309e7a0a33da5b7e2d3e2dbff590700d96dd2b7ed190abe7cf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:08:39
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:08:39.000000
    Evidence SHA-256
    f479a81821f047309e7a0a33da5b7e2d3e2dbff590700d96dd2b7ed190abe7cf
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:08:39
    Evidence reason
    alive_content
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:09:38.000000
    Evidence SHA-256
    912cd4fabf454c2b4fe08bc97ac3bb3bb1220d0d02c91fe9099a8e7f8bc478f8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:09:38
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:09:38.000000
    Evidence SHA-256
    912cd4fabf454c2b4fe08bc97ac3bb3bb1220d0d02c91fe9099a8e7f8bc478f8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:09:38
    Evidence reason
    alive_content
  20. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:09:56.000000
    Evidence SHA-256
    ec5de5d8a8c885089c341f81d8b1e1af8763cc7f7aa09a12cf22e5643738b25d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:09:56
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:09:56.000000
    Evidence SHA-256
    ec5de5d8a8c885089c341f81d8b1e1af8763cc7f7aa09a12cf22e5643738b25d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:09:56
    Evidence reason
    alive_content
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:10:27.000000
    Evidence SHA-256
    0a02ab66f50d9bfb3c21a71e13e2e56b7391b6ac5c969249353e9585985568f8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:10:27
    Evidence reason
    alive_content
  24. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:10:27.000000
    Evidence SHA-256
    0a02ab66f50d9bfb3c21a71e13e2e56b7391b6ac5c969249353e9585985568f8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:10:27
    Evidence reason
    alive_content
  25. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:09.000000
    Evidence SHA-256
    0198105caf9f5e3fc291448e4878c6e95b2cf8e8a03b20545d718dbaabcc2433
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-29 03:39:09
    Evidence reason
    redirect
  26. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:09.000000
    Evidence SHA-256
    0198105caf9f5e3fc291448e4878c6e95b2cf8e8a03b20545d718dbaabcc2433
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-29 03:39:09
    Evidence reason
    redirect
  27. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  28. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:04:37.000000
    Evidence SHA-256
    9a1470ba4b8d29a9da45731d52dbdaac6320f18e0fcf3cbbd3db5dd19b83c662
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 12:04:37
    Evidence reason
    redirect
  29. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:04:37.000000
    Evidence SHA-256
    9a1470ba4b8d29a9da45731d52dbdaac6320f18e0fcf3cbbd3db5dd19b83c662
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 12:04:37
    Evidence reason
    redirect
  30. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:44.000000
    Evidence SHA-256
    ea282f4c14d35e33d2fe6bdc912a688b20519a6e8bd956c3cc9fd570e0f3a885
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 00:04:44
    Evidence reason
    redirect
  31. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:04:44.000000
    Evidence SHA-256
    ea282f4c14d35e33d2fe6bdc912a688b20519a6e8bd956c3cc9fd570e0f3a885
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 00:04:44
    Evidence reason
    redirect
  32. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:25.000000
    Evidence SHA-256
    4ee79164ad14c26708d6f04fb2e272139854aec9596ed7b13811e6d2445bfb14
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-27 12:04:25
    Evidence reason
    redirect
  33. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:04:25.000000
    Evidence SHA-256
    4ee79164ad14c26708d6f04fb2e272139854aec9596ed7b13811e6d2445bfb14
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-27 12:04:25
    Evidence reason
    redirect
  34. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 17:43:53.000000
    Evidence SHA-256
    88d08197eb3480d596790c0e2fd39e133ab943a4ac744eebc8b1ceba6c7e07b9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 17:43:53
    Evidence reason
  35. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 17:43:53.000000
    Evidence SHA-256
    88d08197eb3480d596790c0e2fd39e133ab943a4ac744eebc8b1ceba6c7e07b9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 17:43:53
    Evidence reason
  36. 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-10-26 17:18:12.960038
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 12. 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
    g0gle.hh-meet.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 60
  • 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: 3/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as phishing, Security threats
  • Automated brand label: Google
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: OwnRegistrar, Inc.. Abuse contacts: 1.
    • abuse@ownregistrar.com
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

6 entries
  1. Abuse report sent

    PD-20261026-702AC3 · Receipt 83502

    abuse@ownregistrar.com
  2. URLScan

    Page captured

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    g0gle.hh-meet.com

    View source
  6. VirusTotal

    3/92 engine detections

    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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-702AC3 Recipient: abuse@ownregistrar.com
Blocklist hits included with submission: OpenPhish
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.

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 g0gle.hh-meet.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.

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/g0gle.hh-meet.com"
  title="PhishDestroy threat report for g0gle.hh-meet.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>