Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 9. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
googlel0gin.netlify.app favicon

googlel0gin.netlify.app

In short

PhishDestroy stores a record for googlel0gin.netlify.app. Source observations are dated separately; missing checks do not establish safety.

“Sign in - Google Accounts”

Review the evidence
Registrar
United StatesNetlify
Resolved IP
Germany63.176.8.218Amazon.com, Inc. · CDN
First observed
Oct 28, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 9/92 Stored blocklist matches: 1
VirusTotal
9 / 92
engine detections ·
Blocklist matches
1
Phishunt
URLScan
Malicious
engine verdict · score 92
Page captures
9
open gallery
Oct 28, 2026 CDN
X Telegram API

Questions about googlel0gin.netlify.app

Is googlel0gin.netlify.app legit?

PhishDestroy stores a record for googlel0gin.netlify.app. Source observations are dated separately; missing checks do not establish safety.

Is googlel0gin.netlify.app safe to connect a wallet?

This report does not record which wallet requests googlel0gin.netlify.app 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 googlel0gin.netlify.app?

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

Source evidenceVirusTotal 9 / 92 6 sources

VirusTotal

9 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
50
Malicious
8
Suspicious
1
Undetected
33

Vendor labels

DNS8
phishing
ESET
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
suspicious
Kaspersky
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::258
  • TTL, seconds
    120
    Type
    A
    Value
    98.84.224.111
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::259
  • TTL, seconds
    120
    Type
    A
    Value
    18.208.88.157

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial
cd5d0afb0611b5bd9d692535c0ca7c4
SHA-256
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Subject
*.netlify.app
Valid until
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar IANA ID
625
Registrar URL
http://www.name.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 50,
    "malicious": 8,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "suspicious",
    "Kaspersky": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
Name.com, Inc.
Created
2018-05-08T22:48:05Z
Expires
2025-05-08T22:48:05Z
Updated
2024-04-11T16:00:14Z
First seen
2026-08-27T17:35:45Z
DNS records
[
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    }
]
Dns at
2026-10-28T00:49:20Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "serial": "cd5d0afb0611b5bd9d692535c0ca7c4",
    "sha256": "bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478",
    "subject": "*.netlify.app",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2018-05-08T22:48:05Z",
    "updated": "2024-04-11T16:00:14Z",
    "expires": "2025-05-08T22:48:05Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 8 malicious + 1 suspicious / 92 · 2026-10-28 00:43:58 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-28T00:43:58Z
fetched_at
2026-10-28T00:55:44Z
stats
{"timeout":0,"harmless":50,"malicious":8,"suspicious":1,"undetected":33}

URLScan

Malicious · engine verdict · score 92

SHA-256 78031b5e7631fd1359d063a578fa4dac9f15bf0a47896de7c4798e30a6729d91

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a17fd1-23a9-7133-98db-dc2cbab20964

Final URL

https://googlel0gin.netlify.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://googlel0gin.netlify.app/
    From
    http://googlel0gin.netlify.app/
    Status
    307

IP address

63.176.8.218

Reverse DNS (PTR)

ec2-63-176-8-218.eu-central-1.compute.amazonaws.com

Contacted IP addresses

  • 63.176.8.218

Autonomous systems (ASN)

  • 16509

Server countries

  • DE

Document hash

01439f00af75007958d5e28404c8bfb83da8c0f4ab9fd40d19806cb5abe757f6

TLS session and certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Cipher
AES_128_GCM
Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

60

Registered domain age, days

2831

Certificate age, days

254

Certificate validity, days

396

Page requests

5

Provider verdicts

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

HTTP headers

Server
Netlify
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a17fd1-23a9-7133-98db-dc2cbab20964
Final url
https://googlel0gin.netlify.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://googlel0gin.netlify.app/",
        "from": "http://googlel0gin.netlify.app/",
        "status": 307
    }
]
Ip
63.176.8.218
Ptr
ec2-63-176-8-218.eu-central-1.compute.amazonaws.com
Contacted IP addresses
[
    "63.176.8.218"
]
Asns
[
    "16509"
]
Countries
[
    "DE"
]
Document hash
01439f00af75007958d5e28404c8bfb83da8c0f4ab9fd40d19806cb5abe757f6
Tls
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Domain age days
60
Apex age days
2831
Tls age days
254
Tls valid days
396
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Netlify",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
}
Separate monitor record · 2026-10-28 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a17fd1-23a9-7133-98db-dc2cbab20964
score
0
malicious
false
result_at
2026-10-28T04:30:16Z
enriched_at
2026-10-28T09:12:56Z
source_timestamps
{"urlscan_result_at":"2026-10-28 05:30:16","urlscan_enriched_at":"2026-10-28 10:12:56"}
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

10 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-10-28T03:20:16Z

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-28T03:20:16Z
source_timestamp
2026-10-28 04:20:16
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
netlify.app
Allowed issuers
  • digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226

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
2270

Page title and metadata

Page title
Sign in - Google Accounts

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
212
TLS
35
Waiting
36
Connection
17
Download
0
Response time, ms
300

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
3545
CO₂, grams
0.0001
Cleaner than, %
94

DNS servers

Nameservers
  • IP address
    198.51.44.65
    Host
    dns3.p01.nsone.net
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
  • IP address
    198.51.45.1
    Host
    dns2.p01.nsone.net
DNS zone
netlify.app

Location

IP address
2a05:d014:58f:6200::259
ASN
16509
Organization
Amazon.com, Inc.
City
Frankfurt
Country
DE

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app

DNS records

A
  • 63.176.8.218
  • 35.157.26.135
AAAA
  • 2a05:d014:58f:6200::259
  • 2a05:d014:58f:6200::258

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

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
max-age=31536000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a05:d014:58f:6200::258
IP version
6

Redirects

Redirect chain
  • https://googlel0gin.netlify.app

Technology stack

Technologies
  • Netlify
  • HSTS
  • DigiCert

Page links

Internal links
2

HTTP headers

Response headers
Server
Netlify
Content-type
text/html; charset=UTF-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "netlify.app",
    "issuers": [
        "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-27T23:37:22Z",
    "first": "2026-10-27T23:37:22Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2270
}
Page title and metadata
{
    "title": "Sign in - Google Accounts"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 212,
        "tls": 35,
        "wait": 36,
        "connect": 17,
        "download": 0
    },
    "response_ms": 300
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 3545,
    "co2_grams": 0.0001,
    "cleaner_than": 94
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.65",
            "host": "dns3.p01.nsone.net"
        },
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        },
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        },
        {
            "ip": "198.51.45.1",
            "host": "dns2.p01.nsone.net"
        }
    ],
    "zone": "netlify.app"
}
Location
{
    "ip": "2a05:d014:58f:6200::259",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Frankfurt",
    "country": "DE"
}
Ssl
{
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app"
}
DNS records
{
    "A": [
        "63.176.8.218",
        "35.157.26.135"
    ],
    "AAAA": [
        "2a05:d014:58f:6200::259",
        "2a05:d014:58f:6200::258"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a05:d014:58f:6200::258",
    "family": 6
}
Redirects
{
    "chain": [
        "https://googlel0gin.netlify.app"
    ]
}
Tech stack
{
    "technologies": [
        "Netlify",
        "HSTS",
        "DigiCert"
    ]
}
Page links
{
    "internal_count": 2
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=UTF-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
    }
}
Blocklist matchesPhishDestroy · Phishunt · no match in the other 10 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Checked, no match

Last checked

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://googlel0gin.netlify.app/
Position1 / 9
Open capture Wayback Download
All capture links and hashes (9)
googlel0gin.netlify.app: Google impersonation — Flagged by Phishunt, 22/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card googlel0gin.netlify.app: Google impersonation — Flagged by Phishunt, 22/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v feb5230ca5a4

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 92 report ↗
IP Context Germany63.176.8.218 Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Netlify US(US)
Abuse contactabuse@netlify.com
Hosting abuse contact abuse@netlify.com Amazon.com, Inc. · AS16509
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 28, 2026
DOM Analysisanalyzed Oct 28, 2026score 10/1001 brand signal
Submitted URLhttp://googlel0gin.netlify.app/
Favicon Hash
Observed page title
Sign in - Google Accounts
Automated brand references
Google
TLS Certificate
Issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1 · stored validity ends in 140 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Germany63.176.8.218
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
GermanyFrankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate names · 2 SANs
  • *.netlify.app
  • netlify.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 · 63.176.8.218rapiddns.io

Latest Classified Outcome 2026-10-30 12:06:28 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: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-30 12:06:28 UTC
RDAP registration
Observed timeline last reachable: 2026-10-30 00:05:47 UTC last content: 2026-10-30 00:05:47 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 92 security vendors flagged this domain
View on VT
Last analyzed
Criminal IP
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
Seclookup
SOCRadar
Sophos
URLQuery
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
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://googlel0gin.netlify.app/
Final URL: https://googlel0gin.netlify.app/
Sign in - Google Accounts
Response
HTTP 200
HTML body
3.5 KB
Compressed
1.3 KB
Links
4 internal · 0 external
Selected response headers
Cache-Control: public,max-age=0,must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
Server: Netlify
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Accept-Ranges
bytes
Age
0
Cache-Control
public,max-age=0,must-revalidate
Cache-Status
"Netlify Edge"; fwd=miss; fwd-status=200; stored
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Tue, 27 Oct 2026 23:37:36 GMT
Etag
"3a949c1f92da31d4c92bdfc82aa1627c-ssl-df"
Server
Netlify
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Nf-Request-Id
01M5ZVKYDR94CGC9MPY8KGT68R

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: 5 SHA-256 hashes: 2 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:53 UTC.

Open this scan on URLScan 01a17fd1-23a9-7133-98db-dc2cbab20964 ↗

Stored observation history2

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. Domain monitor · First collection record

    Reachable

All retained availability observations14

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
    stale
    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 13:06:28.000000
    Evidence SHA-256
    fd9b1e58da03b132b4fed502c2338d18e85a355300fc3212df07e6654336fc0b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:06:28
    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-10-30 13:06:28.000000
    Evidence SHA-256
    fd9b1e58da03b132b4fed502c2338d18e85a355300fc3212df07e6654336fc0b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:06:28
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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 01:05:47.000000
    Evidence SHA-256
    f387735cf76fd5b0029e2b71485877f9e4f882cb76f14935595f22e6a66078d2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:05:47
    Evidence reason
    alive_content
  4. 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 01:05:47.000000
    Evidence SHA-256
    f387735cf76fd5b0029e2b71485877f9e4f882cb76f14935595f22e6a66078d2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:05:47
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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 13:04:35.000000
    Evidence SHA-256
    f06f04f57c928a392d264268b70f9655823854a983ce608de380618cc8d48964
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 13:04:35
    Evidence reason
    alive_content
  6. 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 13:04:35.000000
    Evidence SHA-256
    f06f04f57c928a392d264268b70f9655823854a983ce608de380618cc8d48964
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 13:04:35
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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 05:04:21.000000
    Evidence SHA-256
    541f162b59fc7fcf530081ffc8699eaf91012c8fa5b33348a17d6c845c52aa58
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 05:04:21
    Evidence reason
    alive_content
  8. 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 05:04:21.000000
    Evidence SHA-256
    541f162b59fc7fcf530081ffc8699eaf91012c8fa5b33348a17d6c845c52aa58
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 05:04:21
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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 00:56:20.000000
    Evidence SHA-256
    95211e3f5e20f0c3abadea6accfd1acc905ee43b28e268e5041a771437cc2302
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:56:20
    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-10-29 00:56:20.000000
    Evidence SHA-256
    95211e3f5e20f0c3abadea6accfd1acc905ee43b28e268e5041a771437cc2302
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 00:56:20
    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
    stale
    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-28 13:03:13.000000
    Evidence SHA-256
    4b161d7636b1b4c715c02612086c4da92862107f1dc084f49139bf4f57bd1712
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:03:13
    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-28 13:03:13.000000
    Evidence SHA-256
    4b161d7636b1b4c715c02612086c4da92862107f1dc084f49139bf4f57bd1712
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:03:13
    Evidence reason
    alive_content
  13. 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-28 01:04:56.000000
    Evidence SHA-256
    6e7578120ff8f476d402722900805084096b4084e03958abc7c4725514fdd1a1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:04:56
    Evidence reason
  14. 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-28 01:04:56.000000
    Evidence SHA-256
    6e7578120ff8f476d402722900805084096b4084e03958abc7c4725514fdd1a1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:04:56
    Evidence reason

Threat Response Pipeline

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

Recorded events: 10. 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
    googlel0gin.netlify.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Blocklist Detection · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 92
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 9/92
  • Blocklist Detection
    Found in blocklists: Phishunt
  • Automated brand label: Google
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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

4 entries
  1. VirusTotal

    9/92 engine detections

    View source
  2. Added to PhishDestroy

    googlel0gin.netlify.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    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.

googlel0gin.netlify.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 9 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 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 googlel0gin.netlify.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.

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/googlel0gin.netlify.app"
  title="PhishDestroy threat report for googlel0gin.netlify.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>