How can we get the client's IP address in ASP.NET MVC C#?

Every machine on a network has a unique identifier called an IP address. Just as you would address a letter to send in the mail, computers use this unique identifier to send data to specific computers on a network. In ASP.NET MVC applications, you often need to retrieve the client's IP address for logging, security, or analytics purposes.

There are several methods to obtain a client's IP address in ASP.NET MVC C#. Each method has its own advantages and use cases depending on your application's architecture and hosting environment.

Using HttpRequest.UserHostAddress Property

The UserHostAddress property is the most straightforward method to get the client's IP address within a controller −

using System;
using System.Web.Mvc;

namespace DemoMvcApplication.Controllers
{
    public class HomeController : Controller
    {
        public ActionResult Index()
        {
            string ipAddress = Request.UserHostAddress;
            ViewBag.ClientIP = ipAddress;
            return View();
        }
        
        public string GetClientIP()
        {
            return Request.UserHostAddress;
        }
    }
}

Using UserHostAddress Outside Controllers

If you need to fetch the IP address outside a controller (in a helper class or service), you can use HttpContext.Current −

using System;
using System.Web;

namespace DemoMvcApplication.Helpers
{
    public static class IPHelper
    {
        public static string GetClientIPAddress()
        {
            if (HttpContext.Current != null)
            {
                string ipAddress = HttpContext.Current.Request.UserHostAddress;
                return ipAddress;
            }
            return "Unknown";
        }
        
        public static void LogClientIP()
        {
            string clientIP = GetClientIPAddress();
            Console.WriteLine($"Client IP: {clientIP}");
        }
    }
}

Using ServerVariables Method

The ServerVariables collection provides an alternative approach using the REMOTE_ADDR variable −

using System;
using System.Web.Mvc;

namespace DemoMvcApplication.Controllers
{
    public class HomeController : Controller
    {
        public ActionResult Index()
        {
            string ipAddress = Request.ServerVariables["REMOTE_ADDR"];
            ViewBag.ClientIP = ipAddress;
            ViewBag.Method = "ServerVariables";
            return View();
        }
        
        public string GetIPViaServerVars()
        {
            return Request.ServerVariables["REMOTE_ADDR"] ?? "Not Available";
        }
    }
}

Handling Proxy and Load Balancer Scenarios

When your application runs behind a proxy or load balancer, you need to check additional headers to get the real client IP −

using System;
using System.Web.Mvc;

namespace DemoMvcApplication.Controllers
{
    public class HomeController : Controller
    {
        public string GetRealClientIP()
        {
            string ipAddress = Request.ServerVariables["HTTP_X_FORWARDED_FOR"];
            
            if (string.IsNullOrEmpty(ipAddress) || ipAddress.ToLower() == "unknown")
            {
                ipAddress = Request.ServerVariables["HTTP_X_REAL_IP"];
            }
            
            if (string.IsNullOrEmpty(ipAddress) || ipAddress.ToLower() == "unknown")
            {
                ipAddress = Request.UserHostAddress;
            }
            
            // Handle multiple IPs (comma-separated)
            if (!string.IsNullOrEmpty(ipAddress) && ipAddress.Contains(","))
            {
                ipAddress = ipAddress.Split(',')[0].Trim();
            }
            
            return ipAddress ?? "Unknown";
        }
    }
}

Comparison of Methods

Output

When running the application locally, the IP address will typically show as ::1 (IPv6 loopback) or 127.0.0.1 (IPv4 loopback). The name localhost normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6 loopback address ::1.

Client IP: ::1
Method: UserHostAddress

Conclusion

Getting a client's IP address in ASP.NET MVC can be achieved through multiple methods. For simple applications, Request.UserHostAddress works well, but for production environments with proxies or load balancers, checking additional headers like X-Forwarded-For ensures you get the real client IP address.