Skip to security report
Analytics Dashboard
Domain security report
phantomapp.io favicon

phantomapp.io

“Phantom — Everything you own, in one place you control”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 12/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Phantom
OTX: 4 refs Sep 9, 2026 Phantom CDN
API
Registrar
Namecheap
Resolved IP
75.2.60.5
Registered
Aug 11, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
This domain has been flagged as malicious
Security engines reporting a detection: 12. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
12 det.
OTX references
4 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Expired or unverified
Age
2 mo New
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

12 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
12/89
OTX
4 community refs
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

Stored evidence for phantomapp.io: VirusTotal recorded 2 detections among 89 scanners on 2026-09-09. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for phantomapp.io. Each item in this report remains at the scope supplied by its dated source record.

Read the full analysis6

Detection Evidence

VirusTotal records 2 detections among 89 scanners in the stored snapshot dated 2026-09-09. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-09 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for phantomapp.io in the snapshot dated 2026-09-09. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains phantomapp.io as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed phantomapp.io on 2026-09-09. The MetaMask and SEAL blocklist snapshot is dated 2026-09-09 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-08-11. A URLScan reference was stored on 2026-09-09 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For phantomapp.io, the registrar field records NAMECHEAP INC; this is kept as an exact source value. The source stores 75.2.60.5 as the observed address in this record. The registration date for phantomapp.io is recorded as 2026-08-11. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The phantomapp.io record states that VirusTotal recorded 2 detections among 89 scanners on 2026-09-09. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-09. PhishDestroy remains a separate publisher catalogue entry in the stored record. For phantomapp.io, the registrar field records NAMECHEAP INC; this remains separate from the other source fields. The observed address field in this record contains 75.2.60.5. The supported conclusion is bounded to the exact stored observations for phantomapp.io. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to phantomapp.io during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain phantomapp.io as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to phantomapp.io. The stored record does not justify extending that rule to 75.2.60.5 or to other infrastructure records.

Data coverage & collection21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
12 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NAMECHEAP INCCollection time not recorded
Network & DNS
75.2.60.5 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE2
Page captures
2 · retained captures
Page analysis
8 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
82/100 · mobile performance
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
22 · stored state changes
Source observation history
3 · stored source events
Lookalike relationships
3 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.
Blocklist records2 · external source matches

Public Blocklist Status

Domain, network & archiveNAMECHEAP INC · 75.2.60.5 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Namecheap US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for phantomapp.io →
RegistrationCreated Aug 11, 2026 (65d · New) — Expires Aug 11, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedSep 9, 2026
DOM Analysisanalyzed Sep 10, 2026score 100/1008 brand signals
Submitted URLhttp://phantomapp.io/

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
75.2.60.5
Network ASN
AS16509
Organization
AWS Global Accelerator (GLOBAL)
Observed location
Seattle, US
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Mail routing 2 MX records

  • mail.protonmail.chpriority 10
  • mailsec.protonmail.chpriority 20

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-08-17 11:17:12
Valid until
2026-11-15 11:17:11
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-09 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint072be1c5cb78b1050709c19862534fa6ae1dfd4fb42e72489e65fd916dab870d
Certificate names · 1 SANs
  • www.phantomapp.io

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

viewdns.info · 75.2.60.5rapiddns.io

Latest Classified Outcome 2026-10-15 22:28:05 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-15 22:28:05 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-15 22:28:05 UTC last content: 2026-10-15 10:27:48 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

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

  • www.phantomapp.ioDomain record

The original observation time is not recorded for these hostnames.

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

VirusTotal Analysis

12 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
Webroot

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 phantomapp.io · checked Sep 9, 2026

82
Needs Work
Performance
FCP
2.65s
First Contentful Paint
LCP
2.65s
Largest Contentful Paint
CLS
0.062
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
17.18s
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.

Detection & evasion checksStored browser and crawler observations
Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Netlify

Scanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://phantomapp.io/; server=Netlify

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-10 22:17:51 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-09-10 22:05:23 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. Threat First Observed 2026-09-09 19:06:52 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 75.2.60.5.
Stored observation history25

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→redirected

    http_redirect

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 20
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→inactive

    parked · parking_or_lifecycle_page

  13. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→inactive

    parked · parking_or_lifecycle_page

  15. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→inactive

    parked · parking_or_lifecycle_page

  17. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unavailable→Reachable

  19. Availability monitor · Recorded state

    Reachable→Unavailable

  20. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
phantomapp.io detected and queued for full analysis
Sep 9, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 10, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 9, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Sep 23, 2026
VirusTotal
12/89 recorded on VirusTotal
Sep 12, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 16, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 10, 2026
Drainer Identified
Solana Drainer wallet drainer — impersonating Phantom
Sep 9, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 9, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Sep 11, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 200); the cause was not independently established.
Sep 11, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 9, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Public Blocklist Status

Related infrastructureShared hosting, registrar records and related domains

Lookalike domains

3 stored lookalike domains

phantom-app.com various phantomapp.com various phantomx.app addition
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Report
ChainAbuse
Help & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

4 evidence signal groups linked 0 reports recorded Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.

Europol
Find the official reporting channel for your EU country
National police directory
Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. 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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing

Recommendations & Advice for Victims

An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with phantomapp.io — act now.

What should I do immediately?
Urgent
  • Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
  • Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
  • 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

According to the FBI, the most important details are transaction data:

  • Cryptocurrency addresses — scammer's wallet (e.g., 0x5856...35985)
  • Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
  • Transaction ID (hash) — the unique blockchain transaction identifier
  • 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 phantomapp.io)
  • 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)
  • Chainabuse — flag scam wallets across exchanges & platforms
  • Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • 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 crypto scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
  • 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
  • Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
  • Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Read every approval — verify permissions before signing. Reject unlimited approvals
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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/phantomapp.io"
  title="PhishDestroy threat report for phantomapp.io"
  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>