Skip to content

Hostname

biccloud.de

Last fetched

biccloud.de resolves to 80.158.92.104, announced in 80.158.92.0/24 by AS6878 - T-Systems International GmbH in DE. biccloud.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · biccloud.deRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/biccloud.de

Resolution chain

IPv6 resolution

No AAAA record for biccloud.de is recorded in WhisperGraph.

Attribution

international

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for biccloud.de. 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
aduno.biccloud.de
api.biccloud.de
azure.biccloud.de
caritas.biccloud.de
dzbank.biccloud.de
erp.biccloud.de
fh-erfurt.biccloud.de
gag-immobilien.biccloud.de
grc.biccloud.de
gsi.biccloud.de
hipp.biccloud.de
hspv-nrw.biccloud.de

Showing 12 of 53. View all subdomains →

Mail and authentication

Nameservers

  • ns-281.awsdns-35.com
  • ns-672.awsdns-20.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1189.awsdns-20.org
  • ns-1555.awsdns-02.co.uk

MX records

  • biccloud-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from biccloud.de 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: "biccloud.de"})-[: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 20

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