Analyser le rapport pour "my-care-plan.com"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

2

Durée

34.15seconde

Date

2024-10-19

IP

18.205.139.112

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A my-care-plan.com)
Nmap scan report for my-care-plan.com (18.205.139.112)
Host is up (0.061s latency).
Other addresses for my-care-plan.com (not scanned): 18.214.203.83 34.225.110.235
rDNS record for 18.205.139.112: ec2-18-205-139-112.compute-1.amazonaws.com
Not shown: 998 filtered tcp ports (no-response)
PORT    STATE SERVICE  VERSION
80/tcp  open  http     awselb/2.0
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 301 Moved Permanently
|     Server: awselb/2.0
|     Date: Sat, 19 Oct 2024 19:26:54 GMT
|     Content-Type: text/html
|     Content-Length: 134
|     Connection: close
|     Location: https://prod-backend-2068211183.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: Sat, 19 Oct 2024 19:26:54 GMT
|     Content-Type: text/html
|     Content-Length: 134
|     Connection: close
|     Location: https://prod-backend-2068211183.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: Sat, 19 Oct 2024 19:26: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: Sat, 19 Oct 2024 19:26:54 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://my-care-plan.com:443/
|_http-server-header: awselb/2.0
443/tcp open  ssl/http nginx
|_http-title: Did not follow redirect to https://mobile.my-care-plan.com/#/guest/landing
| http-robots.txt: 2 disallowed entries 
|_/s-* /*?
| ssl-cert: Subject: commonName=*.my-care-plan.com
| Subject Alternative Name: DNS:*.my-care-plan.com, DNS:my-care-plan.com
| Not valid before: 2024-06-30T00:00:00
|_Not valid after:  2025-07-28T23:59:59
|_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-Port80-TCP:V=7.92%I=7%D=10/19%Time=671407FD%P=x86_64-redhat-linux-gnu%r
SF:(GetRequest,16E,"HTTP/1\.1\x20301\x20Moved\x20Permanently\r\nServer:\x2
SF:0awselb/2\.0\r\nDate:\x20Sat,\x2019\x20Oct\x202024\x2019:26:54\x20GMT\r
SF:\nContent-Type:\x20text/html\r\nContent-Length:\x20134\r\nConnection:\x
SF:20close\r\nLocation:\x20https://prod-backend-2068211183\.us-east-1\.elb
SF:\.amazonaws\.com:443/\r\n\r\n<html>\r\n<head><title>301\x20Moved\x20Per
SF:manently</title></head>\r\n<body>\r\n<center><h1>301\x20Moved\x20Perman
SF:ently</h1></center>\r\n</body>\r\n</html>\r\n")%r(HTTPOptions,16E,"HTTP
SF:/1\.1\x20301\x20Moved\x20Permanently\r\nServer:\x20awselb/2\.0\r\nDate:
SF:\x20Sat,\x2019\x20Oct\x202024\x2019:26:54\x20GMT\r\nContent-Type:\x20te
SF:xt/html\r\nContent-Length:\x20134\r\nConnection:\x20close\r\nLocation:\
SF:x20https://prod-backend-2068211183\.us-east-1\.elb\.amazonaws\.com:443/
SF:\r\n\r\n<html>\r\n<head><title>301\x20Moved\x20Permanently</title></hea
SF:d>\r\n<body>\r\n<center><h1>301\x20Moved\x20Permanently</h1></center>\r
SF:\n</body>\r\n</html>\r\n")%r(RTSPRequest,7A,"<html>\r\n<head><title>400
SF:\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x
SF:20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(X11Probe,110,"HTT
SF:P/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20S
SF:at,\x2019\x20Oct\x202024\x2019:26:54\x20GMT\r\nContent-Type:\x20text/ht
SF:ml\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n\r\n<html>\r\n<
SF:head><title>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><
SF:h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(Fo
SF:urOhFourRequest,191,"HTTP/1\.1\x20301\x20Moved\x20Permanently\r\nServer
SF::\x20awselb/2\.0\r\nDate:\x20Sat,\x2019\x20Oct\x202024\x2019:26:54\x20G
SF:MT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20134\r\nConnectio
SF:n:\x20close\r\nLocation:\x20https://prod-backend-2068211183\.us-east-1\
SF:.elb\.amazonaws\.com:443/nice%20ports%2C/Tri%6Eity\.txt%2ebak\r\n\r\n<h
SF:tml>\r\n<head><title>301\x20Moved\x20Permanently</title></head>\r\n<bod
SF:y>\r\n<center><h1>301\x20Moved\x20Permanently</h1></center>\r\n</body>\
SF:r\n</html>\r\n")%r(RPCCheck,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\n
SF:Server:\x20awselb/2\.0\r\nDate:\x20Sat,\x2019\x20Oct\x202024\x2019:26:5
SF:9\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\r\nCon
SF:nection:\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Request</
SF:title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></cent
SF:er>\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 4.X (87%)
OS CPE: cpe:/o:linux:linux_kernel:4.2
Aggressive OS guesses: Linux 4.2 (87%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 14 hops

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.67 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   0.94 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.78 ms be5471.ccr21.elp02.atlas.cogentco.com (154.54.166.57)
7   32.49 ms be3821.ccr31.dfw01.atlas.cogentco.com (154.54.165.25)
8   32.60 ms be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74)
9   ... 13
14  58.74 ms ec2-18-205-139-112.compute-1.amazonaws.com (18.205.139.112)

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 34.15 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
18.205.139.112
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 my-care-plan.com
Scan date
19 Oct 2024 15:27
Durée de l'analyse
34.15seconde
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: