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

l-mint.com

In short

PhishDestroy describes l-mint.com, where the captured page shows a browser connection reset error instead of site content.

“Redirecting...”

Registrar
Realtime
Resolved IP
United States162.4.84.255ParkLogic Pty Ltd
Registered
Oct 22, 2025
First observed
Oct 30, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 16/92
VirusTotal
engine detections ·
OTX
community references
Page captures
open gallery
Domain age
registered 2025-10-22 according to WHOIS · source data differ
OTX: 1 ref Oct 30, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy describes l-mint.com, where the captured page shows a browser connection reset error instead of site content.

Critical
Status
Last known active
VirusTotal
16 / 92
Hosting
United States162.4.84.255ParkLogic Pty Ltd
Registrar
Realtime
Registered
Oct 22, 2025
OTX
1 community ref
Page captures
5

PhishDestroy analysis, reviewed version

The captured page for l-mint.com is a browser error screen rather than the site itself, reporting "This site can't be reached" with the message that the connection was reset under the code ERR_CONNECTION_RESET. It suggests checking the connection and the proxy and the firewall, and offers Details and Reload buttons as the only interactions. The HTML title reads "Redirecting...", which conflicts with what the screenshot shows.

The stored VirusTotal domain result reports 16 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 16 / 92 · OTX 1 references 8 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
13
Suspicious
3
Undetected
30

Vendor labels

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

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.parklogic.com
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.parklogic.com
  • TTL, seconds
    300
    Type
    A
    Value
    162.4.84.255
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.parklogic.com
    Value
    ns1.parklogic.com
  • TTL, seconds
    300
    Type
    MX
    Value
    mx156.hostedmxserver.com
    Priority
    10
  • TTL, seconds
    300
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 -all

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5

Certificate

Subject alternative names
  • l-mint.com
Issuer
Let's Encrypt / YE1
Serial
6e687757520c1df5acfff7de2d6077f3013
SHA-256
3398057a30499f0ab4e2df48fffe8de76ce187ef78811af45db500fa56e976e1
Subject
l-mint.com
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
  • add period
  • pending delete
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
REALTIME REGISTER B.V.
Registrar IANA ID
839
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2025-10-22T00:00:00Z
Updated
2025-10-22T00:00:00Z
First seen
2024-03-07T08:03:32Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.parklogic.com"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.parklogic.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "162.4.84.255"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.parklogic.com",
        "value": "ns1.parklogic.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx156.hostedmxserver.com",
        "priority": 10
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 -all"
    }
]
Dns at
2026-10-30T09:25:09Z
Jarm
27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5
Certificate
{
    "san": [
        "l-mint.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6e687757520c1df5acfff7de2d6077f3013",
    "sha256": "3398057a30499f0ab4e2df48fffe8de76ce187ef78811af45db500fa56e976e1",
    "subject": "l-mint.com",
    "valid_to": "2027-01-20T09:11:06Z",
    "valid_from": "2026-10-22T09:11:07Z"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "add period",
        "pending delete"
    ],
    "events": {
        "expiration": "2026-10-22T09:18:29Z",
        "last changed": "2026-10-22T09:30:15Z",
        "registration": "2025-10-22T09:18:29Z",
        "registrar expiration": "2026-10-22T09:18:29Z",
        "last update of RDAP database": "2026-10-30T09:25:09Z"
    },
    "registrar": "REALTIME REGISTER B.V.",
    "registrar_iana_id": "839"
}
Separate source record · 13 malicious + 3 suspicious / 92 · 2026-10-30 09:11:40 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-30T09:11:40Z
fetched_at
2026-10-30T22:23:13Z
stats
{"timeout":0,"harmless":46,"malicious":13,"suspicious":3,"undetected":30}

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

666fa916-f3a9-4c95-99ff-fea9f2a42b2e

Final URL

https://l-mint.com/

Navigation history

  • URL
    https://l-mint.com/
    Status
    0

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    l-mint.com
    Type
    A
    Value
    162.4.84.255

DNSSEC valid

No

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Nameservers
  • ns1.rr585.parklogic.com
  • ns2.rr585.parklogic.com
Original source fields · JSON
Uuid
666fa916-f3a9-4c95-99ff-fea9f2a42b2e
Final url
https://l-mint.com/
History
[
    {
        "url": "https://l-mint.com/",
        "status": 0
    }
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "l-mint.com",
        "type": "A",
        "value": "162.4.84.255"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2025-10-22T09:18:29Z",
    "updated": "2026-10-23T08:11:43Z",
    "expires": "2027-10-22T09:18:29Z",
    "nameservers": [
        "ns1.rr585.parklogic.com",
        "ns2.rr585.parklogic.com"
    ]
}

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 0b5ee82b190cdf8f9894710c08636e51a056097282ab0703c7dd55fe58f46b78

Open report
URLScanOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

01a06f5a-e373-70dd-be7d-678d6ee81dbe

Final URL

http://www.l-mint.com/

Redirects

  • To
    https://www.l-mint.com/
    From
    http://www.l-mint.com/
    Status
    307
  • To
    http://www.l-mint.com/
    From
    https://www.l-mint.com/
    Status
    307

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

876

Differs from the registration date in WHOIS (2025-10-22), which gives 317 days on the scan date 2026-09-05. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1298

Differs from the registration date in WHOIS (2025-10-22), which gives 317 days on the scan date 2026-09-05. The two sources disagree; both values are kept as recorded.

Page requests

5

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
-34
Malicious
No
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
01a06f5a-e373-70dd-be7d-678d6ee81dbe
Final url
http://www.l-mint.com/
Redirects
[
    {
        "to": "https://www.l-mint.com/",
        "from": "http://www.l-mint.com/",
        "status": 307
    },
    {
        "to": "http://www.l-mint.com/",
        "from": "https://www.l-mint.com/",
        "status": 307
    }
]
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
876

Differs from the registration date in WHOIS (2025-10-22), which gives 317 days on the scan date 2026-09-05. The two sources disagree; both values are kept as recorded.

Apex age days
1298

