Skip to security report
Domain security and threat intelligence
lrservice.com.ua favicon

lrservice.com.ua

In short

lrservice.com.ua is a Telegram impersonation page detected by PhishDestroy on 2026-10-12. Risk: critical (88/100). Registrar: Internet Invest. Status: Last known active. Hosting: Hetzner Online GmbH. VirusTotal: 6/92 engines flag it. Do not enter credentials or connect a wallet.

“Сторінку не знайдено – Land Rover «Автолайф Центр» офіційний сервіс Ленд Ровер у Києві”

Registrar
Internet Invest
Resolved IP
77.42.5.121
Registered
Mar 9, 2017
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 6/92 Automated brand label: Telegram
OTX: 31 refs Oct 12, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 6 / 92 · OTX 31 references 5 sources

VirusTotal

6 / 92 engine detections

Open report

OTX

31 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
6 / 92
OTX
31 community refs
Page captures
6

PhishDestroy threat report

Overview

lrservice.com.ua is an impersonation phishing site that presents itself as «Автолайф Центр», an official Land Rover service centre in Kyiv. Its audience is Land Rover owners in Ukraine looking for authorised maintenance, repairs or parts. PhishDestroy first flagged the domain on 2026-10-12. As of 2026-10-19 it was still online and serving content.

How the scam works

The page title reads, in Ukrainian, "Page not found – Land Rover «Автолайф Центр» official Land Rover service in Kyiv." A browser tab with that title looks like a genuine dealer site that has a broken link. We classified the domain as an impersonation phishing page. Sites that borrow a dealer's identity usually collect names, phone numbers, vehicle details and VIN codes through booking forms. They may also ask for prepayments or deposits for service slots or parts that never arrive. Victims can lose that money, and the contact details they enter can feed follow-up scam calls that cite their car and booking.

Evidence

On 2026-10-16, 6 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Gridinsoft, Seclookup, SOCRadar, URLQuery and VIPRE. That is a minority of engines, so many security products will not warn visitors yet. Still, six independent vendors reached the same conclusion. The domain also appears in 31 AlienVault OTX threat pulses, which shows that other researchers are tracking it. PhishDestroy is currently the only blocklist that lists it.

Infrastructure

The domain was registered on 2017-03-09 through Internet Invest LLC, more than nine years before PhishDestroy flagged it. That age makes it look more trustworthy than a freshly registered lookalike. The site runs on Hetzner Online GmbH servers in Finland, not on Ukrainian hosting, even though it claims to be a Kyiv service centre. Its certificate is a standard Let's Encrypt one. The padlock in the browser therefore says nothing about who operates the site.

What to do

If you paid a deposit or prepayment through this site, contact your bank or card issuer immediately and dispute the charge. If you entered your phone number, VIN or address, treat any calls or messages about your booking as suspicious. Do not make further payments. Confirm appointments only through a dealer you find via Land Rover Ukraine's official channels, and report the incident to the cyber police. Defenders should block the domain at DNS and proxy level and add it to mail filters. Watch for lures aimed at car owners that reference Land Rover servicing in Kyiv.

Collected source details

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

URLScan · 2026-09-09T19:44:31Z

Observed: · Retrieved:

