Analyser le rapport pour "b7-3-us-w01.u5fgb.com"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

2

Durée

33.66seconde

Date

2024-09-27

IP

18.220.241.11

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A b7-3-us-w01.u5fgb.com)
Nmap scan report for b7-3-us-w01.u5fgb.com (18.220.241.11)
Host is up (0.059s latency).
Other addresses for b7-3-us-w01.u5fgb.com (not scanned): 3.130.244.23
rDNS record for 18.220.241.11: ec2-18-220-241-11.us-east-2.compute.amazonaws.com
Not shown: 998 filtered tcp ports (no-response)
PORT    STATE  SERVICE VERSION
80/tcp  open   http    awselb/2.0
|_http-title: 503 Service Temporarily Unavailable
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 503 Service Temporarily Unavailable
|     Server: awselb/2.0
|     Date: Fri, 27 Sep 2024 19:25:01 GMT
|     Content-Type: text/html
|     Content-Length: 162
|     Connection: close
|     <html>
|     <head><title>503 Service Temporarily Unavailable</title></head>
|     <body>
|     <center><h1>503 Service Temporarily Unavailable</h1></center>
|     </body>
|     </html>
|   GetRequest, HTTPOptions: 
|     HTTP/1.1 503 Service Temporarily Unavailable
|     Server: awselb/2.0
|     Date: Fri, 27 Sep 2024 19:25:00 GMT
|     Content-Type: text/html
|     Content-Length: 162
|     Connection: close
|     <html>
|     <head><title>503 Service Temporarily Unavailable</title></head>
|     <body>
|     <center><h1>503 Service Temporarily Unavailable</h1></center>
|     </body>
|     </html>
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 27 Sep 2024 19:25:06 GMT
|     Content-Type: text/html
|     Content-Length: 122
|     Connection: close
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body>
|     <center><h1>400 Bad Request</h1></center>
|     </body>
|     </html>
|   RTSPRequest: 
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body>
|     <center><h1>400 Bad Request</h1></center>
|     </body>
|     </html>
|   X11Probe: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 27 Sep 2024 19:25:01 GMT
|     Content-Type: text/html
|     Content-Length: 122
|     Connection: close
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body>
|     <center><h1>400 Bad Request</h1></center>
|     </body>
|_    </html>
|_http-server-header: awselb/2.0
443/tcp closed https
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-Port80-TCP:V=7.92%I=7%D=9/27%Time=66F7068C%P=x86_64-redhat-linux-gnu%r(
SF:GetRequest,14C,"HTTP/1\.1\x20503\x20Service\x20Temporarily\x20Unavailab
SF:le\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2027\x20Sep\x202024\x201
SF:9:25:00\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20162\
SF:r\nConnection:\x20close\r\n\r\n<html>\r\n<head><title>503\x20Service\x2
SF:0Temporarily\x20Unavailable</title></head>\r\n<body>\r\n<center><h1>503
SF:\x20Service\x20Temporarily\x20Unavailable</h1></center>\r\n</body>\r\n<
SF:/html>\r\n")%r(HTTPOptions,14C,"HTTP/1\.1\x20503\x20Service\x20Temporar
SF:ily\x20Unavailable\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2027\x20
SF:Sep\x202024\x2019:25:00\x20GMT\r\nContent-Type:\x20text/html\r\nContent
SF:-Length:\x20162\r\nConnection:\x20close\r\n\r\n<html>\r\n<head><title>5
SF:03\x20Service\x20Temporarily\x20Unavailable</title></head>\r\n<body>\r\
SF:n<center><h1>503\x20Service\x20Temporarily\x20Unavailable</h1></center>
SF:\r\n</body>\r\n</html>\r\n")%r(RTSPRequest,7A,"<html>\r\n<head><title>4
SF:00\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x20Bad
SF:\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(X11Probe,110,"H
SF:TTP/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x2
SF:0Fri,\x2027\x20Sep\x202024\x2019:25:01\x20GMT\r\nContent-Type:\x20text/
SF:html\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n\r\n<html>\r\
SF:n<head><title>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<center
SF:><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(
SF:FourOhFourRequest,14C,"HTTP/1\.1\x20503\x20Service\x20Temporarily\x20Un
SF:available\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2027\x20Sep\x2020
SF:24\x2019:25:01\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\
SF:x20162\r\nConnection:\x20close\r\n\r\n<html>\r\n<head><title>503\x20Ser
SF:vice\x20Temporarily\x20Unavailable</title></head>\r\n<body>\r\n<center>
SF:<h1>503\x20Service\x20Temporarily\x20Unavailable</h1></center>\r\n</bod
SF:y>\r\n</html>\r\n")%r(RPCCheck,110,"HTTP/1\.1\x20400\x20Bad\x20Request\
SF:r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2027\x20Sep\x202024\x2019:2
SF:5:06\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\r\n
SF:Connection:\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Reques
SF:t</title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></c
SF:enter>\r\n</body>\r\n</html>\r\n");
Aggressive OS guesses: Linux 2.6.32 (91%), Linux 3.2 - 4.9 (91%), Linux 2.6.32 - 3.10 (91%), Linux 3.10 - 3.13 (88%), Linux 3.1 (87%), Linux 3.2 (87%), Linux 2.6.32 - 2.6.35 (87%), Linux 2.6.32 - 3.5 (87%), Android 5.0 - 7.0 (Linux 3.4 - 3.10) (87%), Linux 2.6.32 - 3.13 (87%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 17 hops

TRACEROUTE (using port 443/tcp)
HOP RTT       ADDRESS
1   0.27 ms   208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.52 ms   gw.mcom-colocationamerica.com (208.64.231.81)
3   0.59 ms   r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   5.11 ms   ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   1.59 ms   ae-16.r24.lsanca07.us.bb.gin.ntt.net (129.250.3.78)
6   32.63 ms  ae-3.r22.dllstx14.us.bb.gin.ntt.net (129.250.7.68)
7   32.73 ms  ae-29.a00.dllstx14.us.bb.gin.ntt.net (129.250.3.47)
8   33.22 ms  ae-3.amazon.dllstx14.us.bb.gin.ntt.net (129.250.201.22)
9   33.79 ms  54.239.105.107
10  32.90 ms  15.230.48.46
11  ...
12  441.19 ms 108.166.252.9
13  ...
14  59.14 ms  108.166.244.1
15  ... 16
17  59.10 ms  ec2-18-220-241-11.us-east-2.compute.amazonaws.com (18.220.241.11)

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 33.66 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
18.220.241.11
Statut d'hôte
UP
Pays cible
L'emplacement IP cible est États-Unis d'Amérique
États-Unis d'Amérique
Scan gratuit
Scan gratuit
Méthode de numérisation
Analyser les informations du système d'exploitation et Traceroute
État de l'analyse
Ports 2 identifiés
Exécuter la commande
nmap -A b7-3-us-w01.u5fgb.com
Scan date
27 Sep 2024 15:25
Durée de l'analyse
33.66seconde
Télécharger le rapport
Remove scan result
$
Total scans
Scannez plus
Prix

PROFESSIONNELLE


  • 5 scans/jour
  • Appels API quotidiens - 100 000 requêtes
  • Enregistrer le journal
  • Analyse publique
  • Analyse OSINT
  • Analyse non répertoriée
  • Balayage privé
  • Pas de ads
  • Supprimer le résultat de l'analyse
  • Supprimer après analyse
  • Méthodes supplémentaires de numérisation
$0.75$7.50/mois
Facturé annuellement @ $9.00$90.00 90% de réduction
Devenez professionnel

INSCRITE


  • 5 scans/jour
  • Appels API quotidiens - 20 requêtes
  • Enregistrer le journal
  • Analyse publique
  • Analyse OSINT
  • Analyse non répertoriée
  • Balayage privé
  • Pas de ads
  • Supprimer le résultat de l'analyse
  • Supprimer après analyse
  • Méthodes supplémentaires de numérisation
$0/durée de vie
 
Enregistrer
Scanner l'hôte
Certains pare-feu bloquent les analyses de port. Pour obtenir de vrais résultats positifs, ajoutez les adresses IP portscanner.online (208.76.253.232-208.76.253.239 ou CIDR 208.76.253.232/29) à la liste blanche
[scan_method]
Visibilité:
Méthode de numérisation: