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

kiiaafse.lovable.app

In short

PhishDestroy records kiiaafse.lovable.app, a page asking visitors to confirm they are over 18 before continuing.

“Potwierdzenie wieku”

Registrar
Lovable Labs
Resolved IP
Sweden185.41.148.1Cloudflare, Inc. · CDN
Registered
May 6, 2023
First observed
Oct 30, 2026
PhishDestroy assessment Critical
84/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 8/92
VirusTotal
engine detections ·
Cloudflare Radar
Page captures
open gallery
Domain age
registered 2023-05-06 according to RDAP · source data differ
Oct 30, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records kiiaafse.lovable.app, a page asking visitors to confirm they are over 18 before continuing.

Critical
Status
Last known active
VirusTotal
8 / 92
Hosting
Sweden185.41.148.1Cloudflare, Inc. · CDN
Registrar
Lovable Labs
Registered
May 6, 2023
Page captures
6

PhishDestroy analysis, reviewed version

The captured page at kiiaafse.lovable.app presents an age-verification overlay titled "Potwierdzenie wieku" (Age confirmation). A centered dialog asks the visitor to confirm they are 18 or older, with a single orange "Potwierdź" (Confirm) button as the main interaction. Behind the overlay, a blurred Polish news-style headline about Monika Olejnik and the NBP president is visible, along with an author credit and timestamp, suggesting the gate sits in front of article content.

The stored VirusTotal domain result reports 8 detections out of 92 engines. DNS8 reported "suspicious"; G-Data reported "phishing".

Source evidenceVirusTotal 8 / 92 8 sources

VirusTotal

8 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
51
Malicious
6
Suspicious
2
Undetected
33

Vendor labels

DNS8
suspicious
G-Data
phishing
Sophos
phishing
PREBYTES
phishing
SOCRadar
phishing
Kaspersky
phishing
Gridinsoft
suspicious
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

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

Registrar

Namecheap Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    185.41.148.2
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a07:8240::1
  • TTL, seconds
    300
    Type
    A
    Value
    185.41.148.1
  • 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": 51,
    "malicious": 6,
    "suspicious": 2,
    "undetected": 33
}
Vendor labels
{
    "DNS8": "suspicious",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "PREBYTES": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
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-08T16:19:40Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "185.41.148.2"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::1"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.41.148.1"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::2"
    }
]
Dns at
2026-10-18T17:52:51Z
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 · 6 malicious + 2 suspicious / 92 · 2026-10-18 17:47:38 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-18T17:47:38Z
fetched_at
2026-10-30T21:19:14Z
stats
{"timeout":0,"harmless":51,"malicious":6,"suspicious":2,"undetected":33}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

e3c8aa32-6583-4560-b928-585c6b72dafb

Final URL

https://kiiaafse.lovable.app/

HTTP response

200

Navigation history

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

DOM structure hash

25e9ac69ab4db952673007c83a8c4cbae307b99f0c1e3537cf15762c6b06bb94

Document hash

318050536d3f05e2a2a1c945cb85305933036145dce36984f0c97a4425f9a058

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

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

DNSSEC valid

No

IP address

127.0.1.60

127.0.1.60 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
e3c8aa32-6583-4560-b928-585c6b72dafb
Final url
https://kiiaafse.lovable.app/
Status
200
History
[
    {
        "url": "https://kiiaafse.lovable.app/",
        "status": 200
    }
]
DOM structure hash
25e9ac69ab4db952673007c83a8c4cbae307b99f0c1e3537cf15762c6b06bb94
Document hash
318050536d3f05e2a2a1c945cb85305933036145dce36984f0c97a4425f9a058
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "kiiaafse.lovable.app",
        "type": "A",
        "value": "185.41.148.2"
    },
    {
        "name": "kiiaafse.lovable.app",
        "type": "A",
        "value": "185.41.148.1"
    },
    {
        "name": "kiiaafse.lovable.app",
        "type": "AAAA",
        "value": "2a07:8240::2"
    },
    {
        "name": "kiiaafse.lovable.app",
        "type": "AAAA",
        "value": "2a07:8240::1"
    }
]
Dnssec valid
false
Ip
127.0.1.60

127.0.1.60 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"
    ]
}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 d0e33023f01493b8b139a7f810a0bbd9d30cb2220364e0568be9da5ee007b7c5

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a18e90-669f-717e-9c62-6e7a3669bffc

Final URL

https://kiiaafse.lovable.app/

HTTP response

200

Redirect type

https-only

Redirects

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

IP address

185.41.148.2

Reverse DNS (PTR)

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

Contacted IP addresses

  • 185.41.148.2

Autonomous systems (ASN)

  • 13335

Server countries

  • SE

Linked domains

  • lovable.dev

Document hash

2445e144834d5e800acb0aa516eb34222dddefa30f0759f51ef6858f3c493d9d