Uuid
01a087b3-3465-76cb-8e07-dd57709ca2f4
Final url
https://lrservice.com.ua/wp-includes/Southwire/KCY5735683679/Corporation/En/Outstanding-Invoices
Status
404
Redirected
https-only
Redirects
[
    {
        "to": "https://lrservice.com.ua/wp-includes/Southwire/KCY5735683679/Corporation/En/Outstanding-Invoices",
        "from": "http://lrservice.com.ua/wp-includes/Southwire/KCY5735683679/Corporation/En/Outstanding-Invoices",
        "status": 307
    }
]
Ip
77.42.5.121
Ptr
static.121.5.42.77.clients.your-server.de
Contacted domains
[
    "my.binotel.ua",
    "widgets.binotel.com",
    "landrover-media.komliev.studio",
    "fonts.googleapis.com",
    "www.googletagmanager.com",
    "fonts.gstatic.com",
    "wschat1.binotel.com",
    "www.google.fi",
    "stats.g.doubleclick.net",
    "region1.analytics.google.com",
    "www.google-analytics.com",
    "connect.facebook.net"
]
Contacted IP addresses
[
    "192.178.183.94",
    "142.251.13.94",
    "142.251.127.156",
    "216.239.34.36",
    "216.239.38.178",
    "45.91.130.36",
    "142.250.154.95",
    "142.251.110.97",
    "77.42.5.121"
]
Asns
[
    "15169",
    "205722",
    "24940"
]
Countries
[
    "US",
    "UA",
    "FI"
]
Linked domains
[
    "www.landrover.ua",
    "service-calculator.landrover.ua",
    "landrover.ua",
    "komliev.studio",
    "t.me"
]
Social
[
    "https://t.me/AutolifeJLR_bot"
]
Document hash
8a63498252d5bc80a2d488b12ca3c3e1444714a2d539df34b86a04a24a05dcd9
Script hashes
[
    "ff84f53a41760cf70a6771bf9fe5a67683cc3318cb0bcc7dd0e67b7333431bdd",
    "22ba3c18584278dcd54a6700f9e7c607c597a1d92876eb6cd7472e8e4557bd39"
]
Globals
[
    "mediaServerBase",
    "gtag",
    "dataLayer",
    "chatbox",
    "fbAsyncInit",
    "$",
    "jQuery",
    "Popper",
    "yii",
    "bootstrap",
    "_determinate",
    "_indeterminate",
    "_update",
    "_type",
    "_click",
    "_touch",
    "_add",
    "_remove",
    "_callback",
    "_label",
    "_cursor",
    "_mobile",
    "Inputmask",
    "Odometer",
    "InteractiveTab",
    "owlMainAutoplays",
    "timers",
    "closeHeaderDropdown",
    "closeBreadcrumbs",
    "moveSearch",
    "restructureLayout",
    "modelsSpecsHeight",
    "restructureModels",
    "scrolltime",
    "google_tag_data",
    "google_tag_manager",
    "GoogleAnalyticsObject",
    "ga",
    "gaGlobal",
    "BinotelGetCallSettings"
]
Cookies
[
    "_csrf-frontend",
    "_ga_F0ECJ3RK0P",
    "_ga",
    "_gid",
    "_gat_gtag_UA_139713798_2",
    "biatv-cookie"
]
Storage keys
[
    "bwc.visitor-data.13890.with-expire",
    "bwc.tab.13890.QL3dKi6VmZpsHdWTaA",
    "bwc.widgetLang",
    "bwc.employee.13890.QL3dKi6VmZpsHdWTaA.with-expire",
    "bwc.teamSelectionState.13890.QL3dKi6VmZpsHdWTaA",
    "bwc.isWorkingTime.13890.with-expire",
    "bwc.chat-id.13890.QL3dKi6VmZpsHdWTaA",
    "bwc.chat-start-time.13890.QL3dKi6VmZpsHdWTaA",
    "bwc.items.13890.QL3dKi6VmZpsHdWTaA",
    "bwc.msg.13890.QL3dKi6VmZpsHdWTaA.dPGeD",
    "bwc.chat.open.13890.QL3dKi6VmZpsHdWTaA"
]
Tls
{
    "san": [
        "admin.lrservice.com.ua",
        "lrservice.com.ua",
        "www.lrservice.com.ua"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "lrservice.com.ua",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-11T19:05:11Z",
    "valid_from": "2026-08-13T19:05:12Z"
}
Domain age days
2829
Apex age days
2829
Tls age days
27
Tls valid days
89
Requests
84
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 29,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.24.0 (Ubuntu)",
    "content-type": "text/html; charset=UTF-8"
}
Cloudflare Radar · 2026-10-12T21:34:48Z

Observed: · Retrieved:

