Dropbox status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Dropbox reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Dropbox users through our website.

• Errors (75%)
• Website Down (25%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Nottingham	Errors	23 days ago
Guayaquil	Website Down	23 days ago
Flumet	Errors	1 month ago
Irapuato	Errors	1 month ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	4 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  David Silva Smith (@DavidSilvaSmith) reported 7 minutes ago

  Got dropbox, ickoud, google drive working last night. Looking at @immichapp for photos…. Home server… hosted server…. Hmmmm

• 
  Kyngsly (@RelentlesslyK) reported 9 minutes ago

  @yettydlaw_ @MTNNG MTN will likely be able to explain it away... Anyway, this how Claude explained. "708GB over 104 days works out to about 6.8GB a day. That sounds shocking until you break down what actually eats data on a modern 5G phone. The usual culprits, roughly in order of how often they turn out to be the answer: Video, especially autoplay. TikTok, Instagram Reels, YouTube Shorts and X video. Scrolling Reels for two hours can burn 4 to 6GB on its own. “Social media and browsing” is exactly the usage profile that quietly does this. 5G itself. This one gets missed constantly. Video players negotiate bitrate based on available throughput. The same 30 minutes of YouTube that cost 300MB on 3G can cost 2GB on 5G because the player auto-selects a much higher resolution. Nothing changed in behavior, but consumption multiplied. Wi-Fi Assist / Adaptive Connectivity. iPhone and Android both silently fall back to cellular when Wi-Fi gets weak. The phone shows the Wi-Fi icon while pushing traffic over the mobile network. People assume they’ve been on Wi-Fi at home all evening when they haven’t. Cloud photo backup. iCloud Photos or Google Photos set to back up over cellular. A few 4K videos is several GB right there. Hotspot and tethering. A laptop pulling Windows updates, OneDrive or Dropbox sync, or a Zoom call. Also worth asking whether the SIM ever sits in a MiFi or router. Background refresh and auto-updates. App store updates over cellular, plus dozens of apps refreshing in the background. Video calls. WhatsApp video runs roughly 300MB an hour, Zoom or Meet more. On the operator side, real errors do happen: duplicate charging, subscription add-ons deducting from the bundle, or misapplied tariffs. But there’s also a structural point worth knowing. Carriers meter at the network layer, so they count protocol overhead and retransmissions, and in a poor RF environment retransmissions can add a real percentage on top of the payload the app thinks it sent. One practical note on that complaint: the app-level breakdown being demanded is hard for any carrier to produce. Traffic is encrypted end to end, so MTN can see volume, timing and destination IP or SNI, but not “3.2GB attributable to Instagram” in any reliable, retained form. The chronological deduction ledger and the subscription/add-on audit are the demands most likely to actually produce something. The fastest self-diagnosis is Settings > Cellular on iOS or Network & Internet > Data usage on Android, sorted by app, with the counter reset date checked. "

• 
  Lando, the Chef (@_Lando7763) reported 9 minutes ago

  @PhyxicxGaming Thanks. And unfortunately it's even worse than that because it's technically "shared housing;" the place was already a ******** when I got here. No pests, fortunately, and I'm pretty sure the landlord has no idea what goes on here, and doesn't care. I've only ever met the maintenance man, who handles move-ins, plus he picks up rent from the dropbox every week. I haven't seen him since the day I moved in, and he even told me as much that I'll never meet the owner. The psycho has his room on the 3rd floor, I'm one of two on the 2nd floor, and there's one person below me. The bathroom is shared, as is the kitchen, which I never use. Only one burner on the stove works anyway. On my first day, I texted about the broken toilet seat, and the Landlord asked me what happened. WTF? Third-Floor Psycho is the only other person who's walking around raging regularly. Everyone else recognizes the general "peace" of the environment. Unfortunately I have to be here at least a few more months, while I'm still paying off old bills, and re-establishing myself in a new city. It's a slow journey, but a steady one. I just happen to hit a ****** rest stop here and there.

• 
  OneToothTeXan (@OneToothTeXan) reported 10 minutes ago

  I'm so sorry I left my zipper down and my sanity got loose. If found: Men, there's a dropbox. Women: please return to original source.

• 
  Olivia Jane. 🦇 🗡️ 🩸 (@livtheripper) reported 14 minutes ago

  @HazeOfBlue84 Haha, I get it! Thankfully someone here at the office set it up and all I had to do was re-sync Dropbox! I had no issues at all, so I'm thankful.

• 
  Juan Pabro (@ironwoodreserve) reported 15 minutes ago

  @BitPaine @Dropbox Is now the worse time to try to login? I was a sent 2FN right as I was getting ready to click on what to use to login. It seemed way too fast for 2FN.

• 
  More Gravy (@lotsmoregravy) reported 15 minutes ago

  @FFT1776 Deputize our military and send them to literally every last damn polling station and dropbox in the United States of America. Every last damn one. Give them the authority to handle **** on the spot. Problem solved.

• 
  Noise (@NoiseesoiN) reported 17 minutes ago

  @esrtweet @EricRichards22 What's funny is that having gigabit on my end isn't the issue. It's connecting to servers which have enough bandwidth to feed it. My line can pull lots of data, but when I'm connecting to Dropbox, I'm lucky to get a third of that (and usually a tenth).

• 
  Karishma Bhardwaj (@bkarishma360) reported 17 minutes ago

  @shahzamannn_ Your SaaS idea doesn’t need to be complicated. Stripe moves money. Postman sends API requests. Notion organizes information. Dropbox syncs files. The lesson? Simple problem + huge market + great execution = massive company. Stop asking, “Is my idea too simple?” Start asking, “How many people have this problem?”

• 
  Bruce Perry (@bhrperry) reported 18 minutes ago

  @Levi_Borovychok Thumb drives can be cheap, but the cheap ones are often slow. It's worth thinking about where cloud storage is done. I believe Dropbox will let you store your files in the EU.

• 
  M.Ellis (@MEllisPhotograp) reported 20 minutes ago

  @DropboxSupport I think bulk of problem is on computer / desk top yes... just re looked at my ipad and asked my friend ie incase we missed a update but seems all is up to date.. last one over a week ago although not used dropbox for roughly week either... I will try 4g hot spot before i sleep.

• 
  Tibor Hudik (@htunlogic) reported 21 minutes ago

  @theonejvo Wispr is a rounding error. Drive, Dropbox, iCloud all sell "encrypted" while they hold the key. Then you paste the pile into Grok so the agent can just handle it. You did not get compromised. You volunteered. That is not E2EE. That is a slogan you paid for.

• 
  Polsia (@polsia) reported 23 minutes ago

  Dropbox treats an 80GB Unreal project like any other folder. Mid-previz, it chokes. Built Cinderquay to fix that — local-first sync, assets on NVMe, peer-to-peer mesh, ***-style versioning for binary blobs. Studios building worlds shouldn't pay egress to anyone. Live soon.

• 
  Guymon Adams (@guymonadams) reported 26 minutes ago

  @BrianRoemmele Man, this seems to be a recurring problem for Dropbox. I remember a similar story several years back about their own employees browsing thru user files. All the reasons I moved over to Sync, a much more secure and respectable alternative.

• 
  Eric Taylor (@bcs_erictaylor) reported 31 minutes ago

  Really?? Dropbox really needs a MCP server? CVE-2026-81102 The Dash MCP server bound its listener to the loopback address but never checked the host a request named. src/mcp_server_dash.py constructed the server for its network mode with the interface restricted to loopback and no transport-security settings, so a name that had been pointed at the loopback address still reached the listener while carrying the attacker's host name. A page in a visitor's browser could therefore drive the local server and invoke its company-search and file-detail tools under the Dropbox credential the server holds. Only the network mode was reachable this way; the standard input mode was not. The fix supplies transport-security settings that enable host checking and allow only the loopback name and port, rejecting other hosts before a tool runs. The repository publishes no versions, so the affected boundary is the commit preceding the fix.

• 
  The Redeemed Artist (@Peace_Grenade81) reported 34 minutes ago

  I know I'm just screaming into the void. And there's probably less than like one or 2% of users that actually use this function. But I'm going to do it anyway. For the longest time the X app beta was absolute garbage on Android. It had serious stability problems, I couldn't use voice to text properly, and I couldn't access my memes from Dropbox, my cloud provider. The most recent change fixed all of the other problems except for my Dropbox integration. At first, I blamed X for this but I have since come to learn that the real culprit is Google. If you go into your app section and look for cloud providers they give you all sorts of choices so long as you like the choice that is Google's. Theoretically, other providers should be in here like Box or Dropbox. But Google has been playing footsie making rules about cloud provider integration and not actually approving anyone else. Google has become Microsoft. Google will tell you what cloud provider to use and it will conveniently be their own. Google will continue to upgrade their operating system closing off any other provider options or applications they simply disagree with for any reason at all. Meanwhile what this means for me is that I can't insert any memes or videos because they are all stored on Dropbox. Yeah, yeah, yeah I could go into Dropbox and then click on a photo and then share it to X and then make a post out of it. But what I can't do is respond to a post and insert a picture or a video directly through the X app. Don't know when this gets fixed, if ever. But I think it's time for Google to be investigated for monopolistic practices. I realize that this doesn't affect many people, but if you think they aren't coming for your various conveniences, I'm pretty certain that that's going to be proven wrong. Since I can't post a meme but only a local photo, here's an unrelated picture of a quilt we bought at auction. 🙄

• 
  Sridhar Katakam (@srikat) reported 35 minutes ago

  @YannDecoopman How about putting the vault in Dropbox? Same problem as syncing with iCloud?

• 
  Mansi 👩‍💻 (@MansiCodez) reported 35 minutes ago

  Solution of yesterday’s question: Design Google Photos: the part after the boxes “Hash it and put it in S3” fails the interview. Two phones compress the same sunset differently. Same photo. Two hashes. Two rows. You just built a worse Dropbox. The system needs three IDs, not one. client_upload_id — generated on the device before the first byte moves content_hash — hash of the exact bytes you received asset_id — the thing the user sees in the library Uploads are sessions. Library entries are assets. Blobs are renditions. If you collapse those into one key, retries, edits, and shared albums all collide. 1. Retries must be idempotent on the client, not on the filename Phone goes offline mid-flight with 612 shots, 40 already half-uploaded. Each photo gets a client_upload_id the moment it enters the queue. Chunks are uploaded against that ID. Commit is PUT /uploads/{id}/complete. Same ID + same bytes → same session. Server returns the existing asset. Late packet after commit is a no-op. Filename + timestamp is not an ID. Camera roll and AirDrop will mint two. 2. Exact dupes are content-addressed. Near-dupes are reconciled. After commit: look up sha256(bytes) if it already exists for that user (or the shared album’s owner set), attach the new upload to the existing asset_id do not create a second photo The 28 shared “Goa 2026” shots that are almost-but-not-quite the library copies will miss on sha256. That is expected. Run a cheap perceptual hash (pHash / dHash) + capture time + camera model from EXIF. If distance is tiny and captured within a few seconds, mark as near_duplicate_of and do not show two tiles. Keep both blobs if you must; hide one in the UI. Two devices, two compressions, one photo in the grid. 3. The library is a set of assets + tombstones. Not last-write-wins. Delete in Delhi must beat a pending upload in Mumbai. Every mutation carries: asset_id op: upsert | delete | restore actor_id (device or user) logical_ts (per-actor Lamport or hybrid logical clock) A deleted asset gets a tombstone that outlives the pending queue. When the flight-mode phone finally flushes those 40 half-uploads, the server sees: upload commit for an asset that already has a newer delete → commit the blob if you want, do not resurrect the tile. Refresh in Mumbai cannot show a photo Delhi just deleted, because the change feed is “tombstone wins over delayed create,” not “whoever wrote last.” 4. Shared albums are references, not copies Partner adds 28 photos to Goa 2026. The album stores {asset_id, added_by, added_ts} — not a second blob, not a second library row. Adds and removes are a small CRDT: add(asset, actor, ts) remove(asset, actor, ts) Two devices adding the same asset = one membership row. Phone sync finishing a second later cannot wipe the partner’s 28 photos, because there is no “replace the whole album document.” Last-write-wins on the album JSON is how photos vanish. 5. An edit is a new rendition, not a new photo and not an overwrite User crops + filters while the original is still processing. Rules: original blob is immutable edit creates rendition_id with parent_asset_id library still shows one asset “current view” pointer moves to the latest rendition history is a list of renditions / edit ops, not 12 full-resolution copies by default If you overwrite the original, face clustering and search lose their source. If you mint a new asset, the user now has original + edit as two photos. Both are wrong. Storage stays sane because you store: original (once) derived thumbs / display sizes lazily, keyed by asset_id + transform not every intermediate crop as a first-class photo 6. Upload path and ML path must not share a lock “Beach sunset with Priya” in minutes, not overnight, also not on the upload critical path. Commit path only: durable bytes asset row appear in library + album enqueue jobs Workers (thumbs, embeddings, face cluster, labels) are async. Search index is eventually consistent. The UI can show the photo immediately with “processing” on faces. If clustering blocks upload, you built a spinner, not Photos. Face identity hangs off asset_id, so an edit does not orphan Priya. The new rendition inherits the parent’s cluster and gets re-checked, not reset. 7. Sync is a checkpoint + change feed, not “download the library” Each device stores last_applied_ts. Server gives a stream: new assets, new renditions, album membership, tombstones. That is how 62,000 existing photos plus 612 offline shots plus 28 shared adds converge without a full rescan, and why a deleted photo does not climb out of another device’s queue. The one-line design Client-generated upload IDs stop retries from cloning. Content hashes stop exact clones. Perceptual reconcile stops “same sunset, different JPEG.” Tombstones stop resurrection. Album CRDTs stop last-write-wins from deleting the partner’s night. Edits are renditions under one asset. ML is a consumer of commit, never part of it. Boxes for S3, CDN, Kafka, Redis are table stakes. This is the part that decides whether you designed Google Photos or a photo-shaped file dump.

• 
  하레 (@ascoeur9) reported 36 minutes ago

  I also experienced the same issue two months ago and reported it, but no action has been taken. In the end, I started syncing all the folders with Dropbox.

• 
  Craig O'Shea (@craig_os) reported 38 minutes ago

  @DropboxSupport major issue with your services right now.

• 
  WPBeginner (@wpbeginner) reported 38 minutes ago

  You built your WordPress site over months (or years). One bad plugin/theme update can wipe it all out overnight. 😱 Plugin conflicts. Malware. A botched migration. A hacked server. The disasters that take down WordPress sites usually happen without warning. And here's the mistake most site owners make: they think their hosting provider's backup is enough. It's NOT. If the server fails, you lose both your site and the backup. We share the complete step-by-step guide for backing up your WordPress site the right way. Here is what you will learn: ✅ Use a Backup Plugin (Best for Most People): @DuplicatorWP is what we use across our sites. Full-site backups, disaster recovery links, and restore without having the plugin pre-installed. Free version available, Pro has scheduled backups. ✅ Use Your Hosting Provider's Backup: SiteGround (where WPBeginner is hosted) includes manual and automated daily backups on all plans. Bluehost partners with CodeGuard and Jetpack for their built-in options. ✅ Manual Backup With cPanel or FTP: Use cPanel's Backup Wizard for a full backup, or connect via FileZilla FTP to download your wp-content, themes, plugins, and wp-config.php files directly. ✅ Send Backups to Cloud Storage: Duplicator and UpdraftPlus both connect natively to Google Drive, Dropbox, OneDrive, and Amazon S3. Never store backups on the same server as your website. If your host fails, both are gone. ✅ Set Up Automatic Scheduled Backups: Configure hourly, daily, weekly, or monthly backups in Duplicator based on how often you publish. eCommerce stores and busy blogs need daily. Slower-moving sites can get away with weekly. Ready to protect years of hard work with a proper WordPress backup system? Read the full ultimate step-by-step guide 👇 (Link is in the thread below)

• 
  Brandon (@BJohnsonxAR) reported 39 minutes ago

  @DropboxSupport I’m having issues logging in. When I try to login it’s making me sign up when I already have a paid account. This is happening on both the app and my browser. @Dropbox

• 
  Callitlikeitis (@Callittlikeitis) reported 40 minutes ago

  @iAnonPatriot Yeah no.. That’s even more piracy. I will Dropbox if it comes down to this drone diarrhea. Or better yet bypass lameazon all together

• 
  Christopher Bailey (@LexBaileyAI) reported 49 minutes ago

  @TetraspaceWest At Fitbit we hired a half dozen people from Jawbone who brought everything cleverly hidden in Dropbox. They got prosecuted. Decade later, companies kaput but Fable found it, processed it and now it’s intermixed in various *** repos and Huggingface. Is nVidia now in trouble?

• 
  Tony Sibert (@AiRiskBytes) reported 50 minutes ago

  ~5,000 Dropbox accounts were breached through Lenovo IDs the victims never created. Attackers registered 'verified' identities on other people's email addresses...the federated login did the rest. Your account is as strong as the weakest identity provider your platform trusts for you. Nobody asked the users. Do you know every IdP your SaaS vendors accept on your behalf?

• 
  Matt Mazur (@mhmazur) reported 51 minutes ago

  Day 2 of Claude autonomously shipping to my SaaS, including, for the first time, all night while I slept: The first day I had the hourly routine that kicked off this process end at 8pm so that if anything went awry, it could @ me in Slack and I'd quickly see the notification and dig in. The first day went smoothly, so I let it continue working overnight last night: every hour it would look for a small, safe change to make, ship it to ****, and monitor server logs and Sentry to make sure everything went well. A few other process improvements: - It now creates a PR for every change and links to it from its Slack summaries - Previously I only allowed it to make changes in 3 files max, but sometimes it identified the same issue spread across multiple locations, so it would have to spread that work over several hours; I bumped the limit to 8 files. - If I have uncommitted changes in main, it no longer blocks Claude's work; it moves them to a separate branch - Added a mandatory security review before pushing to ****. For these simple changes it's not that necessary, but it will be important for larger projects in the future. Specifically, I told it to run the default /security-review skill and if it flagged anything, to halt everything and wait for me to review. - Ran into a slight issue one hour where it ran that skill, the security review passed, and then it did nothing. I asked Claude to investigate, and it discovered it had run the skill in its main context window, which confused it into thinking its only job was the security review. It changed the process so the security review happens in a subagent, keeping the context window clean, which fixed things. - I asked it to maintain a ledger of things it needs me to do and to ping me every 24 hours if I haven't knocked them out. More and more, the agent is giving me things to do. - I told it to adopt the tone of TARS from Interstellar in its Slack updates going forward, cause why not. Here's a list of improvements it made on day 2: 1. Return 404s for bad case-study URLs 2. Extended the 404 fix site-wide 3. Removed stray code leaking into HTML 4. Fixed broken citation example in docs 5. Fixed wrong URL in sharing docs 6. Corrected false free-plan claim 7. Removed duplicate HTML attributes 8. Fixed dead links in embed docs 9. Fixed garbled copy on two pages 10. Pointed "paid plans" link at pricing 11. Added missing alt text to logo 12. Corrected a misleading code comment 13. Upgraded insecure links to HTTPS 14. Replaced dead testimonial link 15. Fixed broken example in Dropbox docs 16. Fixed awkward grammar on comparison page 17. Fixed reversed table of contents 18. Fixed missing Show More button 19. Matched nav label to its section 20. Corrected outdated visibility docs claim 21. Removed obsolete step from setup docs These can be categorized as: support-doc accuracy fixes (7), functional bug fixes (4), broken or insecure links (3), copy improvements (3), invalid markup (2), accessibility (1), and code hygiene (1). Excited to expand the scope of things I allow it to work on, but am going to wait until next week to ensure the current process is robust.

• 
  GHOST 🌙 (@ghosstty_) reported 54 minutes ago

  OPUS 5 + HIGGSFIELD CAN TURN A 6-QUESTION FORM INTO A $35K WEBSITE. IN ONE SESSION. FOR $4 IN TOKENS. no mockup. no wireframe. no mood board. six answers from the client. that's the input. a live website is the output. here's the form. here's what each question does. and here's why agencies charge $35K for what this produces in one session. → QUESTION 1: "WHO IS THIS SITE FOR?" not "describe your target audience in 500 words." one sentence. "CFOs at mid-size SaaS companies looking to switch billing providers." this one answer sets the tone, the copy angle, the visual weight, and the CTA hierarchy. an agency runs a two-hour discovery call to get this. I get it in a google form on monday. → QUESTION 2: "WHAT SHOULD A VISITOR DO?" book a demo. buy the product. join the waitlist. one action. this kills scope creep before it starts. no "maybe we should also add a blog and a careers page." one page. one goal. one conversion. → QUESTION 3: "SHARE 3 SITES YOU LIKE AND SAY WHY." not "what's your brand aesthetic?" nobody can answer that. "I like stripe because it's clean. I like linear because of the motion. I like notion because it feels simple." three links. three reasons. that's the design system seed. → QUESTION 4: "WHAT MAKES YOU DIFFERENT FROM COMPETITORS?" one paragraph. sometimes one sentence. this becomes the headline. the subhead. the entire above-the-fold story. a copywriter would interview the founder for an hour. this question does it in 30 seconds. → QUESTION 5: "SEND YOUR LOGO, BRAND COLOURS, AND ANY EXISTING ASSETS." a dropbox link. a google drive folder. sometimes just three hex codes and a png. this grounds the design in reality. no inventing a brand from scratch. no "let's explore some directions." → QUESTION 6: "WHEN DO YOU NEED IT LIVE?" not a timeline negotiation. a date. "next friday." done. that's when it ships. → WHAT HAPPENS NEXT friday night. six answers go into the pipeline. Opus 5 takes the answers and builds. design system. responsive layout. copy. CMS. all from the spec those six answers created. Higgsfield generates the hero media. product shots. clips. matched to the brand. saturday I review. adjust. polish. sunday morning - walkthrough link in the client's inbox. → WHY THIS WORKS because $35K was never the cost of building a website. it was the cost of figuring out what to build. discovery calls. alignment meetings. three directions. two rejected. scope changes. revision rounds. all of that is just a slow, expensive way of answering six questions. I ask the questions upfront. the client answers in 10 minutes. the machine builds from the answers. $4 in tokens. one session. same site. the full system - the form, the pipeline, the stack, and the pricing model - is in the article below. reply "FORM" and follow me - I'll send you the full playbook.

• 
  kayden (@codependentyaoi) reported 54 minutes ago

  @unprojection i think the issue was the site i was uploading my art to to link on ao3, i was using dropbox and it wouldn't link and then i saw some ppl on reddit say dropbox didnt work for them either, but i was able to find another website thankfully :]

• 
  Rituraj (@RituWithAI) reported 55 minutes ago

  🚨 Someone built a tool that checks if your email is registered on 120+ sites — without the sites ever knowing someone checked. No notifications sent. No login attempts logged. No alerts triggered. Silent. Invisible. Complete. It's called Holehe. 16,800 GitHub stars. And the technique behind it is what makes it different from every other email OSINT tool. Here's how most email checkers work — and why they fail. Standard approach: try to log in with the email and a fake password. If the error says "wrong password" — the account exists. If it says "account not found" — it doesn't. Problem: every login attempt gets logged. Every failed attempt triggers security alerts on accounts with 2FA. Some platforms lock accounts after repeated failed attempts. The target knows someone was checking. Holehe never attempts a login. Instead it uses the "forgot password" flow — the password reset mechanism that every platform exposes publicly. When you enter an email on a forgot password page, the platform has to check whether that email exists in its database. It tells you: "we sent a reset link" or "no account found." Holehe reads that response. Gets the answer. Never touches the login flow. Never triggers a security alert. Never logs an access attempt against the account. The platform confirms whether the email exists. The account owner never finds out anyone asked. Here's what 120+ platforms looks like in practice. Social media: Twitter, Instagram, Facebook, TikTok, Pinterest, Tumblr, Reddit. Professional: LinkedIn, GitHub, Freelancer, Fiverr. Dating: Tinder, Bumble, OkCupid, Badoo, Happn. Entertainment: Spotify, Netflix, Twitch, Steam, Epic Games, Deezer. Shopping: Amazon, eBay, Etsy, Zalando, AliExpress. Services: Airbnb, Uber, PayPal, Dropbox, Adobe. And 90+ more. Every registration checked silently. Here's the use case that makes people share this. Run your own email address. See every platform that comes back positive. Then run an email address you gave to a company that claimed they'd never share it. See if it's registered on data broker sites and marketing platforms you never signed up for. See where your email has been sold or leaked to. Here's what investigators actually use it for. Journalists verifying whether a source's claimed identity matches their digital footprint. Security researchers auditing their own exposure before a public disclosure. HR teams verifying whether candidate profiles match claimed backgrounds. And the obvious: anyone who needs to know whether a specific email address belongs to a real active person — without alerting that person. Here's the wildest part. It runs async — all 120+ platforms checked simultaneously. Results in seconds. And it exports clean JSON or CSV for integration into larger OSINT pipelines. Pair it with Blackbird (which takes the confirmed email and finds linked profiles), Sherlock (which takes usernames found in those profiles and searches 400+ platforms), and Maigret (which builds the full dossier) — and you have a complete four-tool OSINT pipeline from a single email address. One command to instal. Run it on your own email first. 16.8K GitHub stars. 1.7K forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  Matt Uribe (@MattUribe) reported 56 minutes ago

  I can't get my @bot to login to @dropbox . Anyone else having that issue. It's kind of a big deal for what I am trying to set up with my team. No matter what, it says too many attempts when I try using chrome on my bots screen. The plugin has no place to authenticate. Also I wish I could sign an email login to each bot. Seems we can only link one for the team using outlook. I guess that's why it beta. :)