NFT Allowlist Spot Checker
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
NFT Allowlist Spot Checker detects when the current page displays a wallet address—in the URL, in page text, or as a user-inputted address—then checks multiple blockchain explorers and NFT marketplaces to determine if that address is on any known allowlist for upcoming NFT drops. It displays all verified allowlist memberships and eligibility status in a clear, organized format, helping you quickly verify if you or others are eligible for NFT mints, presales, or exclusive drops.
WHERE IT RUNS
This tool works on any webpage that displays wallet addresses, including NFT minting pages, marketplace profiles, Discord embeds, Twitter profiles, project websites, and blockchain explorers. It automatically detects addresses in page content and URLs. The script runs on all websites as designated in its match patterns.
HOW TO USE
After installing the BotGentz extension, navigate to any page with wallet addresses. Click the NFT Allowlist Spot Checker icon in your browser toolbar or use the keyboard shortcut (Alt+N). The panel will open. Click "Connect Wallet" to connect your real EVM wallet extension (MetaMask, Coinbase Wallet, etc.)—this auto-detects and fills your wallet address. Alternatively, paste any address into the input field or click "Detect Address on Page" to automatically find addresses in the current page. Choose which chains to check (All Chains, Ethereum Mainnet, Polygon, Arbitrum, Optimism). Toggle whether to show only active allowlists. Click "Check Allowlist" to scan all configured providers. Results appear in the panel showing which allowlists the address is on, the project name, status, and chain. Copy results to your clipboard with the "Copy Results" button.
TECHNICAL SECTION — MULTI-PROVIDER ALLOWLIST AGGREGATION
Unlike simple allowlist checkers that query a single source, this tool uses a multi-provider aggregation engine. It simultaneously queries multiple allowlist APIs, blockchain explorers, and NFT marketplaces including OpenSea and LooksRare. For each configured chain, the engine performs parallel checks across providers, aggregating results into a unified view. The tool detects allowlist memberships through several mechanisms: direct allowlist API calls to services like allowlist.io, activity checks on marketplaces that reveal address holdings, and RPC-based contract reads when allowlists are stored on-chain. The aggregation layer deduplicates results and applies filtering based on your settings. This approach provides comprehensive coverage across the fragmented NFT allowlist landscape, where projects often use different providers or publish allowlists to different chains. The tool is capped at scanning all configured chains and providers within a reasonable timeframe.
THE PANEL
The panel is draggable anywhere on the screen and remembers its position per site. It can snap to the left, right, top, or bottom edges, or float freely. Collapse it to a small status indicator when you need more page visibility, and expand it again with a single click. Resize it vertically or horizontally to show more results. Press Escape to close the panel instantly. All settings (selected chain, auto-check, show active only) are saved globally and persist across sessions.
PLEASE NOTE
This tool requires the free BotGentz extension and a real EVM wallet extension already installed in your browser. EVM chains only—supports Ethereum Mainnet, Polygon, Arbitrum, and Optimism. Wallet connection is read-only; this tool never initiates transactions or signs messages. Cannot see private allowlists not published on-chain, cannot read wallet addresses that require user interaction beyond what is visible on the page, and cannot access allowlist data for chains that are not configured or block public RPC access. Websites change their layouts frequently; scripts may need updates, and we work to keep them current but cannot guarantee uninterrupted operation. Wallet addresses and allowlist data are processed locally and sent only to the configured RPC endpoints and allowlist APIs; your private keys are never exposed.