Scan report for "socked-io-uws-2b5a7a67f7636d45.elb.us-east-1.amazonaws.com"

Membership level: Free member
Scan OS information and Traceroute (nmap -A socked-io-uws-2b5a7a67f7636d45.elb.us-east-1.amazonaws.com)
Nmap scan report for socked-io-uws-2b5a7a67f7636d45.elb.us-east-1.amazonaws.com (3.82.237.223)
Host is up (0.071s latency).
rDNS record for 3.82.237.223: ec2-3-82-237-223.compute-1.amazonaws.com
Not shown: 999 filtered ports
PORT    STATE SERVICE   VERSION
443/tcp open  ssl/https
| fingerprint-strings: 
|   FourOhFourRequest, GetRequest, HTTPOptions, RTSPRequest, SIPOptions: 
|     HTTP/1.1 200 OK
|     uWebSockets: 18
|     Content-Length: 20
|_    Nothing to see here!
|_http-title: Site doesn't have a title.
| ssl-cert: Subject: commonName=*.reamaze.com
| Subject Alternative Name: DNS:*.reamaze.com, DNS:reamaze.com
| Not valid before: 2023-07-13T17:50:50
|_Not valid after:  2024-08-13T17:50:50
|_ssl-date: TLS randomness does not represent time
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
SF-Port443-TCP:V=7.70%T=SSL%I=7%D=11/19%Time=655ACC80%P=x86_64-redhat-linu
SF:x-gnu%r(GetRequest,4C,"HTTP/1\.1\x20200\x20OK\r\nuWebSockets:\x2018\r\n
SF:Content-Length:\x2020\r\n\r\nNothing\x20to\x20see\x20here!")%r(HTTPOpti
SF:ons,4C,"HTTP/1\.1\x20200\x20OK\r\nuWebSockets:\x2018\r\nContent-Length:
SF:\x2020\r\n\r\nNothing\x20to\x20see\x20here!")%r(FourOhFourRequest,4C,"H
SF:TTP/1\.1\x20200\x20OK\r\nuWebSockets:\x2018\r\nContent-Length:\x2020\r\
SF:n\r\nNothing\x20to\x20see\x20here!")%r(RTSPRequest,4C,"HTTP/1\.1\x20200
SF:\x20OK\r\nuWebSockets:\x2018\r\nContent-Length:\x2020\r\n\r\nNothing\x2
SF:0to\x20see\x20here!")%r(SIPOptions,4C,"HTTP/1\.1\x20200\x20OK\r\nuWebSo
SF:ckets:\x2018\r\nContent-Length:\x2020\r\n\r\nNothing\x20to\x20see\x20he
SF:re!");
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
OS fingerprint not ideal because: Missing a closed TCP port so results incomplete
No OS matches for host
Network Distance: 17 hops

TRACEROUTE (using port 80/tcp)
HOP RTT      ADDRESS
1   7.48 ms  208.76.251.177
2   7.90 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   7.89 ms  1.162.45.96-dedicated.multacom.com (96.45.162.1)
4   8.44 ms  be5361.ccr42.lax01.atlas.cogentco.com (38.99.219.57)
5   18.72 ms be2932.ccr32.phx01.atlas.cogentco.com (154.54.45.161)
6   26.03 ms be3872.ccr22.elp02.atlas.cogentco.com (154.54.26.54)
7   43.48 ms be3851.ccr42.iah01.atlas.cogentco.com (154.54.2.5)
8   44.96 ms be2418.rcr51.b023723-0.iah01.atlas.cogentco.com (154.54.6.78)
9   48.29 ms 38.88.155.218
10  48.77 ms 52.93.254.205
11  48.13 ms 52.93.64.171
12  ... 16
17  75.88 ms ec2-3-82-237-223.compute-1.amazonaws.com (3.82.237.223)

OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 198.12 seconds
Color Scheme
Target
socked-io-uws-2b5a7a67f7636d45.elb.us-east-1.amazonaws.com
Target IP
3.82.237.223
Target Country
US
Scan method
Scan OS information and Traceroute
Run command
nmap -A socked-io-uws-2b5a7a67f7636d45.elb.us-east-1.amazonaws.com
Scan date
19 Nov 2023 22:06
Copy scan report
Download report
Remove scan result
$
Some firewalls blocks Port scans. For get true positive results add portscanner.online IP addresses (208.76.253.232-208.76.253.239 or CIDR 208.76.253.232/29 ) to the whitelist
[scan_method]
Visibility:
Scan method: