Skip to content

Hostname

casestudies.interchanges.com

Last fetched

casestudies.interchanges.com resolves to 167.86.127.183, announced in 167.86.126.0/23 by CONTABO - Contabo GmbH in GB. casestudies.interchanges.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 · casestudies.interchanges.comRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint7.6/10canon.whisper.security/host/casestudies.interchanges.com

Resolution chain

IPv6 resolution

No AAAA record for casestudies.interchanges.com is recorded in WhisperGraph.

Attribution

contabo

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for casestudies.interchanges.com. 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
www.casestudies.interchanges.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • 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

SPF policy

  • ip: 216.27.17.128/28
  • include: icpbounce.com
  • a: casestudies.interchanges.com
  • mx: casestudies.interchanges.com
  • a: int5.interchanges.com
  • mx: int5.interchanges.com
  • ip: 108.168.204.14
  • ip: 169.47.206.116
  • ip: 169.48.142.219
  • ip: 173.193.152.199
  • ip: 50.23.14.6
  • ip: 70.86.95.18

Threat-feed evidence

History

Related pages

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