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

mofohoo.lovable.app

In short

PhishDestroy records that mofohoo.lovable.app shows an 18+ age verification gate with a single confirmation button over a street-scene background.

“Weryfikacja wieku — 18+”

Review the evidence
Registrar
Lovable Labs
Resolved IP
Sweden185.41.148.1Cloudflare, Inc. · CDN
Registered
May 6, 2023
First observed
Oct 31, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 5/92
VirusTotal
5 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 96
Cloudflare Radar
Phishing
Page captures
7
open gallery
Domain age
1,274 days
registered 2023-05-06 according to RDAP · source data differ
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that mofohoo.lovable.app shows an 18+ age verification gate with a single confirmation button over a street-scene background.

Critical
Status
Last known active
VirusTotal
5 / 92
Hosting
Sweden185.41.148.1Cloudflare, Inc. · CDN
Registrar
Lovable Labs
Registered
May 6, 2023
Page captures
7
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page on mofohoo.lovable.app presents an age verification gate titled "Weryfikacja wieku" with an 18+ badge. A short Polish message states the site contains content intended only for adults, and the main interaction is a single yellow "Potwierdzam" button that the visitor clicks to confirm they are of age. The gate sits over a dimmed photograph of a city street at dusk, so no content behind the prompt is visible in this capture.

The stored VirusTotal domain result reports 5 detections out of 92 engines. G-Data reported "phishing"; SOCRadar reported "phishing".

Source evidenceVirusTotal 5 / 92 8 sources

VirusTotal

5 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
52
Malicious
5
Suspicious
0
Undetected
35

Vendor labels

G-Data
phishing
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing, AI/ML Applications (alphaMountain.ai)

Registrar

Namecheap Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a07:8240::1
  • 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

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": 52,
    "malicious": 5,
    "suspicious": 0,
    "undetected": 35
}
Vendor labels
{
    "G-Data": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing, AI/ML Applications (alphaMountain.ai)"
}
Registrar
Namecheap Inc.
Created
2023-05-06T14:03:05Z
Expires
2028-05-06T14:03:05Z
Updated
2025-02-10T14:47:24Z
First seen
2026-10-08T09:29:38Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::1"
    },
    {
        "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"
    }
]
Dns at
2026-10-19T10:49:47Z
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"
}
Separate source record · 5 malicious + 0 suspicious / 92 · 2026-10-19 10:44:32 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-19T10:44:32Z
fetched_at
2026-10-31T22:55:51Z
stats
{"timeout":0,"harmless":52,"malicious":5,"suspicious":0,"undetected":35}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

0e0895b1-9ae9-4864-a2e0-8bb5c0ca5cb3

Final URL

https://mofohoo.lovable.app/

HTTP response

200

Navigation history

  • URL
    https://mofohoo.lovable.app/
    Status
    200

DOM structure hash

7ba4c5104369914283374572656d5f7129669bedd9f6bc53b583faa0600853a5

Document hash

22137a2e2f4831662d99e2f466d3ec149ca368be2536b10151b2594b6761ab4e

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    mofohoo.lovable.app
    Type
    A
    Value
    185.41.148.2
  • Name
    mofohoo.lovable.app
    Type
    A
    Value
    185.41.148.1
  • Name
    mofohoo.lovable.app
    Type
    AAAA
    Value
    2a07:8240::1
  • Name
    mofohoo.lovable.app
    Type
    AAAA
    Value
    2a07:8240::2

DNSSEC valid

No

IP address

127.0.1.2

127.0.1.2 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
CloudFlare, Inc.
Registered
Updated
Expires
Nameservers
  • ivan.ns.cloudflare.com
  • rafe.ns.cloudflare.com
Original source fields · JSON
Uuid
0e0895b1-9ae9-4864-a2e0-8bb5c0ca5cb3
Final url
https://mofohoo.lovable.app/
Status
200
History
[
    {
        "url": "https://mofohoo.lovable.app/",
        "status": 200
    }
]
DOM structure hash
7ba4c5104369914283374572656d5f7129669bedd9f6bc53b583faa0600853a5
Document hash
22137a2e2f4831662d99e2f466d3ec149ca368be2536b10151b2594b6761ab4e
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mofohoo.lovable.app",
        "type": "A",
        "value": "185.41.148.2"
    },
    {
        "name": "mofohoo.lovable.app",
        "type": "A",
        "value": "185.41.148.1"
    },
    {
        "name": "mofohoo.lovable.app",
        "type": "AAAA",
        "value": "2a07:8240::1"
    },
    {
        "name": "mofohoo.lovable.app",
        "type": "AAAA",
        "value": "2a07:8240::2"
    }
]
Dnssec valid
false
Ip
127.0.1.2

127.0.1.2 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "CloudFlare, Inc.",
    "created": "2023-05-06T14:03:05Z",
    "updated": "2025-10-10T12:55:21Z",
    "expires": "2029-05-06T14:03:05Z",
    "nameservers": [
        "ivan.ns.cloudflare.com",
        "rafe.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 96

SHA-256 d851279cb3a5225dda8b8e8cc521a5e8092b4a65e7b8d641e4e3fc524cf11dcd

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a19427-f662-753c-a02a-bcaf2027d366

Final URL

https://mofohoo.lovable.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://mofohoo.lovable.app/
    From
    http://mofohoo.lovable.app/
    Status
    307

IP address

2a07:8240::1

Contacted IP addresses

  • 2a07:8240::1

Autonomous systems (ASN)

  • 13335

Server countries

  • SE

Linked domains

  • lovable.dev

Document hash

d851279cb3a5225dda8b8e8cc521a5e8092b4a65e7b8d641e4e3fc524cf11dcd

Script hashes

  • d7992f5ff441ed7c0ed808eabc5b454af184ed81c6fbdd8fbff25c06790d194a
  • 194e9c15c79ab8aa373712b88d41dfd96a39a494ffec0b5566a2615cbd56ddee
  • a86e084b4f82709814be6c15fd6305daa783fda87ad95402da9a4d3a1dd6d748
  • 9005204863a3d003ce0c18bbbe50df0f4d246587e4d19a0d18de980479c61238

JavaScript globals

  • $R
  • parcelRequirebc80
  • Tinybird
  • __lovableEvents
  • __TSR_ROUTER__
  • __TSS_START_OPTIONS__

Cookies

  • __dpl
  • session-id

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

23

Differs from the registration date in RDAP (2023-05-06), which gives 1274 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

23

Differs from the registration date in RDAP (2023-05-06), which gives 1274 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

20

Certificate validity, days

90

Page requests

10

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
96
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
01a19427-f662-753c-a02a-bcaf2027d366
Final url
https://mofohoo.lovable.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://mofohoo.lovable.app/",
        "from": "http://mofohoo.lovable.app/",
        "status": 307
    }
]
Ip
2a07:8240::1
Contacted IP addresses
[
    "2a07:8240::1"
]
Asns
[
    "13335"
]
Countries
[
    "SE"
]
Linked domains
[
    "lovable.dev"
]
Document hash
d851279cb3a5225dda8b8e8cc521a5e8092b4a65e7b8d641e4e3fc524cf11dcd
Script hashes
[
    "d7992f5ff441ed7c0ed808eabc5b454af184ed81c6fbdd8fbff25c06790d194a",
    "194e9c15c79ab8aa373712b88d41dfd96a39a494ffec0b5566a2615cbd56ddee",
    "a86e084b4f82709814be6c15fd6305daa783fda87ad95402da9a4d3a1dd6d748",
    "9005204863a3d003ce0c18bbbe50df0f4d246587e4d19a0d18de980479c61238"
]
Globals
[
    "$R",
    "parcelRequirebc80",
    "Tinybird",
    "__lovableEvents",
    "__TSR_ROUTER__",
    "__TSS_START_OPTIONS__"
]
Cookies
[
    "__dpl",
    "session-id"
]
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
23

Differs from the registration date in RDAP (2023-05-06), which gives 1274 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
23

Differs from the registration date in RDAP (2023-05-06), which gives 1274 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
20
Tls valid days
90
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "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 · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a19427-f662-753c-a02a-bcaf2027d366
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

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

Open report
Separate monitor score · 0 / 100 · 2026-10-31T23:20:14Z

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-31T23:20:14Z
source_timestamp
2026-11-01 00:20:14
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
mofohoo.lovable.app — Age Verification Gate (18+)
ai_description
PhishDestroy records that mofohoo.lovable.app shows an 18+ age verification gate with a single confirmation button over a street-scene background.
ai_summary
The captured page on mofohoo.lovable.app presents an age verification gate titled "Weryfikacja wieku" with an 18+ badge. A short Polish message states the site contains content intended only for adults, and the main interaction is a single yellow "Potwierdzam" button that the visitor clicks to confirm they are of age. The gate sits over a dimmed photograph of a city street at dusk, so no content behind the prompt is visible in this capture. The stored VirusTotal domain result reports 5 detections out of 92 engines. G-Data reported "phishing"; SOCRadar reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 23:57:51
revision
dba7c7feb53db48d84abce0545afaa7dd746e60ad7d17238f06672d357c03c93
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

CAA records

Domain
mofohoo.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
Weryfikacja wieku — 18+
Author
Lovable
Open Graph type
website
Open Graph image
https://pub-bb2e103a32db4e198524a2e9ed8f35b4.r2.dev/lovp_281yxjxf5q8p993e2s3cnxt7fv/499ef79397aafff5643cbf1b712a21ed_1791216481457.png
Open Graph title
Weryfikacja wieku — 18+
Description
Ta strona zawiera treści przeznaczone wyłącznie dla osób pełnoletnich. Potwierdź, że masz ukończone 18 lat.
Twitter card
summary_large_image
Twitter account
@Lovable
Open Graph description
Ta strona zawiera treści przeznaczone wyłącznie dla osób pełnoletnich. Potwierdź, że masz ukończone 18 lat.

Trackers

Requests
9

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
6
TLS
19
Waiting
533
Connection
8
Download
0
Response time, ms
566

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
14724
CO₂, grams
0.0005
Cleaner than, %
63

DNS servers

Nameservers
  • IP address
    108.162.192.216
    Host
    rafe.ns.cloudflare.com
  • IP address
    172.64.33.120
    Host
    ivan.ns.cloudflare.com
DNS zone
lovable.app

Cookies

Cookies
  • Name
    __dpl
    Secure
    Yes
    SameSite
    Lax
  • Name
    session-id
    Secure
    Yes

Location

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

TLS certificate

Issuer
Google Trust Services / WE1
Subject
lovable.app

DNS records

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

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://mofohoo.lovable.app

Social profiles

Profiles
  • https://x.com/Lovable

Page links

External link addresses
  • https://lovable.dev/projects/lovp_281yxjxf5q8p993e2s3cnxt7fv
External links
1

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": "mofohoo.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": "Weryfikacja wieku — 18+",
    "author": "Lovable",
    "ogType": "website",
    "ogImage": "https://pub-bb2e103a32db4e198524a2e9ed8f35b4.r2.dev/lovp_281yxjxf5q8p993e2s3cnxt7fv/499ef79397aafff5643cbf1b712a21ed_1791216481457.png",
    "ogTitle": "Weryfikacja wieku — 18+",
    "description": "Ta strona zawiera treści przeznaczone wyłącznie dla osób pełnoletnich. Potwierdź, że masz ukończone 18 lat.",
    "twitterCard": "summary_large_image",
    "twitterSite": "@Lovable",
    "ogDescription": "Ta strona zawiera treści przeznaczone wyłącznie dla osób pełnoletnich. Potwierdź, że masz ukończone 18 lat."
}
Trackers
{
    "requests": 9
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 6,
        "tls": 19,
        "wait": 533,
        "connect": 8,
        "download": 0
    },
    "response_ms": 566
}
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": 14724,
    "co2_grams": 0.0005,
    "cleaner_than": 63
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.192.216",
            "host": "rafe.ns.cloudflare.com"
        },
        {
            "ip": "172.64.33.120",
            "host": "ivan.ns.cloudflare.com"
        }
    ],
    "zone": "lovable.app"
}
Cookies
{
    "cookies": [
        {
            "name": "__dpl",
            "secure": true,
            "same_site": "Lax"
        },
        {
            "name": "session-id",
            "secure": true
        }
    ]
}
Location
{
    "ip": "2a07:8240::2",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "country": "SE"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "lovable.app"
}
DNS records
{
    "A": [
        "185.41.148.1",
        "185.41.148.2"
    ],
    "AAAA": [
        "2a07:8240::1",
        "2a07:8240::2"
    ]
}
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://mofohoo.lovable.app"
    ]
}
Social profiles
{
    "profiles": [
        "https://x.com/Lovable"
    ]
}
Page links
{
    "external": [
        "https://lovable.dev/projects/lovp_281yxjxf5q8p993e2s3cnxt7fv"
    ],
    "external_count": 1
}
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"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about mofohoo.lovable.app

Is mofohoo.lovable.app legit?

PhishDestroy records that mofohoo.lovable.app shows an 18+ age verification gate with a single confirmation button over a street-scene background.

Is mofohoo.lovable.app safe to connect a wallet?

This report does not record which wallet requests mofohoo.lovable.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 mofohoo.lovable.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

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

Checked, no match

Last checked

Stored Capture · 7 captures

Cloudflare Radar 1 / 7 Used in the analysis Source file SHA-256: 0b028ec74f0e761ca6bdce40c9b6faf6e896f6ca08d42ed546da489ff8a0744a SHA-256 of the prepared copy given to the model: 1aace96d1cd0ba888b043fc11a59df328bc860ef2a615ef2b999aeb5e895e241
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://mofohoo.lovable.app/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)
Observed page title
Weryfikacja wieku — 18+
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 68 days

Domain details

Domain
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 Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://mofohoo.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
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
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
G-Data
Kaspersky
LevelBlue
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of mofohoo.lovable.app · checked Oct 31, 2026

96
Good
Performance
FCP
1.51 s
First Contentful Paint
LCP
1.51 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
4.8 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Captured network requests

Network requests: 10 SHA-256 hashes: 10 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-31 22:54 UTC.

Open this scan on URLScan 01a19427-f662-753c-a02a-bcaf2027d366 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    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-31 23:51:36.000000
    Evidence SHA-256
    2947ffbe6d222b43d45412f5fc7174d23ad2a0c2060a270e46eded508328385f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:51:36
    Evidence reason
  2. 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-31 23:51:36.000000
    Evidence SHA-256
    2947ffbe6d222b43d45412f5fc7174d23ad2a0c2060a270e46eded508328385f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:51:36
    Evidence reason

Threat Response Pipeline

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

Recorded events: 9. 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
    mofohoo.lovable.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 96
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 5/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Malware, Security threats
  • 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. Cloudflare Radar

    Phishing

    View source
  2. Added to PhishDestroy

    mofohoo.lovable.app

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    5/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

Check for cloaking

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

mofohoo.lovable.app

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious 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 mofohoo.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.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/mofohoo.lovable.app"
  title="PhishDestroy threat report for mofohoo.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>