Hostname
bitek.net.id
Last fetched
bitek.net.id resolves to 104.21.60.82, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. bitek.net.id is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.60.82
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.194.61
172.67.192.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.2
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.2
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bitek.net.id. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| backbone.bitek.net.id |
| backupconfigs.bitek.net.id |
| ipam.bitek.net.id |
| mrtg.bitek.net.id |
| nperf.bitek.net.id |
| ns1.bitek.net.id |
| ns2.bitek.net.id |
| smtp.bitek.net.id |
| speedtest.bitek.net.id |
| www.bitek.net.id |
Showing 10 of 10 subdomains (10 per page).
Mail and authentication
Nameservers
- kia.ns.cloudflare.com
- yichun.ns.cloudflare.com
MX records
- bitek-net-id.mail.protection.outlook.com
SPF policy
- include: _spf.google.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from bitek.net.id into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bitek.net.id"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.