Hostname
bitiba.nl
Last fetched
bitiba.nl resolves to 18.245.46.124, announced in 18.245.44.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. bitiba.nl 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
- 18.245.46.124
18.245.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.245.46.43
18.245.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.245.46.67
18.245.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.245.46.87
18.245.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.162.38.106
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.162.38.68
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.162.38.86
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.162.38.94
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.175.246.9
- 3.175.246.50
- 3.175.246.67
- 3.175.246.101
IPv6 resolution
No AAAA record for bitiba.nl is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:key-systems gmbh
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-282.awsdns-35.com
- ns-922.awsdns-51.net
- ns-1251.awsdns-28.org
- ns-1870.awsdns-41.co.uk
MX records
- mail02.mail-gw.de
- mail03.mail-gw.de
SPF policy
- ip: 62.209.48.170/32
- include: amazonses.com
- include: spf.mailjet.com
- include: spf.protection.outlook.com
- include: fdspfeuc.freshemail.io
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from bitiba.nl 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: "bitiba.nl"})-[: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.