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

dirapoupro.lovable.app

In short

dirapoupro.lovable.app is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Lovable Labs. Status: Last known active. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. VirusTotal: 14/92 engines flag it. Do not enter credentials or connect a wallet.

“Potwierdzenie wieku | Gazeta”

Review the evidence
Registrar
Lovable Labs
Resolved IP
Sweden185.41.148.1Cloudflare, Inc. · CDN
Registered
May 6, 2023
First observed
Oct 25, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 14/92
VirusTotal
14 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 95
Page captures
5
open gallery
Domain age
1,270 days
Oct 25, 2026 CDN
X Telegram API

Questions about dirapoupro.lovable.app

Is dirapoupro.lovable.app legit?

No. PhishDestroy classifies dirapoupro.lovable.app as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 14/92 engines flag it. Treat the site as unsafe.

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

No. Do not connect a wallet, sign messages or approve tokens on dirapoupro.lovable.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used dirapoupro.lovable.app?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 14 / 92 6 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
11
Suspicious
3
Undetected
32

Vendor labels

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

Reputation score

0

Registrar

Namecheap Inc.

Created

Expires

Updated

First seen

DNS records

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

DNS records observed

JARM fingerprint

27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

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

Registration record

Registrar
Namecheap Inc.
Registrar IANA ID
1068
Registrar URL
https://www.namecheap.com/
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ivan.ns.cloudflare.com
  • rafe.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 11,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Namecheap Inc.
Created
2023-05-06T14:03:05Z
Expires
2028-05-06T14:03:05Z
Updated
2025-02-10T14:47:24Z
First seen
2026-09-04T21:06:33Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "185.41.148.1"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.41.148.2"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::2"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a07:8240::1"
    }
]
Dns at
2026-10-21T13:03:58Z
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 · 11 malicious + 3 suspicious / 92 · 2026-10-21 12:58:37 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-21T12:58:37Z
fetched_at
2026-10-25T09:18:44Z
stats
{"timeout":0,"harmless":46,"malicious":11,"suspicious":3,"undetected":32}

URLScan

Malicious · engine verdict · score 95

SHA-256 720cc780cf0776e04bf5074bb4701c09eee897c9cf0ea4ae51493c8a68e52ddc

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a17233-b661-7774-aa69-47fc79f0641f

Final URL

https://dirapoupro.lovable.app/

HTTP response

200

Redirect type

https-only

Redirects

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

IP address

185.41.148.1

Reverse DNS (PTR)

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

Contacted IP addresses

  • 185.41.148.1

Autonomous systems (ASN)

  • 13335

Server countries

  • SE

Linked domains

  • lovable.dev

Document hash

b66dfbdcd667f88aa5d1e23567ed39f486543425e0b3e9e4f6506618ea36d667

Script hashes

  • 547700884c3d41809f4145b17bf3b2d08bbf9b3e0bc7004cfe5de3c2f9240541
  • 53cfa1d3ea2a9ea3edc674079e8452490e62b13377dda5e3dda5731fd84a6071
  • a86e084b4f82709814be6c15fd6305daa783fda87ad95402da9a4d3a1dd6d748
  • cbb3e1e38a0e20bdbe4c49fe9aaa30767732e9155191806ec5936e35a51c5035

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

50

Registered domain age, days

50

Certificate age, days

14

Certificate validity, days

90

Page requests

13

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
95
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
01a17233-b661-7774-aa69-47fc79f0641f
Final url
https://dirapoupro.lovable.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://dirapoupro.lovable.app/",
        "from": "http://dirapoupro.lovable.app/",
        "status": 307
    }
]
Ip
185.41.148.1
Ptr
lovable-app-wd-1-4.p.l5e.io
Contacted IP addresses
[
    "185.41.148.1"
]
Asns
[
    "13335"
]
Countries
[
    "SE"
]
Linked domains
[
    "lovable.dev"
]
Document hash
b66dfbdcd667f88aa5d1e23567ed39f486543425e0b3e9e4f6506618ea36d667
Script hashes
[
    "547700884c3d41809f4145b17bf3b2d08bbf9b3e0bc7004cfe5de3c2f9240541",
    "53cfa1d3ea2a9ea3edc674079e8452490e62b13377dda5e3dda5731fd84a6071",
    "a86e084b4f82709814be6c15fd6305daa783fda87ad95402da9a4d3a1dd6d748",
    "cbb3e1e38a0e20bdbe4c49fe9aaa30767732e9155191806ec5936e35a51c5035"
]
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
50
Apex age days
50
Tls age days
14
Tls valid days
90
Requests
13
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 95,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Separate monitor record · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17233-b661-7774-aa69-47fc79f0641f
score
0
malicious
false
result_at
2026-10-26T04:30:31Z
enriched_at
2026-10-25T09:10:45Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:31","urlscan_enriched_at":"2026-10-25 10:10:45"}
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

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

Open report
Separate monitor score · 0 / 100 · 2026-10-25T11:20:15Z

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-25T11:20:15Z
source_timestamp
2026-10-25 12:20:15
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

Collected source details

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

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

CAA records

Domain
dirapoupro.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.11
Average page size, bytes
7326

Crawler rules

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

Page title and metadata

Page title
Potwierdzenie wieku | Gazeta
Author
Lovable
Open Graph type
website
Indexing directives
noindex, nofollow
Open Graph image
https://pub-bb2e103a32db4e198524a2e9ed8f35b4.r2.dev/f8b31e7ffdc54874b6afa54d6281919b/id-preview-ae42daf0--543030c2-4243-4f57-8f24-0be7ccd55293.lovable.app-1788344802296.png
Open Graph title
Potwierdzenie wieku
Description
Potwierdź, że masz ukończone 18 lat, aby przejść do treści serwisu.
Twitter card
summary_large_image
Twitter account
@Lovable
Open Graph description
Potwierdź swój wiek, aby kontynuować.

Trackers

Requests
9

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
25
TLS
16
Waiting
279
Connection
6
Download
1
Response time, ms
327

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
14307
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::2
IP version
6

Redirects

Redirect chain
  • https://dirapoupro.lovable.app

Social profiles

Profiles
  • https://x.com/Lovable

Page links

External link addresses
  • https://lovable.dev/projects/lovp_5f7r4wat179r8t8txz04ma36m8
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": "dirapoupro.lovable.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T08:27:31Z",
    "first": "2026-10-16T03:05:02Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.11,
    "avg_page_bytes": 7326
}
Crawler rules
{
    "agents": [
        "Googlebot",
        "Bingbot",
        "Twitterbot",
        "facebookexternalhit",
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Potwierdzenie wieku | Gazeta",
    "author": "Lovable",
    "ogType": "website",
    "robots": "noindex, nofollow",
    "ogImage": "https://pub-bb2e103a32db4e198524a2e9ed8f35b4.r2.dev/f8b31e7ffdc54874b6afa54d6281919b/id-preview-ae42daf0--543030c2-4243-4f57-8f24-0be7ccd55293.lovable.app-1788344802296.png",
    "ogTitle": "Potwierdzenie wieku",
    "description": "Potwierdź, że masz ukończone 18 lat, aby przejść do treści serwisu.",
    "twitterCard": "summary_large_image",
    "twitterSite": "@Lovable",
    "ogDescription": "Potwierdź swój wiek, aby kontynuować."
}
Trackers
{
    "requests": 9
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 25,
        "tls": 16,
        "wait": 279,
        "connect": 6,
        "download": 1
    },
    "response_ms": 327
}
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": 14307,
    "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::2",
    "family": 6
}
Redirects
{
    "chain": [
        "https://dirapoupro.lovable.app"
    ]
}
Social profiles
{
    "profiles": [
        "https://x.com/Lovable"
    ]
}
Page links
{
    "external": [
        "https://lovable.dev/projects/lovp_5f7r4wat179r8t8txz04ma36m8"
    ],
    "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"
    }
}
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://dirapoupro.lovable.app/
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)
Observed page title
Potwierdzenie wieku | Gazeta
TLS Certificate
Issued by WE1 · stored validity ends in 73 days
dirapoupro.lovable.app: caution — 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card dirapoupro.lovable.app: caution — 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v a738d17c6e0e

