Skip to content

Hostname

hangisoru.com

Last fetched

hangisoru.com resolves to 185.149.101.17, announced in 185.149.101.0/24 by VERIDYEN - Veridyen Bilisim Teknolojileri Sanayi ve Ticaret Limited Sirketi in TR. hangisoru.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 · hangisoru.comRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/hangisoru.com

Resolution chain

IPv6 resolution

Attribution

veridyen bilisim teknolojileri sanayi ve ticaret sirketi

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:3826
Registrant organisation
domain admin
Contact emails
1217018@whoisprotection.biz, 2553277@whoisprotection.biz, 6584596@whoisprotection.biz

Subdomains

Subdomain
mail.hangisoru.com
ns2.hangisoru.com
testcoz.hangisoru.com
www.hangisoru.com

Showing 4 of 4 subdomains (4 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

  • dawn.ns.cloudflare.com
  • jerry.ns.cloudflare.com
  • ns1.guzelhosting.com
  • ns11.guzelhosting.com
  • ns12.guzelhosting.com
  • ns2.guzelhosting.com
  • ns1.veridyen.com
  • ns2.veridyen.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

  • hangisoru.com

SPF policy

  • include: _spf.protection.veridyen.com
  • include: relay.mailchannels.net

Threat-feed evidence

History

Related pages

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