Update result

fabaff · fabaff · commit cb5bcae9d3dc · 2018-05-29T18:18:44.000+02:00
diff --git a/source/_docs/frontend/webserver.markdown b/source/_docs/frontend/webserver.markdown
@@ -15,25 +15,27 @@ It was only a matter of time until the first queries for tools like [https://www
 To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [nmap device tracker](/components/device_tracker/). 
 
 ```bash
-$ nmap -sV -p 8123 --script=http-title,http-headers 192.168.1.3
+$ nmap -sV -p 8123 --script=http-title,http-headers 192.168.0.3
+
+Starting Nmap 7.60 ( https://nmap.org ) at 2018-05-29 18:16 CEST
+Nmap scan report for 192.168.0.3
+Host is up (0.0058s latency).
 
-Starting Nmap 7.12 ( https://nmap.org ) at 2016-10-06 10:01 CEST
-Nmap scan report for 192.168.1.3 (192.168.1.3)
-Host is up (0.00011s latency).
 PORT     STATE SERVICE VERSION
-8123/tcp open  http    CherryPy wsgiserver
+8123/tcp open  http    aiohttp 3.1.3 (Python 3.6)
 | http-headers: 
 |   Content-Type: text/html; charset=utf-8
-|   Content-Length: 4309
+|   Content-Length: 3073
+|   Date: Tue, 29 May 2018 16:16:50 GMT
+|   Server: Python/3.6 aiohttp/3.1.3
 |   Connection: close
-|   Date: Thu, 06 Oct 2016 08:01:31 GMT
-|   Server: Home Assistant
-|
+|   
 |_  (Request type: GET)
-|_http-server-header: Home Assistant
+|_http-server-header: Python/3.6 aiohttp/3.1.3
 |_http-title: Home Assistant
 
 Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
-Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds
+Nmap done: 1 IP address (1 host up) scanned in 12.13 seconds
+
 ```
 
