Skip to content

Hostname

twitburc.com.tr

Last fetched

twitburc.com.tr resolves to 104.21.21.236, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. twitburc.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 · twitburc.com.trRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint3.2/10canon.whisper.security/host/twitburc.com.tr

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrant organisation
zeynep turan ynce
Contact emails
twitburc@gmail.com

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

  • plato.ns.cloudflare.com
  • tina.ns.cloudflare.com

MX records

  • e.revotas.com
  • mx.yandex.net

SPF policy

  • ip: 95.108.130.0/23
  • ip: 37.140.190.0/23
  • ip: 5.45.198.0/23
  • ip: 95.108.205.0/24
  • ip: 185.93.250.0/24
  • ip: 185.93.251.0/24
  • ip: 77.88.28.0/24
  • ip: 77.88.29.0/24
  • ip: 185.157.40.0/24
  • ip: 176.236.94.0/24
  • ip: 5.45.224.0/25
  • ip: 178.154.239.136/29
  • ip: 178.154.239.144/28
  • ip: 51.250.56.144/28
  • ip: 51.250.56.16/28
  • ip: 178.154.239.200/29
  • ip: 178.154.239.208/28
  • ip: 2a02:6b8:0:1472::/64
  • ip: 2a02:6b8:0:1619::/64
  • ip: 2a02:6b8:0:1a2d::/64
  • ip: 2a02:6b8:0:801::/64
  • ip: 2a02:6b8:c00::/40
  • ip: 185.157.40.3/24
  • ip: 178.154.239.72/29
  • ip: 178.154.239.80/28
  • ip: 51.250.56.80/28
  • ip: 104.21.233.249
  • ip: 104.21.233.250
  • ip: 176.236.94.115
  • ip: 2606:4700:3038:0:0:0:6815:e9f9
  • ip: 2606:4700:3038:0:0:0:6815:e9fa
  • ip: 2a02:6b8:0:0:0:0:0:311
  • ip: 77.88.21.249

Threat-feed evidence

History

Related pages

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