A friendly technical robotmapping the public internet.
VikiTronBot is the crawler behind the tools on vikitron.com. It continuously observes the technical fabric of the public internet — DNS, TLS certificates, robots.txt, HTTP metadata — and turns those observations into free diagnostic tools and a public API. This page is the contract: what we do, what we never touch, how to block us, and how to reach a human.
Public User-Agent·Respects robots.txt·Contact published·Public data only
Why we crawl.
The public internet is shared infrastructure. Every day it changes — new domains appear, certificates rotate, DNS moves, TLS versions age out, misconfigurations creep in. We watch that change so anyone — security researchers, sysadmins, curious webmasters — can look up the technical state of a domain in one place, for free. We keep no secrets about ourselves, so you can decide whether to welcome us or block us with a single line in your robots.txt.
What VikiTronBot looks at.
All of it is data your server would return to any anonymous visitor from the open internet.
DNS records
A, AAAA, MX, NS, TXT, CNAME resolved from public resolvers.
robots.txt
Fetched and parsed to decide what we may crawl and what we must skip.
TLS certificates
From the public TLS handshake and Certificate Transparency logs.
HTTP metadata
Response headers, status codes and reverse-DNS — never response bodies with personal data.
Our commitment.
A short list. The "never" side is the one worth reading twice.
We do
- • Identify ourselves in every request via a public User-Agent that links back to this page.
- • Honour
robots.txt,noindexandnofollowfor every route. - • Rate-limit ourselves per host and back off exponentially on errors.
- • Publish contact addresses and IP ranges (see below) so you can block, throttle or whitelist us at any layer.
- • Reply to abuse and technical questions from a real human.
We never
- • Cross authentication boundaries — no login walls, no session cookies, no gated content.
- • Read or store data submitted through forms.
- • Collect personal information (names, emails, addresses) from page bodies.
- • Attempt to bypass rate limits, firewalls, WAFs or CAPTCHAs.
- • Sell your data. The observations we make available are technical facts about public infrastructure.
How VikiTronBot behaves on your server.
Politeness is the whole point. A crawler that hurts servers gets blocked, and a blocked crawler learns nothing.
Adaptive rate
Default 1–2 requests per second per host. Slower for smaller sites, faster for CDN-fronted ones — driven by response time.
Exponential backoff
Errors, 429s or timeouts trigger backoff. Max 3 retries before we give the host a longer rest.
Off-hours preferred
Where possible, scheduled sweeps land in the target region's off-peak window.
Change-driven
Stable records are re-checked less often. Recently changed data (new certificate, moved DNS) gets picked up quickly.
How to identify VikiTronBot in your logs.
VikiTronBot/1.0 (+https://vikitron.com/bot)The URL in the parentheses always points back to this page. If a request claims to be from us but points elsewhere, it isn’t us.
abuse@bizkithub.com— DMCA takedowns, delisting requests, anything urgent.support@bizkithub.com— technical questions, rate-limit adjustments, whitelisting help.
Both mailboxes are read by a person and answered within two business days.
We’re preparing a machine-readable CIDR list at https://vikitron.com/.well-known/ip-ranges.json (coming soon). For now, ask us at support@bizkithub.com and we’ll send the current ranges so you can whitelist us at the network layer.
How to block, throttle or delist.
Any of these takes effect on our next visit — usually within an hour, always within a day.
Block us entirely
Add this to your robots.txt:
User-agent: VikiTronBot Disallow: /
Just slow us down
We honour Crawl-delay:
User-agent: VikiTronBot Crawl-delay: 10
Protect sensitive paths
Combine Disallow with server-level auth (401/403). robots.txt is a request, not enforcement — a real lock belongs on the door.
Delist existing data
Email abuse@bizkithub.com with the affected domain or IP. We’ll purge our records and add the target to our exclusion list.
Not sure whether your robots.txt actually blocks us?
Test it in our checkerIs that request really us?
User-Agent strings can be spoofed. Two ways to verify.
1. Reverse-DNS + forward-DNS
Run reverse DNS on the source IP — it will resolve to a hostname under *.vikitron.com. Then resolve that hostname forward; the address must match. If either step fails, it’s not us.
2. Verification token
On request, we can fetch a token you place at:
https://example.com/.well-known/vikitron-verify.txtAsk support@bizkithub.com for a fresh token and we’ll fetch it live so you can watch it happen in your logs.
Anything this page didn’t cover?
Visit support portal