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
lecoucou.info favicon

lecoucou.info

In short

PhishDestroy records the lecoucou.info category directory page showing nine French topic links and a ParkLogic copyright footer.

“Redirecting...”

Review the evidence
Registrar
United StatesNameSilo
Resolved IP
Australia162.4.84.247ParkLogic Pty Ltd · CDN
Registered
Sep 24, 2025
First observed
Oct 31, 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 ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 84
Page captures
6
open gallery
Domain age
402 days
registered 2025-09-24 according to WHOIS
OTX: 1 ref Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records the lecoucou.info category directory page showing nine French topic links and a ParkLogic copyright footer.

Critical
Status
Last known active
VirusTotal
14 / 92
Hosting
Australia162.4.84.247ParkLogic Pty Ltd · CDN
Registrar
United StatesNameSilo
Registered
Sep 24, 2025
OTX
1 community ref
Page captures
6
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured lecoucou.info page presents a category directory under the domain name, offering nine French-language topic links arranged in a grid, including Actualités et politique, Technologie et Informatique, Immobilier, Jeux Vidéo, and Musique et audio. The main interaction is selecting one of these category buttons, and the footer attributes copyright to ParkLogic.com with links to About Us, Contact Us, Privacy Policy, and Terms of Service. The HTML title "Redirecting..." differs from the visible directory content shown in the screenshot.

The stored VirusTotal domain result reports 14 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".

Source evidenceVirusTotal 14 / 92 · OTX 1 references 7 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
13
Suspicious
1
Undetected
32

Vendor labels

ESET
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Gridinsoft
suspicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    162.4.84.247
  • TTL, seconds
    300
    Type
    MX
    Value
    mail.eye-mail.net
    Priority
    10
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.parklogic.com
    Value
    ns1.ns306.parklogic.com
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 ip6:fdec:ae16:fda7::/48 -all
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.ns306.parklogic.com
  • TTL, seconds
    300
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.ns306.parklogic.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5

Certificate

Subject alternative names
  • lecoucou.info
Issuer
Let's Encrypt / YE1
Serial
64ebb0d4f75c9ed2ec2a2f996d5a16ccc3f
SHA-256
34cb7886487cec7f4a64ee9f1e5646c37909aa05ac802b6800457d15a6d7dfd0
Subject
lecoucou.info
Valid until
Valid from

Registry data (RDAP)

