req.ip and req.hostname in Express - Performance & Optimization

Performance: req.ip and req.hostname

LOW IMPACT

Accessing req.ip and req.hostname affects server-side request handling speed and can impact response time if used inefficiently.

Extract client IP and hostname efficiently in Express middleware

Express

app.use((req, res, next) => {
  req.clientIp = req.ip;
  req.clientHostname = req.hostname;
  // Avoid DNS lookup or perform async caching if needed
  next();
});

Avoids blocking operations; uses Express built-in properties directly for fast access.

📈 Performance GainNon-blocking, immediate access with zero added latency

Extract client IP and hostname efficiently in Express middleware

Express

app.use((req, res, next) => {
  const ip = req.ip;
  const hostname = req.hostname;
  // Synchronous DNS lookup for hostname
  const dns = require('dns');
  let address;
  try {
    address = dns.lookupSync(hostname);
  } catch (err) {
    return next(err);
  }
  req.resolvedAddress = address;
  next();
});

Synchronous or blocking DNS lookups on req.hostname delay response and block event loop.

📉 Performance CostBlocks event loop during DNS lookup, increasing response time by 50-200ms depending on network

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Access req.ip and req.hostname directly	N/A (server-side)	N/A	N/A	[OK] Good
Perform synchronous DNS lookup on req.hostname	N/A	N/A	N/A	[X] Bad

Rendering Pipeline

On the server, accessing req.ip and req.hostname happens during request processing before response is sent. It does not affect browser rendering but impacts server response time.

→Request Handling

→Response Preparation

⚠️ BottleneckBlocking synchronous operations based on req.hostname (e.g., DNS lookups)

Optimization Tips

1Access req.ip and req.hostname directly without blocking operations.

2Avoid synchronous DNS lookups during request processing.

3Cache any hostname resolutions asynchronously to prevent delays.

Performance Quiz - 3 Questions

What is the main performance risk when using req.hostname in Express middleware?

A Increasing DOM nodes on the client

B Performing synchronous DNS lookups blocking the event loop

C Triggering browser reflows

D Adding large CSS files

DevTools: Network

How to check: Open DevTools Network panel, inspect server response times for requests, and look for increased latency caused by middleware.

What to look for: Long server response times or waterfall delays indicating blocking operations during request processing

Practice

1. What does req.ip represent in an Express app?

easy

A. The visitor's IP address

B. The domain name used in the request

C. The server's IP address

D. The HTTP method of the request

Solution

1. Step 1: Understand the purpose of req.ip

   req.ip provides the IP address of the client making the request.

2. Step 2: Differentiate from req.hostname

   req.hostname gives the domain name, not the IP address.

3. Final Answer:

   The visitor's IP address -> Option A

4. Quick Check:

   req.ip = visitor's IP [OK]

Hint: Remember: IP is address, hostname is domain name [OK]

Common Mistakes:

• Confusing req.ip with req.hostname
• Thinking req.ip is server IP
• Assuming req.ip gives HTTP method

2. Which of the following is the correct way to access the hostname in an Express route handler?

easy

A. req.host

B. req.domain

C. req.hostname

D. req.hostName

Solution

1. Step 1: Recall Express request object properties

   The correct property for the domain name is req.hostname.

2. Step 2: Check other options for validity

   req.host, req.domain, and req.hostName are not valid Express properties.

3. Final Answer:

   req.hostname -> Option C

4. Quick Check:

   Hostname property = req.hostname [OK]

Hint: Hostname is all lowercase: req.hostname [OK]

Common Mistakes:

• Using req.host instead of req.hostname
• Capitalizing property names incorrectly
• Assuming req.domain exists

3. Consider this Express route handler: <pre>app.get('/', (req, res) => { res.send(`IP: ${req.ip}, Hostname: ${req.hostname}`); }); If a user visits http://example.com from IP 192.168.1.5, what will be the response text?

medium

A. IP: undefined, Hostname: example.com

B. IP: example.com, Hostname: 192.168.1.5

C. IP: 127.0.0.1, Hostname: localhost

D. IP: 192.168.1.5, Hostname: example.com

Solution

1. Step 1: Identify req.ip and req.hostname values

   req.ip gives the visitor's IP, which is 192.168.1.5. req.hostname gives the domain, which is example.com.

2. Step 2: Substitute values into the response string

   The response string becomes: IP: 192.168.1.5, Hostname: example.com.

3. Final Answer:

   IP: 192.168.1.5, Hostname: example.com -> Option D

4. Quick Check:

   IP and hostname match request info [OK]

Hint: Match IP to visitor, hostname to domain in response [OK]

Common Mistakes:

• Swapping IP and hostname values
• Assuming localhost IP instead of visitor IP
• Using undefined or wrong properties

4. You wrote this Express middleware: <pre>app.use((req, res, next) => { console.log(req.ipAddress); next(); }); What is the problem with this code?

medium

A. Middleware must be declared after routes

B. req.ipAddress is not a valid property; should use req.ip

C. Logging should be done with res.ip instead

D. Missing call to next() to continue middleware chain

Solution

1. Step 1: Check property names on req

   req.ipAddress does not exist in Express; the correct property is req.ip.

2. Step 2: Verify middleware correctness

   The middleware calls next(), so chain continues correctly.

3. Final Answer:

   req.ipAddress is not a valid property; should use req.ip -> Option B

4. Quick Check:

   Use req.ip for IP address [OK]

Hint: Use exact property names: IP is req.ip [OK]

Common Mistakes:

• Using req.ipAddress instead of req.ip
• Forgetting to call next()
• Trying to log IP from res object

5. You want to restrict access to your Express app only to requests coming from the domain trusted.com. Which code snippet correctly uses req.hostname to allow this?

hard

A. app.use((req, res, next) => { if (req.hostname === 'trusted.com') next(); else res.status(403).send('Forbidden'); });

B. app.use((req, res, next) => { if (req.ip === 'trusted.com') next(); else res.status(403).send('Forbidden'); });

C. app.use((req, res, next) => { if (req.host === 'trusted.com') next(); else res.status(403).send('Forbidden'); });

D. app.use((req, res, next) => { if (req.hostname.includes('trusted.com')) next(); else res.status(403).send('Forbidden'); });

Solution

1. Step 1: Use req.hostname to check exact domain

   app.use((req, res, next) => { if (req.hostname === 'trusted.com') next(); else res.status(403).send('Forbidden'); }); correctly compares req.hostname to the string 'trusted.com'.

2. Step 2: Evaluate other options for correctness

   app.use((req, res, next) => { if (req.ip === 'trusted.com') next(); else res.status(403).send('Forbidden'); }); wrongly compares req.ip to a domain string. app.use((req, res, next) => { if (req.host === 'trusted.com') next(); else res.status(403).send('Forbidden'); }); uses invalid req.host. app.use((req, res, next) => { if (req.hostname.includes('trusted.com')) next(); else res.status(403).send('Forbidden'); }); uses includes which may allow subdomains, not exact match.

3. Final Answer:

   Option A code snippet -> Option A

4. Quick Check:

   Exact match with req.hostname = app.use((req, res, next) => { if (req.hostname === 'trusted.com') next(); else res.status(403).send('Forbidden'); }); [OK]

Hint: Check exact domain with req.hostname === 'domain' [OK]

Common Mistakes:

• Comparing IP to domain string
• Using invalid property req.host
• Using partial match instead of exact domain