Skip to content

Hostname

borks.de

Last fetched

borks.de resolves to 194.164.55.137, announced in 194.164.48.0/20 by IONOS-AS - IONOS SE in DE. borks.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 · borks.deRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/borks.de

Resolution chain

IPv6 resolution

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

Attribution

ionos se

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for borks.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
analytics.borks.de
devel.borks.de
feriehus.borks.de
mail.borks.de
mxrelay.borks.de
owner.borks.de
portal.borks.de
remote.borks.de
secure.borks.de
ssl.borks.de
ssl2.borks.de
u003ewww.borks.de

Showing 12 of 13. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • nsa0.schlundtech.de
  • nsb0.schlundtech.de
  • nsc0.schlundtech.de
  • nsd0.schlundtech.de

MX records

  • borks-de.mail.protection.outlook.com
  • mxrelay.borks.de

SPF policy

  • include: spf.protection.outlook.com
  • a: borks.de
  • mx: borks.de
  • a: mxrelay.borks.de

Threat-feed evidence

History

Related pages

Pivot from borks.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: "borks.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.