Status
  • renew period
  • client hold
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
NameSilo, LLC
Registrar IANA ID
1479
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 13,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2025-09-24T00:00:00Z
Updated
2025-09-24T00:00:00Z
First seen
2025-09-24T07:00:29Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "162.4.84.247"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mail.eye-mail.net",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.parklogic.com",
        "value": "ns1.ns306.parklogic.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 ip6:fdec:ae16:fda7::/48 -all"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.ns306.parklogic.com"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.ns306.parklogic.com"
    }
]
Dns at
2026-10-26T19:12:09Z
Jarm
27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5
Certificate
{
    "san": [
        "lecoucou.info"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "64ebb0d4f75c9ed2ec2a2f996d5a16ccc3f",
    "sha256": "34cb7886487cec7f4a64ee9f1e5646c37909aa05ac802b6800457d15a6d7dfd0",
    "subject": "lecoucou.info",
    "valid_to": "2026-12-24T05:20:11Z",
    "valid_from": "2026-09-25T05:20:12Z"
}
Registry data
{
    "status": [
        "renew period",
        "client hold"
    ],
    "events": {
        "last changed": "2026-10-24T23:40:22Z",
        "registration": "2025-09-24T00:00:00Z",
        "registrar expiration": "2026-09-24T00:00:00Z",
        "last update of RDAP database": "2026-10-26T19:12:08Z"
    },
    "registrar": "NameSilo, LLC",
    "registrar_iana_id": "1479"
}
Separate source record · 13 malicious + 1 suspicious / 92 · 2026-10-26 19:06:03 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-26T19:06:03Z
fetched_at
2026-10-31T00:16:23Z
stats
{"timeout":0,"harmless":46,"malicious":13,"suspicious":1,"undetected":32}

URLScan

Malicious · engine verdict · score 84

SHA-256 8603209bea06d2bbc8e0acc465dd4491b827fb5a7061a667356836f5832ea7ee

Open report
URLScanOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Report ID

019e8cfc-18ea-713b-b2dc-758a5b160b81

Final URL

https://lecoucou.info/

HTTP response

200

Redirect type

https-only

IP address

172.67.162.103

Contacted IP addresses

  • 172.67.162.103

Autonomous systems (ASN)

  • 13335

Document hash

e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

TLS session and certificate

Subject alternative names
  • lecoucou.info
  • *.lecoucou.info
Cipher
AES_128_GCM
Issuer
WE1
Subject
lecoucou.info
Protocol
QUIC
Valid until
Valid from

Domain age, days

252

Registered domain age, days

252

Certificate age, days

13

Certificate validity, days

90

Page requests

2

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
019e8cfc-18ea-713b-b2dc-758a5b160b81
Final url
https://lecoucou.info/
Status
200
Redirected
https-only
Ip
172.67.162.103
Contacted IP addresses
[
    "172.67.162.103"
]
Asns
[
    "13335"
]
Document hash
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Tls
{
    "san": [
        "lecoucou.info",
        "*.lecoucou.info"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "lecoucou.info",
    "protocol": "QUIC",
    "valid_to": "2026-08-18T21:55:25Z",
    "valid_from": "2026-05-20T20:55:29Z"
}
Domain age days
252
Apex age days
252
Tls age days
13
Tls valid days
90
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 84,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}
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
019e8cfc-18ea-713b-b2dc-758a5b160b81
score
0
malicious
false
result_at
2026-10-31T04:30:14Z
enriched_at
2026-10-31T09:10:59Z
source_timestamps
{"urlscan_result_at":"2026-10-31 05:30:14","urlscan_enriched_at":"2026-10-31 10:10:59"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

174a0c9d-96b2-4fa9-8b73-d05d607245f3

Final URL

https://lecoucou.info/

Navigation history

  • URL
    https://lecoucou.info/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    lecoucou.info
    Type
    A
    Value
    162.4.84.247

DNSSEC valid

No

Registration record

Registrar
NameSilo, LLC
Registered
Updated
Expires
Nameservers
  • ns2.ns306.parklogic.com
  • ns1.ns306.parklogic.com
Original source fields · JSON
Uuid
174a0c9d-96b2-4fa9-8b73-d05d607245f3
Final url
https://lecoucou.info/
History
[
    {
        "url": "https://lecoucou.info/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "lecoucou.info",
        "type": "A",
        "value": "162.4.84.247"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2025-09-24T07:24:59Z",
    "updated": "2026-10-25T06:40:22Z",
    "expires": "2027-09-24T07:24:59Z",
    "nameservers": [
        "ns2.ns306.parklogic.com",
        "ns1.ns306.parklogic.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

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
lecoucou.info category directory page with French topic links
ai_description
PhishDestroy records the lecoucou.info category directory page showing nine French topic links and a ParkLogic copyright footer.
ai_summary
The captured lecoucou.info page presents a category directory under the domain name, offering nine French-language topic links arranged in a grid, including Actualités et politique, Technologie et Informatique, Immobilier, Jeux Vidéo, and Musique et audio. The main interaction is selecting one of these category buttons, and the footer attributes copyright to ParkLogic.com with links to About Us, Contact Us, Privacy Policy, and Terms of Service. The HTML title "Redirecting..." differs from the visible directory content shown in the screenshot. The stored VirusTotal domain result reports 14 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 01:17:43
revision
a93292c618b84207b7080bbbfab0a7ffb1f9b6682a794a3ec5a921c6779d4e40
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: 13 fields

Mail configuration

MX records
  • mail.eye-mail.net
SPF record
v=spf1 ip6:fdec:ae16:fda7::/48 -all
SPF lookups
0

CAA records

Count
1
Domain
lecoucou.info
Allowed issuers
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Trackers

Requests
2

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.4.84.11
    Host
    ns1.ns306.parklogic.com
  • IP address
    162.4.84.12
    Host
    ns2.ns306.parklogic.com
DNS zone
lecoucou.info

Location

IP address
162.4.84.247
ASN
154653
Organization
ParkLogic Pty Ltd
Country
AU

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
lecoucou.info

DNS records

A
  • 162.4.84.247
MX
  • Mail server
    mail.eye-mail.net
    Priority
    10
NS
  • ns2.ns306.parklogic.com
  • ns1.ns306.parklogic.com
SOA
Primary nameserver
ns1.ns306.parklogic.com
Hostmaster
hostmaster.parklogic.com
Serial
1
Refresh, seconds
86400
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
300
TXT
  • v=spf1 ip6:fdec:ae16:fda7::/48 -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
162.4.84.247
IP version
4

Subdomains

Count
1
Subdomains
  • dev-api.lecoucou.info
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mail.eye-mail.net"
    ],
    "spf": "v=spf1 ip6:fdec:ae16:fda7::/48 -all",
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "lecoucou.info",
    "issuers": [
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Trackers
{
    "requests": 2
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.4.84.11",
            "host": "ns1.ns306.parklogic.com"
        },
        {
            "ip": "162.4.84.12",
            "host": "ns2.ns306.parklogic.com"
        }
    ],
    "zone": "lecoucou.info"
}
Location
{
    "ip": "162.4.84.247",
    "asn": "154653",
    "org": "ParkLogic Pty Ltd",
    "country": "AU"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "lecoucou.info"
}
DNS records
{
    "A": [
        "162.4.84.247"
    ],
    "MX": [
        "{\"exchange\": \"mail.eye-mail.net\", \"priority\": 10}"
    ],
    "NS": [
        "ns2.ns306.parklogic.com",
        "ns1.ns306.parklogic.com"
    ],
    "SOA": "{\"nsname\": \"ns1.ns306.parklogic.com\", \"hostmaster\": \"hostmaster.parklogic.com\", \"serial\": 1, \"refresh\": 86400, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 300}",
    "TXT": [
        "v=spf1 ip6:fdec:ae16:fda7::/48 -all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "162.4.84.247",
    "family": 4
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "dev-api.lecoucou.info"
    ]
}
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation

Questions about lecoucou.info

Is lecoucou.info legit?

PhishDestroy records the lecoucou.info category directory page showing nine French topic links and a ParkLogic copyright footer.

Is lecoucou.info safe to connect a wallet?

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

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

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

Checked, no match

Last checked

Stored Capture · 6 captures

URLScan · 2026-10-31 1 / 6 Used in the analysis Source file SHA-256: 51827576060709cc002b7a3b449c6c98530868c9bd592f9303376b47c00f0a30 SHA-256 of the prepared copy given to the model: ec279fe4c49f2a9ca486dd005dcde4f0ae352ab6093b8186c4e69c68b06a291e
SourceURLScan · 2026-10-31
Recorded
StateStored capture
Final URLhttps://lecoucou.info/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 84 report ↗
IP Context Australia162.4.84.247 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NameSilo US(US) PhishDestroy Investigation
Abuse contact["45e4e5b147cb0de7s@privacyguardian.org"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for lecoucou.info →
RegistrationCreated Sep 24, 2025 — Expires Sep 24, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant258ca18155e01fe645e4e5b147cb0de7s@privacyguardian.org VirusTotal WHOIS
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
Submitted URLhttp://lecoucou.info/
Favicon Hash
Observed page title
Redirecting...
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 53 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Australia162.4.84.247
Network ASN
AS154653
Organization
ParkLogic Pty Ltd
Observed location
AustraliaAU
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • ns2.ns306.parklogic.com
  • ns1.ns306.parklogic.com

SOA

  • nsname: ns1.ns306.parklogic.com
  • hostmaster: hostmaster.parklogic.com
  • serial: 1
  • refresh: 86400
  • retry: 7200
  • expire: 1209600
  • minttl: 300

Mail routing 1 MX record

  • mail.eye-mail.netpriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-25 05:20:12
Valid until
2026-12-24 05:20:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint34cb7886487cec7f4a64ee9f1e5646c37909aa05ac802b6800457d15a6d7dfd0
Certificate names · 1 SAN
  • lecoucou.info

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

viewdns.info · 162.4.84.247rapiddns.io

Latest Classified Outcome 2026-10-31 11:04:56 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 11:04:56 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:04:56 UTC last content: 2026-10-31 11:04:56 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • dev-api.lecoucou.infoDomain record
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
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of lecoucou.info · checked Oct 31, 2026

100
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
1.52 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.65 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://lecoucou.info/
Redirecting...
Response
HTTP 200
HTML body
5.5 KB
Compressed
2.7 KB
Links
0 internal · 0 external
Selected response headers
Server: openresty
Content-Type: text/html
Cache-Control: no-store, max-age=0
Content-Encoding: gzip
Security headers present
Permissions-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Accept-CH
Sec-CH-UA, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Full-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version, Sec-CH-UA-WoW64
Cache-Control
no-store, max-age=0
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sat, 31 Oct 2026 00:16:34 GMT
Permissions-Policy
ch-ua=(self "https://*.parklogic.com"), ch-ua-arch=(self "https://*.parklogic.com"), ch-ua-bitness=(self "https://*.parklogic.com"), ch-ua-full-version=(self "https://*.parklogic.com"), ch-ua-full-version-list=(self "https://*.parklogic.com"), ch-ua-mobile=(self "https://*.parklogic.com"), ch-ua-model=(self "https://*.
Server
openresty
Transfer-Encoding
chunked

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-31 00:17 UTC.

Open this scan on URLScan 019e8cfc-18ea-713b-b2dc-758a5b160b81 ↗

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. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations6

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

  1. current_http_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:56.000000
    Evidence SHA-256
    7f574911050a4467b14d22509071ccf910a32673d144d933ac338b2155fa68e0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:56
    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-31 12:04:56.000000
    Evidence SHA-256
    7f574911050a4467b14d22509071ccf910a32673d144d933ac338b2155fa68e0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:56
    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 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    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
    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-31 03:00:13.000000
    Evidence SHA-256
    c43e44fc0ebaa1477b9967b81c98c0627fe84e0ffcefe0ebf7398b0b33d8b06f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:00:13
    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 03:00:13.000000
    Evidence SHA-256
    c43e44fc0ebaa1477b9967b81c98c0627fe84e0ffcefe0ebf7398b0b33d8b06f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:00:13
    Evidence reason
    alive_content
  6. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:19:51.795542
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

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
    lecoucou.info detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Registrar Context: NameSilo · Forensic Evidence Collected Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 84
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 14/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
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. AlienVault OTX

    1 community references

    View source
  2. Added to PhishDestroy

    lecoucou.info

    View source
  3. VirusTotal

    14/92 engine detections

    View source
  4. URLScan

    Malicious · engine verdict · score 84

    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.

lecoucou.info

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 14 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 1 ref 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?

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

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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

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

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

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

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

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

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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

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

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

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