Skip to content

Hostname

appliedbiosignals.com

Last fetched

appliedbiosignals.com resolves to 89.22.106.33, announced in 89.22.106.0/24 by ONE-NETWORK - dogado GmbH in DE. appliedbiosignals.com 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 · appliedbiosignals.comRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/appliedbiosignals.com

Resolution chain

IPv6 resolution

No AAAA record for appliedbiosignals.com is recorded in WhisperGraph.

Attribution

dogado

ORIGIN_AS

WHOIS identity

Registrar
iana:1239
Registrant organisation
applied biosignals
Contact emails
h.koetsier@ebiosig.com

Subdomains

Subdomain
mail.appliedbiosignals.com
mail2.appliedbiosignals.com
wildcard.appliedbiosignals.com
www.appliedbiosignals.com

Showing 4 of 4 subdomains (4 per page).

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

Sample outbound links

Mail and authentication

Nameservers

  • cns2.cloudpit.com
  • cns1.cloudpit.de
  • cns3.cloudpit.io
  • dns1alvo.dogado.net
  • dns2alvo.dogado.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

MX records

  • mx03.secure-mailgate.com
  • mx04.secure-mailgate.com

Threat-feed evidence

History

Related pages

Pivot from appliedbiosignals.com 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: "appliedbiosignals.com"})-[: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.