VirusTotal
18 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Flap: Instantly Launch and Trade Your Own Token”
Assessment based on the stored source evidence below. Review 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.
18 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
15/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
3 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
Analysis indicates that the domain drop-flap.com was registered on 31 July 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED. The authoritative name servers are aspen.ns.cloudflare.com and jaxson.ns.cloudflare.com, directing traffic to the Cloudflare edge IP 172.67.187.154. VirusTotal records show that a single out of ninety‑one scanned security vendors flagged the domain, suggesting limited detection coverage. The domain appears on one public blocklist and is actively blocked by the PhishDestroy service, confirming that at least one anti‑phishing organization has taken mitigation steps.
The short registration window—creation less than two days before the report date—combined with the use of Cloudflare’s CDN suggests a rapid‑deployment phishing infrastructure. No additional intelligence such as page title, SSL certificate details, or observed HTTP responses is available, leaving the exact content and target brand of the phishing campaign unverified. Consequently, the precise lure (e.g., credential harvesting for a specific service) remains uncertain. Defenders should add drop-flap.com to outbound filtering rules and ensure that internal DNS resolvers block resolution to the associated Cloudflare IP address.
Security information and event management (SIEM) systems should monitor for connections to 172.67.187.154 and generate alerts on any successful HTTP(S) requests. Because the domain is hosted on a shared Cloudflare edge, blocking the IP may impact legitimate services; therefore, a domain‑level blocklist entry is preferred. Continuous re‑scanning with multi‑vendor engines is advised to capture any changes in detection status, and threat‑intel feeds should be queried for future sightings of the same registrar or nameserver patterns.
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.
These checks have no retained result. This does not mean they passed or that a scan is running.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/FlapOfficialStored page referenceIoC extraction recorded 2026-08-02 04:00:21 UTC
Edge-IP reputation is not attributed to this domain.
aspen.ns.cloudflare.comjaxson.ns.cloudflare.comLocation describes the IP network.
bea803304c45404ad0f7aaa1f7f11115629ea55694143c11f7d927df32c4c9aaSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of drop-flap.com · checked Aug 1, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://drop-flap.com/https://drop-flap.com/Content-Type: text/htmlServer: cloudflareCache-Control: max-age=2592000CF-Cache-Status: HITContent-Encoding: gzipsummary_large_image36978h3=":443"; ma=86400max-age=2592000defaultHITa243841abdb3dc94-FRAkeep-alivegzipframe-ancestors http: https:text/htmlSat, 01 Aug 2026 08:36:35 GMTFri, 31 Jul 2026 20:30:48 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=e5lr8NE6owuLhF9cU%2FSWLxkUp2MQ7OlSZt7r1YyaeZXTZTIyAgg3DSYuupvh1A39imNvKQh3lpXENb4k0iF8p2%2F6l%2BtjoE38sKayxBDewMrmfrK3mVmMAdQSmqZiEjGk"}]}cloudflaremax-age=63072000; includeSubDomains; preloadchunkedaccept-encodingnosniff1; mode=blockValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
The collection attempt did not establish a file status. No usable HTTP response was retained.
/sitemap.xml
The collection attempt did not establish a file status. No usable HTTP response was retained.
/.well-known/security.txt
The collection attempt did not establish a file status. No usable HTTP response was retained.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareLocal archived 2026-08-01 08:36:36 UTCScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
172.67.187.154.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
Unknown→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Unknown
probe_inconclusive
blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unavailable→Reachable
Reachable→Unavailable
Reachable
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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