Skip to security report
Domain security and threat intelligence
lnfo-support.live favicon

lnfo-support.live

In short

lnfo-support.live is an Apple impersonation page detected by PhishDestroy on 2026-10-25.

“iCloud”

Registrar
Dynadot
Resolved IP
104.21.25.108
Registered
Oct 7, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation
VirusTotal detections: 10/92 Stored blocklist matches: 1 Automated brand label: Apple Young domain: 17 days old
VirusTotal
engine detections
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Reports sent
No sent record
OTX: 2 refs Oct 25, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 10. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Domain summary

lnfo-support.live is an Apple impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (90/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 10/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
10 / 92
OTX
2 community refs
Page captures
3

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment classified lnfo-support.live as an impersonation phishing page. The recorded page title reads "iCloud," suggesting the site pretends to be Apple’s iCloud service. The domain was first seen by PhishDestroy on 2026-10-25 and returned an HTTP 200 response at that time.

How the scam works

Impersonation phishing pages copy the look and language of a legitimate brand to trick visitors into entering login credentials, recovery phrases, or other sensitive data. The harvested information can then be used to hijack accounts or conduct further fraud, though the exact behavior of this site was not observed in the captured snapshot.

Evidence

VirusTotal scanned the domain on 2026-10-24 and reported 10 detections across 92 engines, labeling it malicious by BitDefender, CRDF, G-Data, LevelBlue and OpenPhish, and suspicious by several others. Google Safe Browsing checked on 2026-10-25 did not flag the site. urlscan.io captured the page on 2026-10-25; its engine verdict marked it malicious with a score of 90, while the overall verdict was not malicious. Cloudflare Radar also flagged the domain as phishing on 2026-10-25. The external OpenPhish blocklist includes the domain, and OTX lists two pulses referencing it.

Infrastructure

The domain was registered on 2026-10-07 through Dynadot Inc, giving it an age of 17 days at the time of observation. The recorded DNS records listed A entries for 172.67.134.7 and 104.21.25.108, and the HTTP response headers included a Cloudflare server header indicating a Cloudflare‑provided WAF. The recorded TLS certificate was issued by Let’s Encrypt, covered the apex and a wildcard, and was valid until 2027-01-05.

What to do

Do not enter any Apple ID credentials, recovery phrases, or personal data on this site. If credentials were submitted, change the associated passwords immediately and enable two‑factor authentication. Organizations should block lnfo-support.live at the network perimeter and monitor logs for any connections to the recorded IP addresses.

Source evidenceVirusTotal 10 / 92 · OTX 2 references 5 sources

VirusTotal

10 / 92 engine detections

Open report
VirusTotal · 2026-10-24T12:00:35Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 6,
    "suspicious": 4,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "SOCRadar": "suspicious",
    "LevelBlue": "phishing",
    "OpenPhish": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Suspicious (alphaMountain.ai)"
}
First seen
2026-10-07T09:57:54Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:196c"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.134.7"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "bristol.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "cosmin.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:8607"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.25.108"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "bristol.ns.cloudflare.com"
    }
]
Dns at
2026-10-24T12:50:05Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.lnfo-support.live",
        "lnfo-support.live"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "62c34caae10b2bdb451189598ddaa4e650f",
    "sha256": "dd97506014a9539beaee29f584fee0d6a1a81b3d1db519fa37bfe4e9d16ec437",
    "subject": "lnfo-support.live",
    "valid_to": "2027-01-05T09:22:34Z",
    "valid_from": "2026-10-07T09:22:35Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-07T10:02:54Z",
        "last changed": "2026-10-07T13:22:56Z",
        "registration": "2026-10-07T10:02:54Z",
        "registrar expiration": "2027-10-07T10:02:54Z",
        "last update of RDAP database": "2026-10-23T11:19:59Z"
    },
    "registrar": "DYNADOT LLC",
    "registrar_iana_id": "472"
}

Cloudflare Radar

Malicious

Not recorded
Open report
Cloudflare Radar · 2026-10-25T04:37:53Z

Observed: · Retrieved:

Uuid
ae78c924-d9e5-4258-a707-4b00852acdaa
Final url
https://lnfo-support.live/
Status
200
History
[
    {
        "url": "https://lnfo-support.live/",
        "status": 200
    }
]
DOM structure hash
a7d9675e08f2352eeb37c5eb268ac62122abacc9e9b512703a4b2c703c2b19ec
Document hash
e13ce0b406a2ae3f14d9601a069a2935992f0706a5b5d6327e700a120bad5ccc
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains",
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "lnfo-support.live",
        "type": "A",
        "value": "172.67.134.7"
    },
    {
        "name": "lnfo-support.live",
        "type": "A",
        "value": "104.21.25.108"
    },
    {
        "name": "lnfo-support.live",
        "type": "AAAA",
        "value": "2606:4700:3031::6815:196c"
    },
    {
        "name": "lnfo-support.live",
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:8607"
    }
]
Dnssec valid
false
Ip
172.67.134.7
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

