Analyser le rapport pour "chroma.zenlist.com"

  1. Portscanner en ligne
  2. Analyser le rapport pour "chroma.zenlist.com"
Niveau d'adhésion: Membre gratuit
Sommaire

Ports

2

Durée

38.03seconde

Date

2024-12-26

IP

54.149.127.17

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A chroma.zenlist.com)
Nmap scan report for chroma.zenlist.com (54.149.127.17)
Host is up (0.026s latency).
Other addresses for chroma.zenlist.com (not scanned): 52.40.35.169 34.210.166.110
rDNS record for 54.149.127.17: ec2-54-149-127-17.us-west-2.compute.amazonaws.com
Not shown: 998 filtered tcp ports (no-response)
PORT    STATE  SERVICE   VERSION
80/tcp  closed http
443/tcp open   ssl/https
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 403 Forbidden
|     Date: Thu, 26 Dec 2024 07:43:00 GMT
|     Content-Type: application/json
|     Content-Length: 23
|     Connection: close
|     x-amzn-RequestId: 843c1aea-4edf-49e8-a1b2-4013a82d6224
|     x-amzn-ErrorType: ForbiddenException
|     x-amz-apigw-id: DY5Y0EidvHcErvg=
|     {"message":"Forbidden"}
|   GetRequest: 
|     HTTP/1.1 403 Forbidden
|     Date: Thu, 26 Dec 2024 07:43:00 GMT
|     Content-Type: application/json
|     Content-Length: 23
|     Connection: close
|     x-amzn-RequestId: 2d0e34fb-ab6f-4eab-96fd-41434e053809
|     x-amzn-ErrorType: ForbiddenException
|     x-amz-apigw-id: DY5YyFuIvHcEDTw=
|     {"message":"Forbidden"}
|   HTTPOptions: 
|     HTTP/1.1 403 Forbidden
|     Date: Thu, 26 Dec 2024 07:43:00 GMT
|     Content-Type: application/json
|     Content-Length: 23
|     Connection: close
|     x-amzn-RequestId: 818b3503-b4e6-415f-b570-958763234de4
|     x-amzn-ErrorType: ForbiddenException
|     x-amz-apigw-id: DY5YzFQ3vHcEn5w=
|     {"message":"Forbidden"}
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Thu, 26 Dec 2024 07:43: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>
|   tor-versions: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Thu, 26 Dec 2024 07:43:00 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-trane-info: Problem with XML parsing of /evox/about
|_http-title: Site doesn't have a title (application/json).
|_ssl-date: TLS randomness does not represent time
| tls-alpn: 
|   h2
|_  http/1.1
| ssl-cert: Subject: commonName=chroma.zenlist.com
| Subject Alternative Name: DNS:chroma.zenlist.com
| Not valid before: 2024-05-29T00:00:00
|_Not valid after:  2025-06-28T23:59:59
| tls-nextprotoneg: 
|   h2
|_  http/1.1
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=12/25%Time=676D0903%P=x86_64-redhat-linu
SF:x-gnu%r(GetRequest,11D,"HTTP/1\.1\x20403\x20Forbidden\r\nDate:\x20Thu,\
SF:x2026\x20Dec\x202024\x2007:43:00\x20GMT\r\nContent-Type:\x20application
SF:/json\r\nContent-Length:\x2023\r\nConnection:\x20close\r\nx-amzn-Reques
SF:tId:\x202d0e34fb-ab6f-4eab-96fd-41434e053809\r\nx-amzn-ErrorType:\x20Fo
SF:rbiddenException\r\nx-amz-apigw-id:\x20DY5YyFuIvHcEDTw=\r\n\r\n{\"messa
SF:ge\":\"Forbidden\"}")%r(HTTPOptions,11D,"HTTP/1\.1\x20403\x20Forbidden\
SF:r\nDate:\x20Thu,\x2026\x20Dec\x202024\x2007:43:00\x20GMT\r\nContent-Typ
SF:e:\x20application/json\r\nContent-Length:\x2023\r\nConnection:\x20close
SF:\r\nx-amzn-RequestId:\x20818b3503-b4e6-415f-b570-958763234de4\r\nx-amzn
SF:-ErrorType:\x20ForbiddenException\r\nx-amz-apigw-id:\x20DY5YzFQ3vHcEn5w
SF:=\r\n\r\n{\"message\":\"Forbidden\"}")%r(FourOhFourRequest,11D,"HTTP/1\
SF:.1\x20403\x20Forbidden\r\nDate:\x20Thu,\x2026\x20Dec\x202024\x2007:43:0
SF:0\x20GMT\r\nContent-Type:\x20application/json\r\nContent-Length:\x2023\
SF:r\nConnection:\x20close\r\nx-amzn-RequestId:\x20843c1aea-4edf-49e8-a1b2
SF:-4013a82d6224\r\nx-amzn-ErrorType:\x20ForbiddenException\r\nx-amz-apigw
SF:-id:\x20DY5Y0EidvHcErvg=\r\n\r\n{\"message\":\"Forbidden\"}")%r(tor-ver
SF:sions,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0
SF:\r\nDate:\x20Thu,\x2026\x20Dec\x202024\x2007:43:00\x20GMT\r\nContent-Ty
SF:pe:\x20text/html\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n\
SF:r\n<html>\r\n<head><title>400\x20Bad\x20Request</title></head>\r\n<body
SF:>\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\n</ht
SF:ml>\r\n")%r(RTSPRequest,7A,"<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")%r(RPCCheck,110,"HTTP/1\.1\x20400\x20
SF:Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20Thu,\x2026\x20Dec\
SF:x202024\x2007:43:06\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Len
SF:gth:\x20122\r\nConnection:\x20close\r\n\r\n<html>\r\n<head><title>400\x
SF:20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20
SF:Request</h1></center>\r\n</body>\r\n</html>\r\n");
Device type: general purpose
Running (JUST GUESSING): Linux 4.X|2.6.X|3.X (87%)
OS CPE: cpe:/o:linux:linux_kernel:4.2 cpe:/o:linux:linux_kernel:2.6 cpe:/o:linux:linux_kernel:3
Aggressive OS guesses: Linux 4.2 (87%), Linux 2.6.32 - 3.0 (86%), Linux 3.2 - 3.8 (85%), Linux 2.6.32 or 3.10 (85%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 11 hops

TRACEROUTE (using port 80/tcp)
HOP RTT      ADDRESS
1   0.19 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   1.94 ms  r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   0.43 ms  206.72.211.146.any2ix.coresite.com (206.72.211.146)
5   ... 10
11  26.70 ms ec2-54-149-127-17.us-west-2.compute.amazonaws.com (54.149.127.17)

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 38.03 seconds
Schéma de couleur
Trustpilot
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
54.149.127.17
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 chroma.zenlist.com
Scan date
26 Dec 2024 02:43
API - Scan ID
Durée de l'analyse
38.03seconde
Copier le rapport de numérisation
Télécharger le rapport
Remove scan result
$
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: