Spamhaus DBL
phishing domain
PhishDestroy first recorded pendle.finance-safe.site on 2026-11-15. Listed by external blocklists: MetaMask, SEAL.
Page title: “$PENDLE Rewards Date Proposal”
Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Recorded source summary
pendle.finance-safe.site is a subdomain of finance-safe.site. PhishDestroy first observed the hostname on Nov 15, 2026. The hostname explicitly references Pendle; stored content metadata identifies the same apparent target. The captured page title is “$PENDLE Rewards Date Proposal”. Current evidence score: 66/100 (high).
Positive findings are stored from 3 sources: MetaMask, SEAL, and Spamhaus DBL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 11:20 UTC. Spamhaus DBL: DBL_PHISH on Nov 15, 2026 at 19:31 UTC. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Nov 15, 2026 at 04:55 UTC.
Latest classified outcome: dns inactive; cause dns nxdomain on Nov 22, 2026 at 05:03 UTC. Registration records for the registrable domain finance-safe.site list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Nov 15, 2026 as the creation date. Registration and first observation occurred on the same UTC date. At collection time, the hostname resolved to 188.114.96.3 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Nov 15, 2026 at 19:20 UTC returned 25/100. The evidence archive retains 7 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. TLS metadata lists YE2 as the certificate issuer with validity through Feb 13, 2027.
The content indicators and 3 positive source findings support the current Pendle impersonation and phishing classification. The target field identifies Pendle.
phishing domain
Scan report
Open reportPage capture
SHA-256 2604316f…9184ada
25 / 100 · heuristic score · 1 brand reference · 0 classifications
Content heuristic only; not the final score
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
|---|---|
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Registration record | Registrar: NICENIC INTERNATIONAL GROUP CO., LIMITED; Registrar iana ID: 3765; Registrar URL: https://nicenic.com/; Created: 2026-11-15T04:37:57Z; Updated: 2026-11-17T17:40:09Z; Expires: 2027-11-15T04:37:57Z; Status: serverHold https://icann.org/epp, clientDeleteProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp, clientHold https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: dahlia.ns.cloudflare.com, ian.ns.cloudflare.com; Dnssec: unsigned |
PhishDestroy rates pendle.finance-safe.site as high risk (evidence score 66/100) from the recorded evidence; it was first recorded on 2026-11-15. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on pendle.finance-safe.site. A confirmed blockchain transaction cannot be reversed.
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Last checked
56026402adf0bac62cfbda6489fd3569ffda436916d6078b6aef8dee84e8f7d6 · 17085 bytes 71587b29f44b93c017500f4a2e2e46f97252b26648b3370cdc8d9c1dc78af9e5 · 13148 bytes ee461841dd1ea703c543c6492fb810141b6e2c3cc04742733312e5d2415bcb82 · 16778 bytes 8a159aad66e53a8da9f746259c45e01920ad4fbd1d3ed2336a20478fdb985262 · 19204 bytes 7b69abf9ebe3d10f8e764f905be21c8c0bdd8272a4fe69a963ecbef11a2f0777 · 17027 bytes 2e1d1e1217316e1b08952e33010bd78c10939b65bfd82feb273344262d3d181a · 115278 bytes Registrable domain behind this subdomain: finance-safe.site. 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.
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.
Edge-IP reputation is not attributed to this domain.
dahlia.ns.cloudflare.comian.ns.cloudflare.comLocation describes the IP network.
d6cc938da5991dc2d9a0726b47e4ae03b459f45ab81837caef90c2911d0c0047*.finance-safe.sitefinance-safe.siteSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The domain no longer resolves in DNS.
Google PageSpeed Insights — mobile performance audit of pendle.finance-safe.site ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://pendle.finance-safe.site/Content-Type: text/html; charset=UTF-8CF-Mitigated: challengeServer: cloudflareContent-Encoding: gzip7d73d22d650fe1149c2606c1070ce26696714e7f541754842ef84d0422123298Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,h3=":443"; ma=86400challengea5af52edf854e51a-TXLclosegzipdefault-src 'none'; script-src 'nonce-5fD4IY71nwHQ6GjGvPL2UD' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blotext/html; charset=UTF-8Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,require-corpsame-originsame-originSun, 15 Nov 2026 15:35:07 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}?1accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*same-origin{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=1qMAYmNO2YKaLDR35ELyolL5VV0rpFYCDGppx%2FxF2LJ%2B4SAR5byDQLh3O4bcylYNa0Kq0dIwKqv7hVJdLSHZJ9kFdQPqySqJAVNHWDkA4MveUlyPmey3piVtvRzQvLAuE9zyCM%2FGHcloudflarechlray;desc="a5af52edf854e51a"chunkednosniffSAMEORIGINValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 9 SHA-256 hashes: 6 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-15 15:37 UTC.
Open this scan on URLScan 01a1dfd7-90cf-77da-8672-7d187fcb0146 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Not resolving in DNS
domain does not exist in DNS
Behind a check page or access restriction
Cloudflare check page · Cloudflare · check page
Behind a check page or access restriction
Cloudflare check page · Cloudflare · check page
Behind a check page or access restriction
Cloudflare check page · Cloudflare · check page
Reachable
Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 14. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 11 h 9 min after registration
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
36 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Where to send it:
Nothing matches. Clear the search or choose another filter.
Showing 12 of 36
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
pendle.finance-safe.site PD-44BFC5794C4C62B52AD3 Recipient: abuse@nicenic.net Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
pendle.finance-safe.site)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.
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.