Analyser le rapport pour "portal.sso.us-east-2.amazonaws.com"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

1

Durée

43.25seconde

Date

2024-05-24

IP

18.117.68.179

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A portal.sso.us-east-2.amazonaws.com)
Nmap scan report for portal.sso.us-east-2.amazonaws.com (18.117.68.179)
Host is up (0.061s latency).
Other addresses for portal.sso.us-east-2.amazonaws.com (not scanned): 3.139.222.188 3.23.211.55
rDNS record for 18.117.68.179: ec2-18-117-68-179.us-east-2.compute.amazonaws.com
Not shown: 999 filtered tcp ports (no-response)
PORT    STATE SERVICE   VERSION
443/tcp open  ssl/https AWS SSO
| tls-nextprotoneg: 
|   h2
|_  http/1.1
| ssl-cert: Subject: commonName=portal.sso.us-east-2.amazonaws.com
| Subject Alternative Name: DNS:portal.sso.us-east-2.amazonaws.com, DNS:onebox.portal.sso.us-east-2.amazonaws.com
| Not valid before: 2023-07-08T00:00:00
|_Not valid after:  2024-08-05T23:59:59
| tls-alpn: 
|   h2
|_  http/1.1
|_http-server-header: AWS SSO
|_ssl-date: TLS randomness does not represent time
|_http-title: Site doesn't have a title (application/json).
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 404 Not Found
|     Date: Fri, 24 May 2024 19:38:24 GMT
|     Content-Type: application/json
|     Content-Length: 230
|     Connection: close
|     Server: AWS SSO
|     {"message":"Could not find resource for full path: https://swbport-alb-4ogsj5cirkff-1945945605.us-east-2.elb.amazonaws.com/nice%20ports%2C/Tri%6Eity.txt%2ebak","__type":"com.amazonaws.switchboard.portal#ResourceNotFoundException"}
|   GetRequest, HTTPOptions: 
|     HTTP/1.1 404 Not Found
|     Date: Fri, 24 May 2024 19:38:24 GMT
|     Content-Type: application/json
|     Content-Length: 195
|     Connection: close
|     Server: AWS SSO
|     {"message":"Could not find resource for full path: https://swbport-alb-4ogsj5cirkff-1945945605.us-east-2.elb.amazonaws.com/","__type":"com.amazonaws.switchboard.portal#ResourceNotFoundException"}
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 24 May 2024 19:38:30 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>
|   tor-versions: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 24 May 2024 19:38:24 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>
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.92%T=SSL%I=7%D=5/24%Time=6650ECAF%P=x86_64-redhat-linux
SF:-gnu%r(GetRequest,15B,"HTTP/1\.1\x20404\x20Not\x20Found\r\nDate:\x20Fri
SF:,\x2024\x20May\x202024\x2019:38:24\x20GMT\r\nContent-Type:\x20applicati
SF:on/json\r\nContent-Length:\x20195\r\nConnection:\x20close\r\nServer:\x2
SF:0AWS\x20SSO\r\n\r\n{\"message\":\"Could\x20not\x20find\x20resource\x20f
SF:or\x20full\x20path:\x20https://swbport-alb-4ogsj5cirkff-1945945605\.us-
SF:east-2\.elb\.amazonaws\.com/\",\"__type\":\"com\.amazonaws\.switchboard
SF:\.portal#ResourceNotFoundException\"}")%r(HTTPOptions,15B,"HTTP/1\.1\x2
SF:0404\x20Not\x20Found\r\nDate:\x20Fri,\x2024\x20May\x202024\x2019:38:24\
SF:x20GMT\r\nContent-Type:\x20application/json\r\nContent-Length:\x20195\r
SF:\nConnection:\x20close\r\nServer:\x20AWS\x20SSO\r\n\r\n{\"message\":\"C
SF:ould\x20not\x20find\x20resource\x20for\x20full\x20path:\x20https://swbp
SF:ort-alb-4ogsj5cirkff-1945945605\.us-east-2\.elb\.amazonaws\.com/\",\"__
SF:type\":\"com\.amazonaws\.switchboard\.portal#ResourceNotFoundException\
SF:"}")%r(FourOhFourRequest,17E,"HTTP/1\.1\x20404\x20Not\x20Found\r\nDate:
SF:\x20Fri,\x2024\x20May\x202024\x2019:38:24\x20GMT\r\nContent-Type:\x20ap
SF:plication/json\r\nContent-Length:\x20230\r\nConnection:\x20close\r\nSer
SF:ver:\x20AWS\x20SSO\r\n\r\n{\"message\":\"Could\x20not\x20find\x20resour
SF:ce\x20for\x20full\x20path:\x20https://swbport-alb-4ogsj5cirkff-19459456
SF:05\.us-east-2\.elb\.amazonaws\.com/nice%20ports%2C/Tri%6Eity\.txt%2ebak
SF:\",\"__type\":\"com\.amazonaws\.switchboard\.portal#ResourceNotFoundExc
SF:eption\"}")%r(tor-versions,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nS
SF:erver:\x20awselb/2\.0\r\nDate:\x20Fri,\x2024\x20May\x202024\x2019:38:24
SF:\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\r\nConn
SF:ection:\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Request</t
SF:itle></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></cente
SF:r>\r\n</body>\r\n</html>\r\n")%r(RTSPRequest,7A,"<html>\r\n<head><title
SF:>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x20B
SF:ad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(RPCCheck,110,
SF:"HTTP/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\
SF:x20Fri,\x2024\x20May\x202024\x2019:38:30\x20GMT\r\nContent-Type:\x20tex
SF:t/html\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n\r\n<html>\
SF:r\n<head><title>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<cent
SF:er><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n");
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: general purpose
Running (JUST GUESSING): Linux 2.6.X|3.X|4.X (90%)
OS CPE: cpe:/o:linux:linux_kernel:2.6.32 cpe:/o:linux:linux_kernel:3 cpe:/o:linux:linux_kernel:4
Aggressive OS guesses: Linux 2.6.32 (90%), Linux 3.2 - 4.9 (90%), Linux 2.6.32 - 3.10 (89%), Linux 2.6.32 - 3.13 (89%), Linux 3.10 - 3.13 (88%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 17 hops

TRACEROUTE (using port 443/tcp)
HOP RTT       ADDRESS
1   0.34 ms   208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.71 ms   gw.mcom-colocationamerica.com (208.64.231.81)
3   0.79 ms   r1b4.n1p1400.lax.multacom.net (64.69.46.9)
4   0.52 ms   ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   1.06 ms   ae-16.r24.lsanca07.us.bb.gin.ntt.net (129.250.3.78)
6   32.66 ms  ae-3.r22.dllstx14.us.bb.gin.ntt.net (129.250.7.68)
7   32.98 ms  ae-5.a00.dllstx14.us.bb.gin.ntt.net (129.250.3.117)
8   40.58 ms  ae-2.amazon.dllstx14.us.bb.gin.ntt.net (129.250.201.10)
9   34.19 ms  15.230.130.167
10  36.45 ms  176.32.125.193
11  ...
12  592.86 ms 108.166.252.8
13  ... 14
15  60.95 ms  108.166.252.24
16  60.96 ms  108.166.252.50
17  61.14 ms  ec2-18-117-68-179.us-east-2.compute.amazonaws.com (18.117.68.179)

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 43.25 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
18.117.68.179
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 1 identifiés
Exécuter la commande
nmap -A portal.sso.us-east-2.amazonaws.com
Scan date
24 May 2024 15:38
Durée de l'analyse
43.25seconde
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: