Skip to content

Hostname

karamanguncel.com

Last fetched

karamanguncel.com resolves to 86.105.4.234, announced in 86.105.4.0/24 by MERT-TURKOGLU-DATAHOST-INTERNET-VE-BILISIM-TEKNOLOJILERI - MERT TURKOGLU trading as DATAHOST INTERNET VE BILISIM TEKNOLOJILERI in TR. karamanguncel.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 · karamanguncel.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/karamanguncel.com

Resolution chain

IPv6 resolution

No AAAA record for karamanguncel.com is recorded in WhisperGraph.

Attribution

mert turkoglu trading datahost ve bilisim teknolojileri

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:3826
Registrant organisation
this domain was caught by dropcatch.com
Contact emails
2018966@whoisprotection.biz, support@dropcatch.com

Subdomains

Subdomain
mail.karamanguncel.com
www.karamanguncel.com

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

  • eu.dnsenable.com
  • hostmaster.dnsenable.com
  • tr.dnsenable.com
  • us.dnsenable.com
  • ns1.datahost.net.tr
  • ns2.datahost.net.tr

MX records

  • karamanguncel.com
  • mail.karamanguncel.com

SPF policy

  • a: karamanguncel.com
  • mx: karamanguncel.com
  • include: relay.mailbaby.net
  • ip: 86.105.4.234

Threat-feed evidence

History

Related pages

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