Skip to security report
Domain security and threat intelligence
megalaunch.live favicon

megalaunch.live

In short

megalaunch.live is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (90/100). Registrar: NETIM SAS. Status: Last known active. Hosting: Network Billing Systems. PhishDestroy sent 1 abuse report. VirusTotal: 6/92 engines flag it. Do not enter credentials or connect a wallet.

“MegaEth — Claim $METH”

Registrar
NETIM SAS
Resolved IP
216.198.79.1
Registered
Jul 9, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 6/92 Stored blocklist matches: 2 Scam type: Crypto Drainer
OTX: 3 refs Oct 23, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 2. 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
Reports sent
view timeline
Source evidenceVirusTotal 6 / 92 · OTX 3 references 6 sources

VirusTotal

6 / 92 engine detections

Open report

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Analysis

Critical
VirusTotal
6 / 92
OTX
3 community refs
Page captures
7

PhishDestroy threat report

Overview

PhishDestroy listed megalaunch.live as a suspicious domain after its intake on 2026-10-23, citing six malicious detections on VirusTotal. The site was first observed by PhishDestroy on 2026-10-23 showing the page title “MegaEth — Claim $METH”. An HTTP 308 redirect was recorded on that date.

How the scam works

The domain appears in typical crypto‑phishing campaigns that lure users with promises such as claiming a token ($METH). Such pages generally attempt to trick visitors into entering wallet credentials or approving transactions, but no specific malicious behavior was captured on this page.

Evidence

VirusTotal reported six malicious detections from alphaMountain.ai, CRDF, Emsisoft, Fortinet, Netcraft and Webroot on 2026-10-23 (6/92 engines). Google Safe Browsing checked on 2026-10-23 did not flag the site. urlscan.io captured the page on 2026-10-21; its overall verdict was non‑malicious but its engine score marked it malicious (score 94). External blocklists MetaMask and SEAL listed the domain, and PhishDestroy’s internal list flagged it. Cloudflare Radar on 2026-10-23 categorized the domain as phishing. OTX recorded three pulses mentioning megalaunch.live.

Infrastructure

The domain was registered on 2026-07-09 through NETIM SAS and was 105 days old at the time of observation. The DNS records observed on 2026-10-23 listed Cloudflare nameservers liz.ns.cloudflare.com and finley.ns.cloudflare.com, without DNSSEC, and the A record pointed to 216.198.79.65, an Amazon‑owned address associated with Vercel. The TLS certificate captured on 2026-10-23 was issued by Let’s Encrypt, valid from 2026-09-11 to 2026-12-10, and the response included an HSTS header with max‑age=63072000.

What to do

Visitors should avoid entering any crypto wallet credentials or approving transactions on the site; if such data was submitted, change associated passwords and monitor wallet activity. Defenders can block megalaunch.live at the network perimeter, add it to phishing blocklists, and review access logs for connections to this exact domain.

Collected source details

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

URLScan · 2026-10-23T03:05:00Z

Observed: · Retrieved:

Uuid
01a166b7-f865-70cb-899e-4ff68a6ce610
Final url
https://www.megalaunch.live/
Status
200
Redirected
parent-domain
Redirects
[
    {
        "to": "https://megalaunch.live/",
        "from": "http://megalaunch.live/",
        "status": 307
    },
    {
        "to": "https://www.megalaunch.live/",
        "from": "https://megalaunch.live/",
        "status": 308
    }
]
Ip
216.198.79.65
Contacted domains
[
    "api.web3modal.org",
    "quiet-pine-8993.hellohyper110.workers.dev",
    "fonts.gstatic.com",
    "fonts.googleapis.com",
    "api.ipify.org",
    "cdnjs.cloudflare.com",
    "pulse.walletconnect.org",
    "secure.walletconnect.org",
    "cdn.jsdelivr.net",
    "pbs.twimg.com",
    "megalaunch.live",
    "invalid"
]
Contacted IP addresses
[
    "192.178.183.94",
    "142.251.20.95",
    "104.18.18.237",
    "172.66.157.155",
    "151.101.193.229",
    "172.67.74.152",
    "104.17.25.14",
    "172.64.150.129",
    "104.21.41.229",
    "216.198.79.65",
    "216.198.79.1"
]
Asns
[
    "15169",
    "13335",
    "54113",
    "16509"
]
Countries
[
    "US"
]
Document hash
c42e38d63bf98a38374b0eba69ce009023e0e72c9dc8342817176ada2c7c85af
Globals
[
    "e46jvfbmmj",
    "c19e53ac75",
    "f449d05aeb4b879d",
    "bbd49f82312d0ffe",
    "db1d0527",
    "abdae6fa4761fdf009",
    "ad441e22bf",
    "_iqfbyspjq",
    "Buffer",
    "global",
    "process",
    "litPropertyMetadata",
    "reactiveElementVersions",
    "litHtmlVersions",
    "litElementVersions",
    "_znisvuhjscdlmsnoz",
    "CoinbaseWalletSDK",
    "CoinbaseWalletProvider",
    "WalletLink",
    "WalletLinkProvider",
    "CryptoJS",
    "_ethers",
    "ethers",
    "windowHandler",
    "MerkleTree",
    "MerkleMountainRange",
    "IncrementalMerkleTree",
    "MerkleSumTree",
    "_gsfojeqdtjrooqppj",
    "q2icokw78y",
    "promptSeed",
    "downloadAppKitLogsBlob"
]
Cookies
[
    "gacfxdn1x7"
]
Storage keys
[
    "IsThisFirstTime_Log_From_LiveServer",
    "@appkit/active_caip_network_id"
]
Tls
{
    "san": [
        "www.megalaunch.live"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "www.megalaunch.live",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-10T08:58:49Z",
    "valid_from": "2026-09-11T08:58:50Z"
}
Domain age days
105
Apex age days
105
Tls age days
41
Tls valid days
89
Requests
53
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000"
}
Cloudflare Radar · 2026-10-23T01:33:25Z

Observed: · Retrieved:

Uuid
ed3dcd1d-6e05-469c-a549-e5de356c9972
Final url
https://www.megalaunch.live/
Status
200
Redirected
subdomain
History
[
    {
        "url": "https://megalaunch.live/",
        "status": 308
    },
    {
        "url": "https://www.megalaunch.live/",
        "status": 200
    }
]
DOM structure hash
a06331748be0cd2ac184d7da6a3e87c4b159b9c2155a578fd20fed497d90e5ec
Document hash
c42e38d63bf98a38374b0eba69ce009023e0e72c9dc8342817176ada2c7c85af
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "megalaunch.live",
        "type": "A",
        "value": "216.198.79.1"
    },
    {
        "name": "www.megalaunch.live",
        "type": "CNAME",
        "value": "38b74f848bedb1da.vercel-dns-017.com"
    },
    {
        "name": "www.megalaunch.live",
        "type": "CNAME",
        "value": "38b74f848bedb1da.vercel-dns-017.com"
    }
]
Dnssec valid
false
Ip
216.198.79.65
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "NETIM SAS",
    "created": "2026-07-09T21:45:37Z",
    "updated": "2026-08-13T19:44:17Z",
    "expires": "2027-07-09T21:45:37Z",
    "nameservers": [
        "liz.ns.cloudflare.com",
        "finley.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-21T12:09:14Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 50,
    "malicious": 6,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "CRDF": "malicious",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-07-09T22:52:40Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "liz.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.1"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "finley.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "finley.ns.cloudflare.com"
    }
]
Dns at
2026-10-21T12:14:46Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "megalaunch.live"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6cb68f720b67d79033be25a49861af92d57",
    "sha256": "99108fccf38495e3f3d4e9537388e452c3f5183faa8d0982098d26c5d0dd1db8",
    "subject": "megalaunch.live",
    "valid_to": "2026-12-09T05:38:26Z",
    "valid_from": "2026-09-10T05:38:27Z"
}
Registry data
{
    "status": [
        "active",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-07-09T21:00:00Z",
        "last changed": "2026-07-09T23:45:34Z",
        "registration": "2026-07-09T00:00:00Z",
        "registrar expiration": "2027-07-09T21:00:00Z",
        "last update of RDAP database": "2026-10-21T10:59:20Z"
    },
    "registrar": "NETIM SAS",
    "registrar_iana_id": "1519"
}
Website checks · 2026-10-23T01:37:44Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "megalaunch.live"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-23T01:32:31Z",
    "first": "2026-10-23T01:32:31Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 6648
}
Page title and metadata
{
    "title": "MegaEth — Claim $METH"
}
Trackers
{
    "requests": 4,
    "trackers": [
        {
            "name": "X Corp.",
            "company": "X Corp.",
            "country": "US",
            "category": "Social Media",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://quiet-pine-8993.hellohyper110.workers.dev/"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 308,
    "timings": {
        "dns": 9,
        "tls": 21,
        "wait": 12,
        "connect": 5,
        "download": 0
    },
    "response_ms": 47
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 25147,
    "co2_grams": 0.0009,
    "cleaner_than": 52
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.58.189",
            "host": "liz.ns.cloudflare.com"
        },
        {
            "ip": "108.162.195.58",
            "host": "finley.ns.cloudflare.com"
        }
    ],
    "zone": "megalaunch.live"
}
Cookies
{
    "cookies": [
        {
            "name": "gacfxdn1x7"
        }
    ]
}
Location
{
    "ip": "216.198.79.1",
    "asn": "16509",
    "org": "Network Billing Systems",
    "city": "Atlanta",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "megalaunch.live"
}
DNS records
{
    "A": [
        "216.198.79.1"
    ],
    "NS": [
        "finley.ns.cloudflare.com",
        "liz.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"finley.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2414407844, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.198.79.1",
    "family": 4
}
Redirects
{
    "chain": [
        "https://megalaunch.live",
        "https://www.megalaunch.live/"
    ],
    "count": 1
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.megalaunch.live"
    ]
}
Tech stack
{
    "technologies": [
        "Vercel",
        "HSTS"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000"
    }
}

Questions about megalaunch.live

Is megalaunch.live legit?

No. PhishDestroy classifies megalaunch.live as a phishing page (risk: critical, 90/100); it was first detected on 2026-10-23. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.

Is megalaunch.live safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on megalaunch.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 megalaunch.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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 7 captures

Observed page title
MegaEth — Claim $METH
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 46 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar NETIM SAS
RegistrationCreated Jul 9, 2026 (105d) — Expires Jul 9, 2027
HTTP Status308 Permanent Redirect
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 60/100
Submitted URLhttp://megalaunch.live/
Favicon Hash
Case ID
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
216.198.79.1
Network ASN
AS16509
Organization
Network Billing Systems
Observed location
Atlanta, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • finley.ns.cloudflare.com
  • liz.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-10 05:38:27
Valid until
2026-12-09 05:38:26
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint99108fccf38495e3f3d4e9537388e452c3f5183faa8d0982098d26c5d0dd1db8
Certificate names · 1 SAN
  • megalaunch.live

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

Recorded subdomains1

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

  • www.megalaunch.liveDomain record

The original observation time is not recorded for these hostnames.

Technologies · 2 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: 6 detections
alphaMountain.ai
CRDF
Emsisoft
Fortinet
Netcraft
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
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://megalaunch.live/
Final URL: https://www.megalaunch.live/
MegaEth — Claim $METH
Response
HTTP 200
HTML body
24.6 KB
Compressed
5.5 KB
Links
0 internal · 0 external
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 14
Access-Control-Allow-Origin
*
Age
0
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 23 Oct 2026 01:32:38 GMT
Etag
W/"67a5763259e3a4e14d5ee01719b51434"
Last-Modified
Fri, 23 Oct 2026 01:32:38 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000
Transfer-Encoding
chunked
X-Vercel-Cache
MISS
X-Vercel-Id
yul1::hksl2-1792719157975-ae1e81c55375

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

Registration & observation details1

Availability observations

Last reachable observation

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

Recorded activity

6 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    6/92 engine detections

    View source
  4. Abuse report sent

    PD-20261023-FEC915

    abuse@netim.net
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    megalaunch.live

    View source

Check for cloaking

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

megalaunch.live

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-FEC915 Recipient: abuse@netim.net
PDF notice generated Notice text archived (275 chars)
Abuse notice text as sent to the provider
Registrar: Netim SARL (France)
Policy Violations: “Strict abuse policy classifying phishing, malware, fraud and botnet activity as illegal domain use; registrar may suspend or terminate affected domains.”
Applicable Laws: French Penal Code Art.323-1+; EU Directive 2013/40/EU
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records 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.

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 megalaunch.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

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