Skip to content

Hostname

corlu.bel.tr

Last fetched

corlu.bel.tr resolves to 213.14.20.213, announced in 213.14.20.0/24 by TELLCOM-AS - Superonline Iletisim Hizmetleri A.S. in TR. corlu.bel.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 · corlu.bel.trRouting diversity2.4/10Peering density9.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/corlu.bel.tr

Resolution chain

IPv6 resolution

No AAAA record for corlu.bel.tr is recorded in WhisperGraph.

Attribution

superonline iletisim hizmetleri

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for corlu.bel.tr. 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
bim.corlu.bel.tr
cbs.corlu.bel.tr
imsva.corlu.bel.tr
kariyer.corlu.bel.tr
mail.corlu.bel.tr
ns1.corlu.bel.tr
ns2.corlu.bel.tr
owa.corlu.bel.tr
www.corlu.bel.tr

Showing 9 of 9 subdomains (9 per page).

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

  • 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
  • ns1.corlu.bel.tr
  • ns2.corlu.bel.tr

MX records

  • imsva.corlu.bel.tr

SPF policy

  • a: corlu.bel.tr
  • mx: corlu.bel.tr
  • a: imsva.corlu.bel.tr
  • ip: 213.14.20.199

Threat-feed evidence

History

Related pages

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