Skip to content

Hostname

users.bitkeeper.org

Last fetched

users.bitkeeper.org resolves to 2 IPv4 addresses operated by AKAMAI-LINODE-AP Akamai Connected Cloud in US.

Nutrition Label

WHISPER CANON · users.bitkeeper.orgRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/users.bitkeeper.org

Resolution chain

users.bitkeeper.org resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
173.255.245.53173.255.240.0/20AS63949AKAMAI-LINODE-AP Akamai Connected CloudUS
216.218.207.89216.218.128.0/17AS6939HURRICANE - Hurricane Electric LLCUS

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

Distinct hostnames that link to or from users.bitkeeper.org in the public web crawl.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

  • users.bitkeeper.org

SPF policy

3 SPF mechanisms authorising senders for users.bitkeeper.org.

MechanismTarget
SPF_Ausers.bitkeeper.org
SPF_INCLUDE_spf.elasticemail.com
SPF_MXusers.bitkeeper.org

Related pages

Pivot deeper into the graph from users.bitkeeper.org.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "users.bitkeeper.org"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.