Skip to content

Hostname

ask.orkg.org

Last fetched

ask.orkg.org resolves to 194.95.114.28, announced in 194.94.0.0/15 by DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. in DE. ask.orkg.org 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 · ask.orkg.orgRouting diversity1.5/10Peering density7.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/ask.orkg.org

Resolution chain

IPv6 resolution

No AAAA record for ask.orkg.org is recorded in WhisperGraph.

Attribution

verein zur foerderung eines deutschen forschungsnetzes

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ask.orkg.org. 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
api.ask.orkg.org
federated.ask.orkg.org
mcp.ask.orkg.org
pb.ask.orkg.org
status.ask.orkg.org

Showing 5 of 5 subdomains (5 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

  • ns01.tib.eu
  • ns02.tib.eu
  • ns03.tib.eu
  • 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

  • a1122.mx.srv.dfn.de
  • b1122.mx.srv.dfn.de
  • c1122.mx.srv.dfn.de

SPF policy

  • ip: 194.95.114.0/26

Threat-feed evidence

History

Related pages

Pivot from ask.orkg.org 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: "ask.orkg.org"})-[: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.