Skip to content

Hostname

reeder.com.tr

Last fetched

reeder.com.tr is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. reeder.com.tr 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 · reeder.com.trRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/reeder.com.tr

Resolution chain

No IPv4 resolution is recorded for reeder.com.tr in WhisperGraph.

IPv6 resolution

WHOIS identity

Contact emails
info@reederebr.info

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • coby.ns.cloudflare.com
  • rachel.ns.cloudflare.com
  • 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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com
  • _dc-mx.628e2214330d.reeder.com.tr

SPF policy

  • ip: 188.132.212.195/1
  • ip: 188.132.212.222/1
  • include: _spf.anpdm.com
  • a: dx1194.dx3webs.com
  • mx: aspmx.l.google.com
  • mx: alt1.aspmx.l.google.com
  • mx: alt2.aspmx.l.google.com
  • mx: aspmx2.googlemail.com
  • mx: aspmx3.googlemail.com
  • mx: aspmx4.googlemail.com
  • mx: aspmx5.googlemail.com
  • a: reeder.com.tr
  • mx: reeder.com.tr

Threat-feed evidence

History

Related pages

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