Skip to content

Hostname

fotokoch.de

Last fetched

fotokoch.de resolves to 91.184.37.59, announced in 91.184.32.0/20 by SpeedPartner - SpeedPartner GmbH in DE. fotokoch.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 · fotokoch.deRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/fotokoch.de

Resolution chain

IPv6 resolution

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

Attribution

speedpartner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fotokoch.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
bilderwelt.fotokoch.de
chat.fotokoch.de
db1.fotokoch.de
db2.fotokoch.de
intranet.fotokoch.de
intranet2.fotokoch.de
jxvrhx.fotokoch.de
lb1.fotokoch.de
lb2.fotokoch.de
lb3.fotokoch.de
mail.fotokoch.de
mail2.fotokoch.de

Showing 12 of 25. 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

  • ns1.namemaster.de
  • ns2.namemaster.de
  • ns3.namemaster.de
  • ns4.namemaster.de
  • ns5.namemaster.de

MX records

  • mail.fotokoch.de
  • mail2.fotokoch.de
  • smtp-backup1.portunity.de
  • smtp-backup2.portunity.de

SPF policy

  • a: fotokoch.de
  • mx: fotokoch.de
  • a: mail.fotokoch.de
  • a: mail2.fotokoch.de
  • a: news.fotokoch.de
  • ip: 188.252.13.216
  • ip: 80.151.142.6
  • ip: 92.50.112.66

Threat-feed evidence

History

Related pages

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