Analyser le rapport pour "www.ncourt.com"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

2

Durée

32.88seconde

Date

2024-09-19

IP

34.194.103.149

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A www.ncourt.com)
Nmap scan report for www.ncourt.com (34.194.103.149)
Host is up (0.064s latency).
Other addresses for www.ncourt.com (not scanned): 18.214.180.69
rDNS record for 34.194.103.149: ec2-34-194-103-149.compute-1.amazonaws.com
Not shown: 998 filtered tcp ports (no-response)
PORT    STATE SERVICE  VERSION
80/tcp  open  http     awselb/2.0
|_http-server-header: awselb/2.0
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 301 Moved Permanently
|     Server: awselb/2.0
|     Date: Fri, 20 Sep 2024 03:50:54 GMT
|     Content-Type: text/html
|     Content-Length: 134
|     Connection: close
|     Location: https://ncourtprod-1624615280.us-east-1.elb.amazonaws.com:443/nice%20ports%2C/Tri%6Eity.txt%2ebak
|     <html>
|     <head><title>301 Moved Permanently</title></head>
|     <body>
|     <center><h1>301 Moved Permanently</h1></center>
|     </body>
|     </html>
|   GetRequest, HTTPOptions: 
|     HTTP/1.1 301 Moved Permanently
|     Server: awselb/2.0
|     Date: Fri, 20 Sep 2024 03:50:53 GMT
|     Content-Type: text/html
|     Content-Length: 134
|     Connection: close
|     Location: https://ncourtprod-1624615280.us-east-1.elb.amazonaws.com:443/
|     <html>
|     <head><title>301 Moved Permanently</title></head>
|     <body>
|     <center><h1>301 Moved Permanently</h1></center>
|     </body>
|     </html>
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 20 Sep 2024 03:50:59 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, 20 Sep 2024 03:50:53 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-title: Did not follow redirect to https://www.ncourt.com:443/
443/tcp open  ssl/http Microsoft IIS httpd 10.0
| tls-nextprotoneg: 
|   h2
|_  http/1.1
| ssl-cert: Subject: commonName=ncourt.com
| Subject Alternative Name: DNS:ncourt.com, DNS:www.ncourt.com
| Not valid before: 2024-07-09T00:00:00
|_Not valid after:  2025-08-07T23:59:59
| tls-alpn: 
|   h2
|_  http/1.1
|_http-server-header: Microsoft-IIS/10.0
|_ssl-date: TLS randomness does not represent time
|_http-title: Did not follow redirect to http://home.ncourt.com/
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/19%Time=66ECF11D%P=x86_64-redhat-linux-gnu%r(
SF:GetRequest,16C,"HTTP/1\.1\x20301\x20Moved\x20Permanently\r\nServer:\x20
SF:awselb/2\.0\r\nDate:\x20Fri,\x2020\x20Sep\x202024\x2003:50:53\x20GMT\r\
SF:nContent-Type:\x20text/html\r\nContent-Length:\x20134\r\nConnection:\x2
SF:0close\r\nLocation:\x20https://ncourtprod-1624615280\.us-east-1\.elb\.a
SF:mazonaws\.com:443/\r\n\r\n<html>\r\n<head><title>301\x20Moved\x20Perman
SF:ently</title></head>\r\n<body>\r\n<center><h1>301\x20Moved\x20Permanent
SF:ly</h1></center>\r\n</body>\r\n</html>\r\n")%r(HTTPOptions,16C,"HTTP/1\
SF:.1\x20301\x20Moved\x20Permanently\r\nServer:\x20awselb/2\.0\r\nDate:\x2
SF:0Fri,\x2020\x20Sep\x202024\x2003:50:53\x20GMT\r\nContent-Type:\x20text/
SF:html\r\nContent-Length:\x20134\r\nConnection:\x20close\r\nLocation:\x20
SF:https://ncourtprod-1624615280\.us-east-1\.elb\.amazonaws\.com:443/\r\n\
SF:r\n<html>\r\n<head><title>301\x20Moved\x20Permanently</title></head>\r\
SF:n<body>\r\n<center><h1>301\x20Moved\x20Permanently</h1></center>\r\n</b
SF:ody>\r\n</html>\r\n")%r(RTSPRequest,7A,"<html>\r\n<head><title>400\x20B
SF:ad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Req
SF:uest</h1></center>\r\n</body>\r\n</html>\r\n")%r(X11Probe,110,"HTTP/1\.
SF:1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x
SF:2020\x20Sep\x202024\x2003:50:53\x20GMT\r\nContent-Type:\x20text/html\r\
SF:nContent-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>40
SF:0\x20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(FourOhF
SF:ourRequest,18F,"HTTP/1\.1\x20301\x20Moved\x20Permanently\r\nServer:\x20
SF:awselb/2\.0\r\nDate:\x20Fri,\x2020\x20Sep\x202024\x2003:50:54\x20GMT\r\
SF:nContent-Type:\x20text/html\r\nContent-Length:\x20134\r\nConnection:\x2
SF:0close\r\nLocation:\x20https://ncourtprod-1624615280\.us-east-1\.elb\.a
SF:mazonaws\.com:443/nice%20ports%2C/Tri%6Eity\.txt%2ebak\r\n\r\n<html>\r\
SF:n<head><title>301\x20Moved\x20Permanently</title></head>\r\n<body>\r\n<
SF:center><h1>301\x20Moved\x20Permanently</h1></center>\r\n</body>\r\n</ht
SF:ml>\r\n")%r(RPCCheck,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nServer:
SF:\x20awselb/2\.0\r\nDate:\x20Fri,\x2020\x20Sep\x202024\x2003:50:59\x20GM
SF:T\r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\r\nConnection
SF::\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Request</title><
SF:/head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n
SF:</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: 16 hops
Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows

TRACEROUTE (using port 443/tcp)
HOP RTT      ADDRESS
1   0.21 ms  208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.58 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   0.72 ms  r1b4.n1p1400.lax.multacom.net (64.69.46.9)
4   0.48 ms  ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   ...
6   32.66 ms ae-3.r22.dllstx14.us.bb.gin.ntt.net (129.250.7.68)
7   32.81 ms ae-29.a00.dllstx14.us.bb.gin.ntt.net (129.250.3.47)
8   33.05 ms ae-1.amazon.dllstx14.us.bb.gin.ntt.net (128.241.14.222)
9   34.14 ms 15.230.130.167
10  35.41 ms 176.32.125.145
11  ... 15
16  63.65 ms ec2-34-194-103-149.compute-1.amazonaws.com (34.194.103.149)

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 32.88 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
34.194.103.149
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 www.ncourt.com
Scan date
19 Sep 2024 23:51
Durée de l'analyse
32.88seconde
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: