Skip to security report
Analytics Dashboard
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
fanimehop.lovable.app favicon

fanimehop.lovable.app

“Website Takedown Notice - Lovable Trust & Safety”

Review the evidence
Registrar
Lovable Labs
Resolved IP
Sweden185.41.148.1Cloudflare, Inc. · CDN
Registered
May 6, 2023
First observed
Oct 26, 2026
PhishDestroy assessment High
63/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored PhishDestroy threat listing
URLScan
Malicious
engine verdict · score 73
Page captures
5
open gallery
Domain age
1,270 days
Oct 26, 2026 CDN
X Telegram API
Source evidence 5 sources

URLScan

Malicious · engine verdict · score 73

SHA-256 b52aa5926975288ba345e52d9c4385d2df5e4f304054eb0e23637fe58d079f3b

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a175fb-978e-7617-a55c-bb02c52c64cd

Final URL

https://fanimehop.lovable.app/blocked

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://fanimehop.lovable.app/
    From
    http://fanimehop.lovable.app/
    Status
    307
  • To
    https://fanimehop.lovable.app/blocked
    From
    https://fanimehop.lovable.app/
    Status
    302

IP address

185.41.148.1

Reverse DNS (PTR)

lovable-app-wd-1-4.p.l5e.io

Contacted domains

  • fonts.googleapis.com

Contacted IP addresses

  • 142.250.68.202
  • 185.41.148.1

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US
  • SE

Linked domains

  • lovable.dev

Document hash

5bb95de6918b8d719455463206044dad5e0a3dc076ae02f9a843aecf5333b618

Script hashes

  • 0ffc22a57571d8ed7a89038c2a31a49e845fadcaf7690839013397bca9990117

JavaScript globals

  • __reactRouterVersion

TLS session and certificate

Subject alternative names
  • lovable.app
  • *.lovable.app
Cipher
AES_128_GCM
Issuer
WE1
Subject
lovable.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

81

Registered domain age, days

81

Certificate age, days

15

Certificate validity, days

90

Page requests

10

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Uuid
01a175fb-978e-7617-a55c-bb02c52c64cd
Final url
https://fanimehop.lovable.app/blocked
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://fanimehop.lovable.app/",
        "from": "http://fanimehop.lovable.app/",
        "status": 307
    },
    {
        "to": "https://fanimehop.lovable.app/blocked",
        "from": "https://fanimehop.lovable.app/",
        "status": 302
    }
]
Ip
185.41.148.1
Ptr
lovable-app-wd-1-4.p.l5e.io
Contacted domains
[
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.250.68.202",
    "185.41.148.1"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US",
    "SE"
]
Linked domains
[
    "lovable.dev"
]
Document hash
5bb95de6918b8d719455463206044dad5e0a3dc076ae02f9a843aecf5333b618
Script hashes
[
    "0ffc22a57571d8ed7a89038c2a31a49e845fadcaf7690839013397bca9990117"
]
Globals
[
    "__reactRouterVersion"
]
Tls
{
    "san": [
        "lovable.app",
        "*.lovable.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "lovable.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-09T00:33:27Z",
    "valid_from": "2026-10-10T23:33:33Z"
}
Domain age days
81
Apex age days
81
Tls age days
15
Tls valid days
90
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 73,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Separate monitor record · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a175fb-978e-7617-a55c-bb02c52c64cd
score
0
malicious
false
result_at
2026-10-26T04:30:09Z
enriched_at
2026-10-26T09:11:19Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:09","urlscan_enriched_at":"2026-10-26 10:11:19"}
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

63 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-26T03:20:13Z

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
0
analyzed_at
2026-10-26T03:20:13Z
source_timestamp
2026-10-26 04:20:13
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
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
11
Suspicious
3
Undetected
32

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Namecheap Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    185.41.148.1
  • TTL, seconds
    300
    Type
    A
    Value
    185.41.148.2
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a07:8240::2
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a07:8240::1

DNS records observed

JARM fingerprint

27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • lovable.app
  • *.lovable.app
Issuer
Google Trust Services / WE1
Serial
a0305f14b2a99af130a9e43af07d3e5
SHA-256
bfd87661dd48f66569436bba3b43026fcf7c54c23ec933e58b748a6db8a5899f
Subject
lovable.app
Valid until
Valid from

Registration record

Registrar
Namecheap Inc.
Registrar IANA ID
1068
Registrar URL
https://www.namecheap.com/
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ivan.ns.cloudflare.com
  • rafe.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 11,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Namecheap Inc.
Created
2023-05-06T14:03:05Z
Expires
2028-05-06T14:03:05Z
Updated
2025-02-10T14:47:24Z
First seen
2026-08-05T13:08:38Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "185.41.148.1"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.41.148.2"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::2"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::1"
    }
]
Dns at
2026-10-21T13:03:20Z
Jarm
27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "lovable.app",
        "*.lovable.app"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "a0305f14b2a99af130a9e43af07d3e5",
    "sha256": "bfd87661dd48f66569436bba3b43026fcf7c54c23ec933e58b748a6db8a5899f",
    "subject": "lovable.app",
    "valid_to": "2027-01-09T00:33:27Z",
    "valid_from": "2026-10-10T23:33:33Z"
}
Registration record
{
    "registrar": "Namecheap Inc.",
    "registrar_iana_id": "1068",
    "registrar_url": "https://www.namecheap.com/",
    "created": "2023-05-06T14:03:05Z",
    "updated": "2025-02-10T14:47:24Z",
    "expires": "2028-05-06T14:03:05Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ivan.ns.cloudflare.com",
        "rafe.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Website checksOriginal source recordRetrieved: 22 fields

CAA records

Domain
fanimehop.lovable.app

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

User agents
  • Googlebot
  • Bingbot
  • Twitterbot
  • facebookexternalhit
  • *
Present
Yes

Page title and metadata

Page title
Website Takedown Notice - Lovable Trust & Safety
Author
Lovable Trust & Safety
Open Graph type
website
Open Graph image
https://lovable.dev/opengraph-image-p98pqg.png
Open Graph title
8f233f00-073f-4162-9068-07aeca720f0a
Description
This website has been taken down by Lovable Trust and Safety team for policy violations. Report suspicious activity at lovable.dev/abuse
Twitter card
summary_large_image
Twitter account
@lovable_dev
Open Graph description
Lovable Generated Project

Trackers

Requests
6
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
21
TLS
12
Waiting
27
Connection
16
Download
0
Response time, ms
76

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

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

DNS servers

Nameservers
  • IP address
    173.245.58.216
    Host
    rafe.ns.cloudflare.com
  • IP address
    108.162.193.120
    Host
    ivan.ns.cloudflare.com
DNS zone
lovable.app

Location

IP address
2a07:8240::1
ASN
13335
Organization
Cloudflare, Inc.
Country
SE

TLS certificate

Issuer
Google Trust Services / WE1
Subject
lovable.app

DNS records

A
  • 185.41.148.2
  • 185.41.148.1
AAAA
  • 2a07:8240::2
  • 2a07:8240::1

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains
Observation
HSTS header does not contain the preload directive.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000; includeSubDomains
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
2a07:8240::1
IP version
6

Redirects

Redirect chain
  • https://fanimehop.lovable.app
  • /blocked
Count
1

Social profiles

Profiles
  • https://x.com/lovable_dev

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Caa records
{
    "domain": "fanimehop.lovable.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "agents": [
        "Googlebot",
        "Bingbot",
        "Twitterbot",
        "facebookexternalhit",
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Website Takedown Notice - Lovable Trust & Safety",
    "author": "Lovable Trust & Safety",
    "ogType": "website",
    "ogImage": "https://lovable.dev/opengraph-image-p98pqg.png",
    "ogTitle": "8f233f00-073f-4162-9068-07aeca720f0a",
    "description": "This website has been taken down by Lovable Trust and Safety team for policy violations. Report suspicious activity at lovable.dev/abuse",
    "twitterCard": "summary_large_image",
    "twitterSite": "@lovable_dev",
    "ogDescription": "Lovable Generated Project"
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 302,
    "timings": {
        "dns": 21,
        "tls": 12,
        "wait": 27,
        "connect": 16,
        "download": 0
    },
    "response_ms": 76
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 1713,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.58.216",
            "host": "rafe.ns.cloudflare.com"
        },
        {
            "ip": "108.162.193.120",
            "host": "ivan.ns.cloudflare.com"
        }
    ],
    "zone": "lovable.app"
}
Location
{
    "ip": "2a07:8240::1",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "country": "SE"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "lovable.app"
}
DNS records
{
    "A": [
        "185.41.148.2",
        "185.41.148.1"
    ],
    "AAAA": [
        "2a07:8240::2",
        "2a07:8240::1"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains",
    "message": "HSTS header does not contain the preload directive."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a07:8240::1",
    "family": 6
}
Redirects
{
    "chain": [
        "https://fanimehop.lovable.app",
        "/blocked"
    ],
    "count": 1
}
Social profiles
{
    "profiles": [
        "https://x.com/lovable_dev"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)
Observed page title
Website Takedown Notice - Lovable Trust & Safety
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 72 days
fanimehop.lovable.app: phishdestroy risk analysis, risk score 63/100 (high); not yet listed by external security vendors.
Social preview card fanimehop.lovable.app: phishdestroy risk analysis, risk score 63/100 (high); not yet listed by external security vendors. v 2a50ad22d268

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 73 report ↗
IP Context Sweden185.41.148.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Lovable Labs
Abuse contactabuse@lovable.dev
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for lovable.app →
Registration (base domain)lovable.app · Created May 6, 2023 — Expires May 6, 2028
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 63/100
Submitted URLhttp://fanimehop.lovable.app/
Favicon Hash
ICANN OVERSIGHT Registration: lovable.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain lovable.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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

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

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Sweden185.41.148.1
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
SwedenStockholm, SE
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-10 23:33:33
Valid until
2027-01-09 00:33:27
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbfd87661dd48f66569436bba3b43026fcf7c54c23ec933e58b748a6db8a5899f
Certificate names · 2 SANs
  • lovable.app
  • *.lovable.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 · 185.41.148.1rapiddns.io

Latest Classified Outcome 2026-10-27 11:03:51 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-27 11:03:51 UTC
RDAP registration
Observed timeline last reachable: 2026-10-26 02:14:45 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

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://fanimehop.lovable.app/
Final URL: http://fanimehop.lovable.app/blocked
Website Takedown Notice - Lovable Trust & Safety
This website has been taken down by Lovable Trust and Safety team for policy violations. Report suspicious activity at lovable.dev/abuse
Response
HTTP 200
HTML body
1.7 KB
Compressed
746 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Server: cloudflare
Security headers present
Strict-Transport-SecurityX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 29a40d56580a5366083461297773dbf146ec043d1156f432f5472cb3487f506b
Open Graph title: 8f233f00-073f-4162-9068-07aeca720f0a
Open Graph description: Lovable Generated Project
Twitter card: summary_large_image
Saved response-header values · 11
CF-RAY
a505e69d4fe44db6-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 26 Oct 2026 02:06:17 GMT
Referrer-Policy
strict-origin-when-cross-origin
Server
cloudflare
Strict-Transport-Security
max-age=31536000; includeSubDomains
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Robots-Tag
noindex, nofollow

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation 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

    redirected

    http_redirect

  2. Domain monitor · First collection record

    Reachable

All retained availability observations6

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_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    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:03:51.000000
    Evidence SHA-256
    0745276896c9e240bcaad2abd1b8ebeb524a965d3f83dd4b317131b2397b4a00
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 12:03:51
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    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:03:51.000000
    Evidence SHA-256
    0745276896c9e240bcaad2abd1b8ebeb524a965d3f83dd4b317131b2397b4a00
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 12:03:51
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    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-26 13:02:42.000000
    Evidence SHA-256
    a0e08869bd348d84b320bf1e29f8f52b1cf2e4e90804b9d0b0d5d51f28c48236
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-26 13:02:42
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    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-26 13:02:42.000000
    Evidence SHA-256
    a0e08869bd348d84b320bf1e29f8f52b1cf2e4e90804b9d0b0d5d51f28c48236
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-26 13:02:42
    Evidence reason
    redirect
  5. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 03:14:45.000000
    Evidence SHA-256
    420ff045202fcdad1ae005394b6a072e816f0aa97cf2a11c080017dea67da67c
    Evidence timestamp as recorded
    2026-10-26 03:14:45
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    false
  6. http_observationunknown
    Observation source
    http_observation
    Cause
    legacy_alive_unverified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    15
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 03:14:45.000000
    Evidence SHA-256
    438aaa486a8328be38956cb9be6a60de688016af2f3dede24542155c00253ff6
    Evidence timestamp as recorded
    2026-10-26 03:14:45

Threat Response Pipeline

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

Recorded events: 7. 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
    fanimehop.lovable.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 5 of 5
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 73
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • 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

3 entries
  1. Added to PhishDestroy

    fanimehop.lovable.app

    View source
  2. URLScan

    Page captured

    View source
  3. 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.

fanimehop.lovable.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including fanimehop.lovable.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/fanimehop.lovable.app"
  title="PhishDestroy threat report for fanimehop.lovable.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>