Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy’s intake AI observed on 2026-10-23 that the site returned a 403 HTTP status and a Cloudflare challenge page, which prevented any page content from being examined. The domain was first seen by PhishDestroy on 2026-10-23 and has been added to the internal blocklist.
How the scam works
The current evidence does not show a specific malicious mechanism; the site only presented a challenge page. In general, challenge pages can be used to hide phishing, credential harvesting, or other fraud, but no such activity was detected here.
Evidence
VirusTotal scanned the domain on 2026-10-22 and reported 0 malicious and 0 suspicious detections from 92 engines. Google Safe Browsing checked on 2026-10-23 and did not flag the domain. urlscan captured the site on 2026-10-16; its overall verdict was clean, although its machine‑learning engine flagged the URL as malicious with a high confidence score. OTX listed two pulses referencing the domain as of 2026-10-23, and external blocklists returned no hits on the same date.
Infrastructure
The domain was registered on 2025-11-04 through Namecheap Inc. Hosting is provided via Cloudflare, with recorded IP addresses 104.21.9.46 and 172.67.141.186, both associated with Canada. The TLS certificate, issued by Google Trust Services / WE1, is valid from 2026-09-11 to 2026-12-10 and covers boringone.page and its subdomains.
What to do
Visitors should avoid entering any credentials or personal information on the site; if any data was submitted, change the associated passwords immediately. Defenders can add boringone.page to blocklists, monitor network logs for connections to the recorded IPs, and keep the domain under observation for future changes.
DOM Analysisanalyzed Oct 23, 2026score 63/1002 brand signals
Submitted URLhttp://boringone.page/
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.9.46
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
mariah.ns.cloudflare.com
ned.ns.cloudflare.com
Mail routing 2 MX records
mx2.privateemail.compriority 10
mx1.privateemail.compriority 10
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-09-11 13:17:32
Valid until
2026-12-10 14:15:04
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb1d74f8170239c1f8780a2ee28d7117ec0581c67ca5a8bb4b16be3aaa7523b80Certificate names · 2 SANs
boringone.page
*.boringone.page
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
HSTS: observedDNSSEC: not observedWAF / firewall: observedCloaking flag: not observed
Open Graph title:BoringOne.page
Open Graph description:The Linktree alternative that builds your page for you. Just paste — AI delivers a clean, beautiful link-in-bio. Free beta, no account needed.
3 evidence signal groups linked0 stored notification recordsUnverified
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.
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 →
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 boringone.page)
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)
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
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.
(SE)