Differs from the registration date in WHOIS (2025-10-22), which gives 317 days on the scan date 2026-09-05. The two sources disagree; both values are kept as recorded.

Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -34,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
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
01a06f5a-e373-70dd-be7d-678d6ee81dbe
score
0
malicious
false
result_at
2026-10-31T04:30:16Z
enriched_at
null
source_timestamps
{"urlscan_result_at":"2026-10-31 05:30:16","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-30T22:38:03Z

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-30T22:38:03Z
source_timestamp
2026-10-30 23:38:03
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
l-mint.com connection reset error page capture
ai_description
PhishDestroy describes l-mint.com, where the captured page shows a browser connection reset error instead of site content.
ai_summary
The captured page for l-mint.com is a browser error screen rather than the site itself, reporting "This site can't be reached" with the message that the connection was reset under the code ERR_CONNECTION_RESET. It suggests checking the connection and the proxy and the firewall, and offers Details and Reload buttons as the only interactions. The HTML title reads "Redirecting...", which conflicts with what the screenshot shows. The stored VirusTotal domain result reports 16 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 23:28:02
revision
43099b79050df17a2d0b28c092a0d261c8887cdd7e5be0c4f43723f2d8ba5b9e
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: 14 fields

Mail configuration

MX records
  • mx156.hostedmxserver.com
SPF record
v=spf1 -all
SPF lookups
0

CAA records

Count
1
Domain
l-mint.com
Allowed issuers
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
50
Archived days
66
Snapshots per day
0.01
Average page size, bytes
4208

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.45
    Host
    ns1.parklogic.com
  • IP address
    162.4.84.46
    Host
    ns2.parklogic.com
DNS zone
l-mint.com

Location

IP address
162.4.84.255
ASN
154653
Organization
ParkLogic Pty Ltd
City
Los Angeles
Country
US

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
l-mint.com

DNS records

A
  • 162.4.84.255
MX
  • Mail server
    mx156.hostedmxserver.com
    Priority
    10
NS
  • ns2.parklogic.com
  • ns1.parklogic.com
SOA
Primary nameserver
ns1.parklogic.com
Hostmaster
hostmaster.parklogic.com
Serial
1
Refresh, seconds
86400
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
300
TXT
  • v=spf1 -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
162.4.84.255
IP version
4

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.rr585.parklogic.com
  • ns2.rr585.parklogic.com
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mx156.hostedmxserver.com"
    ],
    "spf": "v=spf1 -all",
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "l-mint.com",
    "issuers": [
        "letsencrypt.org"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2025-03-06T15:32:57Z",
    "first": "2003-04-30T02:28:31Z",
    "changes": 50,
    "days_archived": 66,
    "scans_per_day": 0.01,
    "avg_page_bytes": 4208
}
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.45",
            "host": "ns1.parklogic.com"
        },
        {
            "ip": "162.4.84.46",
            "host": "ns2.parklogic.com"
        }
    ],
    "zone": "l-mint.com"
}
Location
{
    "ip": "162.4.84.255",
    "asn": "154653",
    "org": "ParkLogic Pty Ltd",
    "city": "Los Angeles",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "l-mint.com"
}
DNS records
{
    "A": [
        "162.4.84.255"
    ],
    "MX": [
        "{\"exchange\": \"mx156.hostedmxserver.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns2.parklogic.com",
        "ns1.parklogic.com"
    ],
    "SOA": "{\"nsname\": \"ns1.parklogic.com\", \"hostmaster\": \"hostmaster.parklogic.com\", \"serial\": 1, \"refresh\": 86400, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 300}",
    "TXT": [
        "v=spf1 -all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "162.4.84.255",
    "family": 4
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2025-10-22T09:18:29Z",
    "updated": "2026-10-23T08:11:43Z",
    "expires": "2027-10-22T09:18:29Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.rr585.parklogic.com",
        "ns2.rr585.parklogic.com"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware

Questions about l-mint.com

Is l-mint.com legit?

PhishDestroy describes l-mint.com, where the captured page shows a browser connection reset error instead of site content.

Is l-mint.com safe to connect a wallet?

This report does not record which wallet requests l-mint.com 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 l-mint.com?

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 · 5 captures

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation United States162.4.84.255 abuse score 0/100 0 reports checked Oct 31, 2026
Registrar Realtime
RegistrationCreated Oct 22, 2025 — Expires Oct 22, 2027
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://l-mint.com/
Favicon Hash
Observed page title
Redirecting...
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 80 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States162.4.84.255
Network ASN
AS154653
Organization
ParkLogic Pty Ltd
Observed location
United StatesLos Angeles, US
Server header
openresty

Nameservers 2

  • ns1.rr585.parklogic.com
  • ns2.rr585.parklogic.com

SOA

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

Mail routing 1 MX record

  • mx156.hostedmxserver.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-22 09:11:07
Valid until
2027-01-20 09:11:06
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3398057a30499f0ab4e2df48fffe8de76ce187ef78811af45db500fa56e976e1
Certificate names · 1 SAN
  • l-mint.com

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 11:05:03 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:05:03 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:05:03 UTC last content: 2026-10-31 11:05:03 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 subdomains8

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

  • adult.l-mint.comDomain record
  • autodiscover.l-mint.comDomain record
  • cpanel.l-mint.comDomain record
  • cpcalendars.l-mint.comDomain record
  • cpcontacts.l-mint.comDomain record
  • webdisk.l-mint.comDomain record
  • webmail.l-mint.comDomain record
  • www.l-mint.comDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 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
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of l-mint.com · checked Oct 30, 2026

97
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
2.59 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.62 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://l-mint.com/
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
Fri, 30 Oct 2026 22:10:28 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.

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: 5 SHA-256 hashes: 3 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 22:24 UTC.

Open this scan on URLScan 01a06f5a-e373-70dd-be7d-678d6ee81dbe ↗

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:05:03.000000
    Evidence SHA-256
    0e856ecf88e86e54cf3b26974fb23bc697960674db9e17bd1c5e0de0eaa129c2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:05:03
    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:05:03.000000
    Evidence SHA-256
    0e856ecf88e86e54cf3b26974fb23bc697960674db9e17bd1c5e0de0eaa129c2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:05:03
    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:25:39.000000
    Evidence SHA-256
    d4dcba3822db121c3fe534245058625102ffe136d8708f0a7820666ab3e14739
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:25:39
    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:25:39.000000
    Evidence SHA-256
    d4dcba3822db121c3fe534245058625102ffe136d8708f0a7820666ab3e14739
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:25:39
    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-30 23:26:26.621782
    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
    l-mint.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · OTX Community References · 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.
  • VirusTotal
    Detections recorded on VirusTotal: 16/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • 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

3 entries
  1. AlienVault OTX

    1 community references

    View source
  2. Added to PhishDestroy

    l-mint.com

    View source
  3. VirusTotal

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

l-mint.com

Evidence & External Reports

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.

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 l-mint.com)
  • 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/l-mint.com"
  title="PhishDestroy threat report for l-mint.com"
  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>