Page capture

Not recorded
Open report
URLScan · 2026-10-25T01:04:20Z

Observed: · Retrieved:

Uuid
01a17096-311a-77a3-a9e0-dc86f4211fd4
Final url
https://lnfo-support.live/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://lnfo-support.live/",
        "from": "http://lnfo-support.live/",
        "status": 307
    }
]
Ip
172.67.134.7
Contacted IP addresses
[
    "172.67.134.7"
]
Asns
[
    "13335"
]
Document hash
644f1ccc7e01d01bc08acc657bdedfd029a91a365d222330ffbdcb0cef3b1c79
Script hashes
[
    "2540e504aee43f794b23548ac6c54233a06df1b62d85c59c4a075add9779b1a9"
]
Globals
[
    "__LINK_ENTRY_TOKEN",
    "cleanUrlBar",
    "restoreCleanUrlEntry",
    "applyCleanUrlTitle"
]
Tls
{
    "san": [
        "*.lnfo-support.live",
        "lnfo-support.live"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "lnfo-support.live",
    "protocol": "QUIC",
    "valid_to": "2027-01-05T09:22:34Z",
    "valid_from": "2026-10-07T09:22:35Z"
}
Domain age days
17
Apex age days
17
Tls age days
17
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 90,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}

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 checks · 2026-10-25T04:40:29Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "lnfo-support.live"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T04:34:28Z",
    "first": "2026-10-07T12:28:22Z",
    "changes": 2,
    "days_archived": 3,
    "scans_per_day": 0.11,
    "avg_page_bytes": 1468
}
Page title and metadata
{
    "title": "iCloud"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 16,
        "wait": 169,
        "connect": 6,
        "download": 0
    },
    "response_ms": 194
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 407,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.45",
            "host": "cosmin.ns.cloudflare.com"
        },
        {
            "ip": "108.162.194.47",
            "host": "bristol.ns.cloudflare.com"
        }
    ],
    "zone": "lnfo-support.live"
}
Location
{
    "ip": "2606:4700:3031::6815:196c",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "lnfo-support.live"
}
DNS records
{
    "A": [
        "172.67.134.7",
        "104.21.25.108"
    ],
    "NS": [
        "cosmin.ns.cloudflare.com",
        "bristol.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"bristol.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416859456, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3031::6815:196c",
        "2606:4700:3035::ac43:8607"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3031::6815:196c",
    "family": 6
}
Redirects
{
    "chain": [
        "https://lnfo-support.live"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats New Domains Security Risks

Questions about lnfo-support.live

Is lnfo-support.live legit?

No. PhishDestroy classifies lnfo-support.live as an Apple impersonation page (risk: critical, 90/100); it was first detected on 2026-10-25. VirusTotal: 10/92 engines flag it. Treat the site as unsafe.

Is lnfo-support.live safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on lnfo-support.live. 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 lnfo-support.live?

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

Blocklist matchesOpenPhish · PhishDestroy 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 3 captures

All capture links and hashes (3)
Observed page title
iCloud
Automated brand references
Icloud
TLS Certificate
Issued by YE2 · stored validity ends in 72 days

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
RegistrationCreated Oct 7, 2026 (17d · Very New!)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 10/1001 brand signal
Submitted URLhttp://lnfo-support.live/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.25.108
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • cosmin.ns.cloudflare.com
  • bristol.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-10-07 09:22:35
Valid until
2027-01-05 09:22:34
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintdd97506014a9539beaee29f584fee0d6a1a81b3d1db519fa37bfe4e9d16ec437
Certificate names · 2 SANs
  • *.lnfo-support.live
  • lnfo-support.live

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

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

VirusTotal Analysis

10 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 8 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
G-Data
Gridinsoft
LevelBlue
OpenPhish
SOCRadar
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://lnfo-support.live/
Final URL: https://lnfo-support.live/
iCloud
Response
HTTP 200
HTML body
774 B
Compressed
572 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4fe83d768e4c8b2-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sun, 25 Oct 2026 04:35:31 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=oyZNSFAaZPgevekidAXNTmKtKobhQVdeUF7gwy4G0pfYpoksBFshSnO8uzFou9ZgOt1WPRxY5z8Xb327lx%2BLOqacsF2YDQJkic2aI354dEk10Mg3i3O%2BFutQkita%2BGjK6%2BiM5Q%
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Stored observation history1

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

  1. VirusTotal · Detection count

    8→10

All retained availability observations1

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    stale_current_evidence
    Monitor confidence
    0
    Original source timestamp
    2026-10-25 05:38:40.309689
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. VirusTotal

    10/92 engine detections

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    lnfo-support.live

    View source

Check for cloaking

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

lnfo-support.live

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
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.

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 lnfo-support.live)
  • 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

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 →
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/lnfo-support.live"
  title="PhishDestroy threat report for lnfo-support.live"
  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>