Analyser le rapport pour "amethyst.6pm.com"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

1

Durée

44.84seconde

Date

2024-09-22

IP

34.199.155.165

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A amethyst.6pm.com)
Nmap scan report for amethyst.6pm.com (34.199.155.165)
Host is up (0.064s latency).
Other addresses for amethyst.6pm.com (not scanned): 18.210.220.12 3.218.3.29
rDNS record for 34.199.155.165: ec2-34-199-155-165.compute-1.amazonaws.com
Not shown: 999 filtered tcp ports (no-response)
PORT    STATE SERVICE   VERSION
443/tcp open  ssl/https
|_http-title: Site doesn't have a title (application/json).
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 404 
|     Date: Sun, 22 Sep 2024 07:39:02 GMT
|     Content-Type: application/json
|     Connection: close
|     X-UUID: DEFAULT-3cc4870e-baac-4d52-a62c-ce391451bc0f
|     Vary: Origin
|     Vary: Access-Control-Request-Method
|     Vary: Access-Control-Request-Headers
|     Content-Disposition: inline;filename=f.txt
|     {"timestamp":1726990742699,"status":404,"error":"Not Found","path":"/nice%20ports%2C/Tri%6Eity.txt%2ebak"}
|   GetRequest: 
|     HTTP/1.1 404 
|     Date: Sun, 22 Sep 2024 07:39:02 GMT
|     Content-Type: application/json
|     Connection: close
|     X-UUID: DEFAULT-a8ea51d2-6f67-4b31-872b-cc3e6b76335f
|     Vary: Origin
|     Vary: Access-Control-Request-Method
|     Vary: Access-Control-Request-Headers
|     {"timestamp":1726990742145,"status":404,"error":"Not Found","path":"/"}
|   HTTPOptions: 
|     HTTP/1.1 404 
|     Date: Sun, 22 Sep 2024 07:39:02 GMT
|     Content-Type: application/json
|     Connection: close
|     X-UUID: DEFAULT-10c9ac32-2c44-4b88-bafb-8db9226a0851
|     Vary: Origin
|     Vary: Access-Control-Request-Method
|     Vary: Access-Control-Request-Headers
|     {"timestamp":1726990742418,"status":404,"error":"Not Found","path":"/"}
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Sun, 22 Sep 2024 07:39:08 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: Sun, 22 Sep 2024 07:39:02 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>
| tls-nextprotoneg: 
|   h2
|_  http/1.1
| tls-alpn: 
|   h2
|_  http/1.1
| ssl-cert: Subject: commonName=amethyst.6pm.com
| Subject Alternative Name: DNS:amethyst.6pm.com
| Not valid before: 2024-02-11T00:00:00
|_Not valid after:  2025-03-12T23:59:59
| http-robots.txt: 1 disallowed entry 
|_/
|_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.92%T=SSL%I=7%D=9/22%Time=66EFC995%P=x86_64-redhat-linux
SF:-gnu%r(GetRequest,13F,"HTTP/1\.1\x20404\x20\r\nDate:\x20Sun,\x2022\x20S
SF:ep\x202024\x2007:39:02\x20GMT\r\nContent-Type:\x20application/json\r\nC
SF:onnection:\x20close\r\nX-UUID:\x20DEFAULT-a8ea51d2-6f67-4b31-872b-cc3e6
SF:b76335f\r\nVary:\x20Origin\r\nVary:\x20Access-Control-Request-Method\r\
SF:nVary:\x20Access-Control-Request-Headers\r\n\r\n{\"timestamp\":17269907
SF:42145,\"status\":404,\"error\":\"Not\x20Found\",\"path\":\"/\"}")%r(HTT
SF:POptions,13F,"HTTP/1\.1\x20404\x20\r\nDate:\x20Sun,\x2022\x20Sep\x20202
SF:4\x2007:39:02\x20GMT\r\nContent-Type:\x20application/json\r\nConnection
SF::\x20close\r\nX-UUID:\x20DEFAULT-10c9ac32-2c44-4b88-bafb-8db9226a0851\r
SF:\nVary:\x20Origin\r\nVary:\x20Access-Control-Request-Method\r\nVary:\x2
SF:0Access-Control-Request-Headers\r\n\r\n{\"timestamp\":1726990742418,\"s
SF:tatus\":404,\"error\":\"Not\x20Found\",\"path\":\"/\"}")%r(FourOhFourRe
SF:quest,18E,"HTTP/1\.1\x20404\x20\r\nDate:\x20Sun,\x2022\x20Sep\x202024\x
SF:2007:39:02\x20GMT\r\nContent-Type:\x20application/json\r\nConnection:\x
SF:20close\r\nX-UUID:\x20DEFAULT-3cc4870e-baac-4d52-a62c-ce391451bc0f\r\nV
SF:ary:\x20Origin\r\nVary:\x20Access-Control-Request-Method\r\nVary:\x20Ac
SF:cess-Control-Request-Headers\r\nContent-Disposition:\x20inline;filename
SF:=f\.txt\r\n\r\n{\"timestamp\":1726990742699,\"status\":404,\"error\":\"
SF:Not\x20Found\",\"path\":\"/nice%20ports%2C/Tri%6Eity\.txt%2ebak\"}")%r(
SF:tor-versions,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awse
SF:lb/2\.0\r\nDate:\x20Sun,\x2022\x20Sep\x202024\x2007:39:02\x20GMT\r\nCon
SF:tent-Type:\x20text/html\r\nContent-Length:\x20122\r\nConnection:\x20clo
SF:se\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Request</title></head>\r
SF:\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\
SF:r\n</html>\r\n")%r(RTSPRequest,7A,"<html>\r\n<head><title>400\x20Bad\x2
SF:0Request</title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request<
SF:/h1></center>\r\n</body>\r\n</html>\r\n")%r(RPCCheck,110,"HTTP/1\.1\x20
SF:400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20Sun,\x2022\
SF:x20Sep\x202024\x2007:39:08\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");
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.20 ms  208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   1.00 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   0.81 ms  r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   0.40 ms  ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   1.93 ms  ae-16.r24.lsanca07.us.bb.gin.ntt.net (129.250.3.78)
6   32.72 ms ae-3.r22.dllstx14.us.bb.gin.ntt.net (129.250.7.68)
7   32.77 ms ae-22.a01.dllstx14.us.bb.gin.ntt.net (129.250.3.115)
8   33.43 ms ae-1.amazon.dllstx14.us.bb.gin.ntt.net (128.241.14.222)
9   33.42 ms 15.230.130.157
10  33.17 ms 15.230.48.44
11  ... 16
17  64.27 ms ec2-34-199-155-165.compute-1.amazonaws.com (34.199.155.165)

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 44.84 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
34.199.155.165
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 amethyst.6pm.com
Scan date
22 Sep 2024 03:39
Durée de l'analyse
44.84seconde
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: