Hostname
mangamac.com
Last fetched
mangamac.com resolves to 31.186.11.113, announced in 31.186.11.0/24 by TURKTICARET-AS1 - TURKTICARET.NET YAZILIM HIZMETLERI SAN. ve TIC. A.S. in TR. mangamac.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for mangamac.com is recorded in WhisperGraph.
Attribution
turkticaret net yazilim hizmetleri san ve tic
ORIGIN_AS
WHOIS identity
- Registrar
- iana:819
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- gdpr-masking@gdpr-masked.com, 17b19750b4d2851948660e80168a812cf43b181aca0dbad3b2c7aa32de4ab385@mangamac.com.whoisproxy.org, 642b4f5cf17dfb7a947c103f03a746ed686c5abcdaafff65c32c182889c619c5@mangamac.com.whoisproxy.org, 808503de6c597d219c7b127f707ad02b218f535666acc80d2aaea542cbbfebf3@mangamac.com.whoisproxy.org, cbab6bfcf5516be4744f1a7665eb3afe57a8df638bf9466b48251cc1696b3aae@mangamac.com.whoisproxy.org, d71482e2adf7d33d9f5332bfbda10e7036a896d4c0afaaf472fc1b1a2cd5f525@mangamac.com.whoisproxy.org, db5ecb31e4491e71f1ee2d3211217c67d0840f6328b9f8517a46e17a76b94929@mangamac.com.whoisproxy.org, fc9deb2f865ec7fc4115ed17295e2fd2bb6751deb6483871297fd901a925ceb4@mangamac.com.whoisproxy.org, fde3114d830e69ef15cd0b1538fcd392e66b1973a59dc869b49039cb84623088@mangamac.com.whoisproxy.org
Subdomains
| Subdomain |
|---|
| www.mangamac.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns1.turkticaret.net
- ns2.turkticaret.net
- ns3.turkticaret.net
MX records
- mx.turkticaret.net
SPF policy
- include: _spf.turkticaret.net
Threat-feed evidence
History
Related pages
Pivot from mangamac.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: "mangamac.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.