Script hashes

  • e4814558b553d0d8c9d9bf8653c58311c032b37a228e574104831350bf6bbcc4
  • b9c6081cae72189a37293d01055981c615056bc1bbd3fd2400698aff095aa10d
  • 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

22

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

Registered domain age, days

22

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

Certificate age, days

19

Certificate validity, days

90

Page requests

13

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
01a18e90-669f-717e-9c62-6e7a3669bffc
Final url
https://kiiaafse.lovable.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://kiiaafse.lovable.app/",
        "from": "http://kiiaafse.lovable.app/",
        "status": 307
    }
]
Ip
185.41.148.2
Ptr
lovable-app-wd-2-4.p.l5e.io
Contacted IP addresses
[
    "185.41.148.2"
]
Asns
[
    "13335"
]
Countries
[
    "SE"
]
Linked domains
[
    "lovable.dev"
]
Document hash
2445e144834d5e800acb0aa516eb34222dddefa30f0759f51ef6858f3c493d9d
Script hashes
[
    "e4814558b553d0d8c9d9bf8653c58311c032b37a228e574104831350bf6bbcc4",
    "b9c6081cae72189a37293d01055981c615056bc1bbd3fd2400698aff095aa10d",
    "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
22

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

Apex age days
22

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

Tls age days
19
Tls valid days
90
Requests
13
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-31 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a18e90-669f-717e-9c62-6e7a3669bffc
score
0
malicious
false
result_at
2026-10-31T04:30:18Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-10-31 05:30:18","urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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-30T21:26:29Z

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-30T21:26:29Z
source_timestamp
2026-10-30 22:26:29
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
kiiaafse.lovable.app age confirmation page
ai_description
PhishDestroy records kiiaafse.lovable.app, a page asking visitors to confirm they are over 18 before continuing.
ai_summary
The captured page at kiiaafse.lovable.app presents an age-verification overlay titled "Potwierdzenie wieku" (Age confirmation). A centered dialog asks the visitor to confirm they are 18 or older, with a single orange "Potwierdź" (Confirm) button as the main interaction. Behind the overlay, a blurred Polish news-style headline about Monika Olejnik and the NBP president is visible, along with an author credit and timestamp, suggesting the gate sits in front of article content. The stored VirusTotal domain result reports 8 detections out of 92 engines. DNS8 reported "suspicious"; G-Data reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 22:22:28
revision
e41511b5922e1c6daeb2b1389316f94c8f36df8ef1278bf94922213512735d94
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: 25 fields

CAA records

Domain
kiiaafse.lovable.app

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.06
Average page size, bytes
7270

Crawler rules

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

Page title and metadata

Page title
Potwierdzenie wieku
Author
Lovable
Open Graph type
website
Open Graph image
https://pub-bb2e103a32db4e198524a2e9ed8f35b4.r2.dev/lovp_78hfhfg9q986h86m48a8bagpee/d9c6e62c771f2ebfa10963247eb8c8b2_1791380334063.png
Open Graph title
Potwierdzenie wieku
Description
Proszę potwierdzić, że masz ukończone 18 lat.
Twitter card
summary
Twitter account
@Lovable
Open Graph description
Proszę potwierdzić, że masz ukończone 18 lat.

Trackers

Requests
10

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
20
Waiting
479
Connection
13
Download
1
Response time, ms
515

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

DNS servers

Nameservers
  • IP address
    173.245.59.120
    Host
    ivan.ns.cloudflare.com
  • IP address
    173.245.58.216
    Host
    rafe.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::1
ASN
13335
Organization
Cloudflare, Inc.
City
Stockholm
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::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://kiiaafse.lovable.app

Social profiles

Profiles
  • https://x.com/Lovable

Page links

External link addresses
  • https://lovable.dev/projects/lovp_78hfhfg9q986h86m48a8bagpee
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": "kiiaafse.lovable.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-30T20:42:40Z",
    "first": "2026-10-13T14:00:26Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.06,
    "avg_page_bytes": 7270
}
Crawler rules
{
    "agents": [
        "Googlebot",
        "Bingbot",
        "Twitterbot",
        "facebookexternalhit",
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Potwierdzenie wieku",
    "author": "Lovable",
    "ogType": "website",
    "ogImage": "https://pub-bb2e103a32db4e198524a2e9ed8f35b4.r2.dev/lovp_78hfhfg9q986h86m48a8bagpee/d9c6e62c771f2ebfa10963247eb8c8b2_1791380334063.png",
    "ogTitle": "Potwierdzenie wieku",
    "description": "Proszę potwierdzić, że masz ukończone 18 lat.",
    "twitterCard": "summary",
    "twitterSite": "@Lovable",
    "ogDescription": "Proszę potwierdzić, że masz ukończone 18 lat."
}
Trackers
{
    "requests": 10
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 20,
        "wait": 479,
        "connect": 13,
        "download": 1
    },
    "response_ms": 515
}
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": 14409,
    "co2_grams": 0.0005,
    "cleaner_than": 64
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.59.120",
            "host": "ivan.ns.cloudflare.com"
        },
        {
            "ip": "173.245.58.216",
            "host": "rafe.ns.cloudflare.com"
        }
    ],
    "zone": "lovable.app"
}
Cookies
{
    "cookies": [
        {
            "name": "__dpl",
            "secure": true,
            "same_site": "Lax"
        },
        {
            "name": "session-id",
            "secure": true
        }
    ]
}
Location
{
    "ip": "2a07:8240::1",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Stockholm",
    "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::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://kiiaafse.lovable.app"
    ]
}
Social profiles
{
    "profiles": [
        "https://x.com/Lovable"
    ]
}
Page links
{
    "external": [
        "https://lovable.dev/projects/lovp_78hfhfg9q986h86m48a8bagpee"
    ],
    "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

Questions about kiiaafse.lovable.app

Is kiiaafse.lovable.app legit?

PhishDestroy records kiiaafse.lovable.app, a page asking visitors to confirm they are over 18 before continuing.

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

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

Last checked

Stored Capture · 6 captures

All capture links and hashes (6)
Observed page title
Potwierdzenie wieku
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 69 days
kiiaafse.lovable.app: caution — 8/92 VirusTotal engines. PhishDestroy risk score 84/100 (critical).
Social preview card kiiaafse.lovable.app: caution — 8/92 VirusTotal engines. PhishDestroy risk score 84/100 (critical). v 8689fb7269e3

Domain details

Domain
URLScan verdict Analysis completed score 0 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
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 30, 2026
DOM Analysisanalyzed Oct 30, 2026score 0/100
Submitted URLhttp://kiiaafse.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.

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.

Latest Classified Outcome 2026-10-31 23:04:32 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 23:04:32 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:04:32 UTC last content: 2026-10-31 23:04:32 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
DNS8
G-Data
Gridinsoft
Kaspersky
PREBYTES
SOCRadar
Sophos

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

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

99
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
2.75 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://kiiaafse.lovable.app/
Final URL: https://kiiaafse.lovable.app/
Potwierdzenie wieku
Proszę potwierdzić, że masz ukończone 18 lat.
Response
HTTP 200
HTML body
14.1 KB
Compressed
5.9 KB
Links
0 internal · 1 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache, must-revalidate, max-age=0
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
Open Graph title: Potwierdzenie wieku
Open Graph description: Proszę potwierdzić, że masz ukończone 18 lat.
Twitter card: summary
Saved response-header values · 12
Cache-Control
no-cache, must-revalidate, max-age=0
CF-RAY
a52d40b51c444cc4-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 30 Oct 2026 20:43:32 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-deployment-id
psr2.356d3231-7df6-4b91-8476-fbdfe1611a63.1793997812.XaxTFZVd6AbyjWMye63i0Gz95M4j2Ya2dJ0LppGMbS0

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

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: 13 SHA-256 hashes: 13 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-30 20:48 UTC.

Open this scan on URLScan 01a18e90-669f-717e-9c62-6e7a3669bffc ↗

Stored observation history3

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Domain monitor · First collection record

    Reachable

All retained availability observations10

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

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:32.000000
    Evidence SHA-256
    48fc71a9d71dc133f7fda7c8e9012d3a894da9f456dc4dc3275691fd650ac19a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:32
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:04:32.000000
    Evidence SHA-256
    48fc71a9d71dc133f7fda7c8e9012d3a894da9f456dc4dc3275691fd650ac19a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:32
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:04:51.000000
    Evidence SHA-256
    05a90570ad38aa0d4ae1a1d898de9e2b1e0b6b3fdb8eb1e7a282073661af0a69
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:51
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:04:51.000000
    Evidence SHA-256
    05a90570ad38aa0d4ae1a1d898de9e2b1e0b6b3fdb8eb1e7a282073661af0a69
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:51
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:12:29.000000
    Evidence SHA-256
    52c8c41d2c2f65f0a00c063211d2a38faa14fdc5af63b09a3109b3b139bcfd4f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 01:12:29
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:12:29.000000
    Evidence SHA-256
    52c8c41d2c2f65f0a00c063211d2a38faa14fdc5af63b09a3109b3b139bcfd4f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 01:12:29
    Evidence reason
    alive_content
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  9. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 21:48:32.000000
    Evidence SHA-256
    0751e2448e3f55b49dccd84e55623d419d9210ccb5b679a4abc1be2aa552fe7e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 21:48:32
    Evidence reason
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 21:48:32.000000
    Evidence SHA-256
    0751e2448e3f55b49dccd84e55623d419d9210ccb5b679a4abc1be2aa552fe7e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 21:48:32
    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
    kiiaafse.lovable.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 8/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

5 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Added to PhishDestroy

    kiiaafse.lovable.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source
  5. VirusTotal

    8/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.

Check for cloaking

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

kiiaafse.lovable.app

Evidence & External Reports

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.

Official reporting routes

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.

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

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.

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