Hostname
murka.com
Last fetched
murka.com resolves to 38.73.229.136, announced in 38.0.0.0/8 by COGENT-174 - Cogent Communications, LLC in CY. murka.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
- 38.73.229.136
38.0.0.0/8 · COGENT-174 - Cogent Communications, LLC · Limassol, CY
- 38.73.231.135
38.0.0.0/8 · COGENT-174 - Cogent Communications, LLC · Limassol, CY
- 38.73.231.136
38.0.0.0/8 · COGENT-174 - Cogent Communications, LLC · Limassol, CY
- 38.73.229.211
38.0.0.0/8 · COGENT-174 - Cogent Communications, LLC · Limassol, CY
- 38.73.229.212
38.0.0.0/8 · COGENT-174 - Cogent Communications, LLC · Limassol, CY
- 38.73.231.215
38.0.0.0/8 · COGENT-174 - Cogent Communications, LLC · Limassol, CY
IPv6 resolution
No AAAA record for murka.com is recorded in WhisperGraph.
Attribution
cogent
ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domain administrator
- Contact emails
- 6yantq8m4oq84fhpge3@privacyyes.com, domains@murka.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
- ns1.fsticks.net
- ns2.fsticks.net
- ns3.fsticks.net
- ns4.fsticks.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- mx: mail.helpshift.com
- include: mail.zendesk.com
- a: smtp-relay.fsticks.net
- include: 6381084.spf05.hubspotemail.net
- include: transmail.net
Threat-feed evidence
History
Related pages
Pivot from murka.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: "murka.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.