This document provides examples of how to use the API Resource Availability Bot and common use cases.
Input:
https://github.com
Output:
π Detailed Scan Report
π― Target: https://github.com
π Time: 2026-01-24 12:00:00
π Availability:
Status: AVAILABLE
Message: Resource is accessible
Response Time: 0.234s
π DNS Information:
IPv4: 140.82.121.4
IPv6: 2606:50c0:8000::153
CNAME: None
π Protocol & Security:
Protocol: HTTPS
SSL/TLS: β
Enabled
SSL Version: TLSv1.3
HTTP Version: HTTP/2
π° Paywall Detection:
Status: π’ None
π‘οΈ Security Status:
Status: SECURE
Overall Score: 95/100
Vulnerabilities: 0
Input:
https://api.github.com/users/octocat
Output:
Target: https://api.github.com/users/octocat
Status: π’ Available
Response Time: 0.156s
Protocol: HTTPS
SSL/TLS: β
Enabled
Primary IP: 140.82.121.6
Paywall: π’ None
Security: β
Secure (98/100)
Input:
https://www.nytimes.com/2024/01/article
Output:
Status: π Authentication Required
Paywall: π΄ Detected (85% confidence)
Type: Metered paywall
Security: β
Secure
- Scan first resource:
https://api.openai.com
-
Click "π Bookmark"
-
Scan next resource:
https://httpbin.org
-
Click "π Bookmark"
-
View all bookmarks:
/bookmarks
Send /bookmarks to see all saved resources with their current status:
π Your Bookmarks (5)
π’ OpenAI API
π’ HTTPBin
π΄ Example Service (Timeout)
π’ GitHub API
π’ Google
Click any bookmark to rescan and get updated information.
Scenario: You manage several APIs and want to monitor their availability.
Steps:
- Scan each API endpoint
- Bookmark them all
- Use
/bookmarksfor quick status overview - Click "π Refresh All" to update all statuses
- Check
/statsto see scan history
Example APIs to monitor:
https://api.github.com
https://api.openweathermap.org
https://jsonplaceholder.typicode.com
https://dog.ceo/api/breeds/list/all
Scenario: Check if a service supports multiple protocols.
URLs to test:
http://example.com
https://example.com
ftp://ftp.example.com
Compare the results to see:
- Which protocols are available
- SSL/TLS versions
- HTTP version support (HTTP/1.1, HTTP/2, HTTP/3)
Scenario: Perform basic security check on your website.
What the bot checks:
- β SSL certificate validity
- β Security headers (HSTS, CSP, X-Frame-Options, etc.)
- β SSL/TLS version
- β Server information disclosure
- β Common vulnerabilities
Example:
https://yourwebsite.com
Review the security score and recommendations.
Scenario: Verify if your service is accessible from different regions.
Note: The bot scans from your server's location. For multi-region testing, deploy multiple bot instances in different regions.
What to check:
- Status: AVAILABLE vs REGION_BLOCKED
- Response times (latency)
- Content differences
Scenario: Research which sites use paywalls and what type.
Test different sites:
https://www.wsj.com
https://www.nytimes.com
https://medium.com/@user/article
The bot detects:
- Hard paywalls (402 Payment Required)
- Soft paywalls (registration walls)
- Metered paywalls (limited free articles)
Scenario: Investigate DNS configuration of a domain.
What you get:
- A records (IPv4)
- AAAA records (IPv6)
- CNAME (aliases)
- NS (nameservers)
- MX (mail servers)
- TXT records
- Resolution time
Example:
https://github.com
Perfect for troubleshooting DNS issues or verifying configurations.
Configure the bot for your workflow:
-
Detailed Reports (Default: ON)
- ON: Full detailed reports with all information
- OFF: Compact table view
-
Auto Bookmark (Default: OFF)
- ON: Automatically bookmark every scanned URL
- OFF: Manual bookmarking
-
Notifications (Default: ON)
- ON: Get alerts for bookmark status changes
- OFF: Quiet mode
View past scans for any URL:
- Scan a URL multiple times over different periods
- Click "π Logs" button
- See history of all scans with timestamps and status changes
Use case: Track website uptime over time
Scan History for: https://api.example.com
1. 2026-01-24 12:00:00
Status: AVAILABLE
2. 2026-01-24 06:00:00
Status: TIMEOUT
3. 2026-01-23 18:00:00
Status: AVAILABLE
Share scan results with team members:
- Scan a URL
- Click "π€ Share" button
- Select a chat or person
- Bot sends the URL for them to scan
| Status | Meaning | Action |
|---|---|---|
| π’ AVAILABLE | Resource is online and accessible | None needed |
| π΄ UNAVAILABLE | Resource is offline or unreachable | Check if down for everyone or just you |
| π AUTH_REQUIRED | Authentication needed | Verify credentials |
| π REGION_BLOCKED | Blocked by region | Use VPN or check geo-restrictions |
| π« IP_BLOCKED | Your IP is blocked | Contact administrator |
| β±οΈ TIMEOUT | Request timed out | Resource is slow or filtering requests |
| β ERROR | Unexpected error | Check URL format |
| Score | Grade | Meaning |
|---|---|---|
| 90-100 | A | Excellent security |
| 75-89 | B | Good security |
| 50-74 | C | Adequate security |
| 25-49 | D | Poor security |
| 0-24 | F | Critical issues |
| Time | Rating |
|---|---|
| < 0.1s | Excellent |
| 0.1-0.5s | Good |
| 0.5-1s | Average |
| 1-3s | Slow |
| > 3s | Very slow |
View your scanning statistics:
/stats
Output:
π Your Statistics
π Total Bookmarks: 12
π Total Scans: 156
π― Most Scanned: https://api.github.com
(23 times)
What you can learn:
- How many resources you're monitoring
- Your most-checked services
- Total scanning activity
- Bookmark all your critical services
- Each morning, use
/bookmarks - Click "π Refresh All"
- Get instant status overview
Before deploying changes:
- Scan your staging environment
- Verify all endpoints return 200
- Check security score
- Compare with production scan
Scan all API endpoints documented:
- Create bookmark for each endpoint
- Test regularly to ensure they're working
- Use scan history to track uptime
Bookmark your critical services and use /bookmarks for instant visual status (π’/π΄).
Scan both HTTP and HTTPS versions to see differences in security and performance.
Scan the same URL weekly and compare security scores over time.
Scan repeatedly to see if API implements rate limiting.
If a site is slow, check DNS resolution time first.
Review missing security headers and implement them on your own sites.
Test with different user agents (future feature) to see paywall variations.
Use descriptive titles when bookmarking (future feature) to organize better.
Q: Can I scan localhost? A: Not directly. The bot runs on a server and can't access your local machine.
Q: How often can I scan? A: The bot has rate limiting (default: 10 scans per minute). Adjust in config if needed.
Q: Why do some DNS records show empty? A: Not all domains have all record types (IPv6, MX, TXT, etc.).
Q: Can I scan non-HTTP protocols? A: Currently supports HTTP, HTTPS, FTP detection. More protocols coming soon.
Q: Is my data private? A: Yes! All scans run from your bot instance. No data sent to third parties.
Q: Can I scan IP addresses? A: Yes! Send the IP directly:
192.168.1.1
8.8.8.8
Q: Why is paywall detection not 100% accurate? A: Paywall detection uses heuristics and keyword matching. Some paywalls are sophisticated and may not be detected.
Q: Can I export my bookmarks? A: Currently stored in SQLite database. Export feature coming in future update.
Need more examples? Try these URLs:
https://httpstat.us/200
https://httpstat.us/500
https://httpstat.us/timeout
https://api.ipify.org
https://dog.ceo/api/breeds/image/random
Each will demonstrate different aspects of the bot's capabilities!