Uuid
1cdef14b-d07b-4f9f-a6a0-690d472ffe26
Final url
https://lrservice.com.ua/
Status
200
History
[
    {
        "url": "https://lrservice.com.ua/",
        "status": 200
    }
]
DOM structure hash
61ff06ecc213219afd2d0cdb756433027858bb9d7f264de4e023659aac1ffbca
Document hash
3e4c13626ff74cccf6d579e7d4833b9ed6fcfe92f7afe0e4879eadd844aaaa44
Domain risks
[
    "Vehicles"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "lrservice.com.ua",
        "type": "A",
        "value": "77.42.5.121"
    }
]
Dnssec valid
false
Ip
77.42.5.121
Registration record
{
    "registrar": "ua.imena",
    "created": "2017-03-09T13:42:11Z",
    "updated": "2026-02-09T12:22:20Z",
    "expires": "2027-03-09T13:42:11Z",
    "nameservers": [
        "helium.ns.hetzner.de",
        "hydrogen.ns.hetzner.com",
        "oxygen.ns.hetzner.com"
    ]
}
VirusTotal · 2026-10-16T02:00:27Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 4,
    "suspicious": 2,
    "undetected": 32
}
Vendor labels
{
    "VIPRE": "malware",
    "SOCRadar": "phishing",
    "URLQuery": "suspicious",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Malicious, Vehicles (alphaMountain.ai)"
}
Popularity
{
    "Alexa": 441788,
    "Statvoo": 441788
}
Registrar
ua.imena
Expires
2027-03-09T13:42:11Z
First seen
2023-10-05T12:32:57Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "hydrogen.ns.hetzner.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "oxygen.ns.hetzner.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "helium.ns.hetzner.de"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "dns.hetzner.com",
        "value": "hydrogen.ns.hetzner.com"
    },
    {
        "ttl": 21600,
        "type": "MX",
        "value": "mail.lrservice.com.ua",
        "priority": 10
    },
    {
        "ttl": 21600,
        "type": "A",
        "value": "77.42.5.121"
    }
]
Dns at
2026-10-16T02:00:42Z
Jarm
27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5
Certificate
{
    "san": [
        "admin.lrservice.com.ua",
        "lrservice.com.ua",
        "www.lrservice.com.ua"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6582e7e8c4dfc0e9de30fbce632aa868441",
    "sha256": "ae25140543be19c4dc2bb5d439e46f028649988feee94cde688a68715ea8847b",
    "subject": "lrservice.com.ua",
    "valid_to": "2027-01-10T20:59:52Z",
    "valid_from": "2026-10-12T20:59:53Z"
}
Registration record
{
    "registrar": "ua.imena"
}

Questions about lrservice.com.ua

Is lrservice.com.ua legit?

No. PhishDestroy classifies lrservice.com.ua as a Telegram impersonation page (risk: critical, 88/100); it was first detected on 2026-10-12. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.

Is lrservice.com.ua safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on lrservice.com.ua. 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 lrservice.com.ua?

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

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/AutolifeJLR_botStored page reference

IoC extraction recorded 2026-10-14 04:00:34 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 13, 2026
OTX tags cyber securityiocmaliciousnextrayphishingurlhaus
Registrar Internet Invest
RegistrationCreated Mar 9, 2017 — Expires Mar 9, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 12, 2026
DOM Analysisanalyzed Oct 13, 2026score 88/1001 brand signal
IoC Extractionscanned Oct 14, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://lrservice.com.ua/
Favicon Hash
Observed page title
Сторінку не знайдено – Land Rover «Автолайф Центр» офіційний сервіс Ленд Ровер у Києві
Automated brand references
Telegram
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 80 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
77.42.5.121
Network ASN
AS24940
Organization
HETZNER-DC
Observed location
Helsinki, FI
Server header
nginx/1.24.0 (Ubuntu)

Nameservers 1

  • oxygen.ns.hetzner.com

Mail routing 1 MX record

  • mail.lrservice.com.uapriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-12 20:59:53
Valid until
2027-01-10 20:59:52
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-12 22:02:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprintae25140543be19c4dc2bb5d439e46f028649988feee94cde688a68715ea8847b
Certificate names · 2 SANs
  • admin.lrservice.com.ua
  • www.lrservice.com.ua

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-22 10:29:42 UTC

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-22 10:29:42 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:29:42 UTC last content: 2026-10-22 10:29:42 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 subdomains5

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

  • admin.lrservice.com.uaDomain record
  • jaguarservice.com.ua.lrservice.com.uaDomain record
  • mail.lrservice.com.uaDomain record
  • www.admin.lrservice.com.uaDomain record
  • www.lrservice.com.uaDomain record

The original observation time is not recorded for these hostnames.

Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Gridinsoft
Seclookup
SOCRadar
URLQuery
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of lrservice.com.ua · checked Oct 12, 2026

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

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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 5
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/92 engine detections

    View source
  3. AlienVault OTX

    31 community references

    View source
  4. Added to PhishDestroy

    lrservice.com.ua

    View source

Check for cloaking

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

lrservice.com.ua

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes

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 →

Report to Your Local Authorities

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

97-country directory

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

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 lrservice.com.ua)
  • 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

Live Threat Feed Appeal This Listing
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/lrservice.com.ua"
  title="PhishDestroy threat report for lrservice.com.ua"
  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>