Domain details

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

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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

Accreditation is a contract, not a safety certification.

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

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

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-10-10 23:33:33
Valid until
2027-01-09 00:33:27
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbfd87661dd48f66569436bba3b43026fcf7c54c23ec933e58b748a6db8a5899f
Certificate names · 2 SANs
  • lovable.app
  • *.lovable.app

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 185.41.148.1rapiddns.io

Latest Classified Outcome 2026-10-27 11:02:48 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-27 11:02:48 UTC
RDAP registration
Observed timeline last reachable: 2026-10-26 00:19:21 UTC last content: 2026-10-26 00:19:21 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://dirapoupro.lovable.app/
Final URL: https://dirapoupro.lovable.app/
Potwierdzenie wieku | Gazeta
Potwierdź, że masz ukończone 18 lat, aby przejść do treści serwisu.
Response
HTTP 200
HTML body
14.0 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: Potwierdź swój wiek, aby kontynuować.
Twitter card: summary_large_image
Saved response-header values · 12
Cache-Control
no-cache, must-revalidate, max-age=0
CF-RAY
a4ffd779fca1f187-GRU
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 08:27:23 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.a1225949-7628-413f-9d13-78d84747f475.1793521642.leJHdc-erCubiOknL5ll-yd1r2e7C4UlC2sdvjNRUGo

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history2

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability 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
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:48.000000
    Evidence SHA-256
    042522cc5059d6c1cc1ba7f2777d333ef5f99bd822f0e4d4035e001a5abec9b9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:48
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:48.000000
    Evidence SHA-256
    042522cc5059d6c1cc1ba7f2777d333ef5f99bd822f0e4d4035e001a5abec9b9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:48
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:21.000000
    Evidence SHA-256
    43e8f35fc565e71b06909773d1dcf7dfcac639a17e802a85600d8b7be787ab63
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:21
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:21.000000
    Evidence SHA-256
    43e8f35fc565e71b06909773d1dcf7dfcac639a17e802a85600d8b7be787ab63
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:21
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:21.000000
    Evidence SHA-256
    49c544f1a297b12da16942d9042a0ba833c25ea9c23daac0675b3b4a4d70a700
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:21
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:21.000000
    Evidence SHA-256
    49c544f1a297b12da16942d9042a0ba833c25ea9c23daac0675b3b4a4d70a700
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:21
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:23:04.000000
    Evidence SHA-256
    b1febcefe4c5cb895212376269ebf99bc63e6a40aeacd7821e7dede5ca0f0814
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:23:04
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:23:04.000000
    Evidence SHA-256
    b1febcefe4c5cb895212376269ebf99bc63e6a40aeacd7821e7dede5ca0f0814
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:23:04
    Evidence reason
    alive_content
  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-25 09:37:55.000000
    Evidence SHA-256
    5b865779ee6465edecf713102c81ce393425a5357ed362b4da235d0c684349e0
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:37:55
    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-25 09:37:55.000000
    Evidence SHA-256
    5b865779ee6465edecf713102c81ce393425a5357ed362b4da235d0c684349e0
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:37:55
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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
    dirapoupro.lovable.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 95
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 14/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. VirusTotal

    14/92 engine detections

    View source
  2. Added to PhishDestroy

    dirapoupro.lovable.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

dirapoupro.lovable.app

Evidence & External Reports

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

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

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

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

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

What information should I collect for my report?

FBI guidelines

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

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including dirapoupro.lovable.app)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

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

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

Embed This Report

Share this threat intelligence on your website or blog

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