Analyser le rapport pour "torch.buyerzone.com"

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

Ports

2

Durée

41.37seconde

Date

2024-11-29

IP

3.222.14.233

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A torch.buyerzone.com)
Nmap scan report for torch.buyerzone.com (3.222.14.233)
Host is up (0.061s latency).
Other addresses for torch.buyerzone.com (not scanned): 34.225.103.7 3.217.6.17
rDNS record for 3.222.14.233: ec2-3-222-14-233.compute-1.amazonaws.com
Not shown: 998 filtered tcp ports (no-response)
PORT    STATE  SERVICE   VERSION
80/tcp  closed http
443/tcp open   ssl/https awselb/2.0
| tls-alpn: 
|   h2
|_  http/1.1
|_http-title: Site doesn't have a title (text/plain; charset=utf-8).
| ssl-cert: Subject: commonName=*.buyerzone.com
| Subject Alternative Name: DNS:*.buyerzone.com, DNS:buyerzone.com
| Not valid before: 2024-07-13T00:00:00
|_Not valid after:  2025-08-10T23:59:59
|_http-server-header: awselb/2.0
| http-robots.txt: 1 disallowed entry 
|_/
| tls-nextprotoneg: 
|   h2
|_  http/1.1
|_ssl-date: TLS randomness does not represent time
| fingerprint-strings: 
|   DNSVersionBindReqTCP, RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 29 Nov 2024 11:35: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>
|   FourOhFourRequest, GetRequest, HTTPOptions: 
|     HTTP/1.1 403 Forbidden
|     Server: awselb/2.0
|     Date: Fri, 29 Nov 2024 11:35:00 GMT
|     Content-Type: text/plain; charset=utf-8
|     Content-Length: 9
|     Connection: close
|     Forbidden
|   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, 29 Nov 2024 11:35: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>
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=11/29%Time=6749A6E4%P=x86_64-redhat-linu
SF:x-gnu%r(GetRequest,AB,"HTTP/1\.1\x20403\x20Forbidden\r\nServer:\x20awse
SF:lb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\x202024\x2011:35:00\x20GMT\r\nCon
SF:tent-Type:\x20text/plain;\x20charset=utf-8\r\nContent-Length:\x209\r\nC
SF:onnection:\x20close\r\n\r\nForbidden")%r(HTTPOptions,AB,"HTTP/1\.1\x204
SF:03\x20Forbidden\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov
SF:\x202024\x2011:35:00\x20GMT\r\nContent-Type:\x20text/plain;\x20charset=
SF:utf-8\r\nContent-Length:\x209\r\nConnection:\x20close\r\n\r\nForbidden"
SF:)%r(FourOhFourRequest,AB,"HTTP/1\.1\x20403\x20Forbidden\r\nServer:\x20a
SF:wselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\x202024\x2011:35:00\x20GMT\r\n
SF:Content-Type:\x20text/plain;\x20charset=utf-8\r\nContent-Length:\x209\r
SF:\nConnection:\x20close\r\n\r\nForbidden")%r(tor-versions,110,"HTTP/1\.1
SF:\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2
SF:029\x20Nov\x202024\x2011:35:00\x20GMT\r\nContent-Type:\x20text/html\r\n
SF:Content-Length:\x20122\r\nConnection:\x20close\r\n\r\n<html>\r\n<head><
SF:title>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400
SF:\x20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(RTSPRequ
SF:est,7A,"<html>\r\n<head><title>400\x20Bad\x20Request</title></head>\r\n
SF:<body>\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\
SF:n</html>\r\n")%r(RPCCheck,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nSe
SF:rver:\x20awselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\x202024\x2011:35:06\
SF:x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\r\nConne
SF:ction:\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Request</ti
SF:tle></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></center
SF:>\r\n</body>\r\n</html>\r\n")%r(DNSVersionBindReqTCP,110,"HTTP/1\.1\x20
SF:400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2029\
SF:x20Nov\x202024\x2011:35:06\x20GMT\r\nContent-Type:\x20text/html\r\nCont
SF:ent-Length:\x20122\r\nConnection:\x20close\r\n\r\n<html>\r\n<head><titl
SF:e>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x20
SF:Bad\x20Request</h1></center>\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: 14 hops

TRACEROUTE (using port 80/tcp)
HOP RTT      ADDRESS
1   0.22 ms  208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.69 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   2.05 ms  r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   ...
5   12.36 ms be2931.ccr31.phx01.atlas.cogentco.com (154.54.44.85)
6   21.39 ms be5471.ccr21.elp02.atlas.cogentco.com (154.54.166.57)
7   32.42 ms be3821.ccr31.dfw01.atlas.cogentco.com (154.54.165.25)
8   32.68 ms be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74)
9   ... 13
14  65.66 ms ec2-3-222-14-233.compute-1.amazonaws.com (3.222.14.233)

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 41.37 seconds
Schéma de couleur
Trustpilot
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
3.222.14.233
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 torch.buyerzone.com
Scan date
29 Nov 2024 06:35
API - Scan ID
Durée de l'analyse
41.37seconde
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: