Analyser le rapport pour "api.veeva.link"

  1. Portscanner en ligne
  2. Analyser le rapport pour "api.veeva.link"
Niveau d'adhésion: Membre gratuit
Sommaire

Ports

1

Durée

48.64seconde

Date

2024-11-29

IP

18.202.60.163

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A api.veeva.link)
Nmap scan report for api.veeva.link (18.202.60.163)
Host is up (0.15s latency).
Other addresses for api.veeva.link (not scanned): 34.241.126.108 52.31.57.131
rDNS record for 18.202.60.163: ec2-18-202-60-163.eu-west-1.compute.amazonaws.com
Not shown: 999 filtered tcp ports (no-response)
PORT    STATE SERVICE        VERSION
443/tcp open  ssl/http-proxy (bad gateway)
| http-server-header: 
|   awselb/2.0
|_  nginx
|_http-title: Not Found
| ssl-cert: Subject: commonName=*.veeva.link/organizationName=Veeva Systems Inc./stateOrProvinceName=California/countryName=US
| Subject Alternative Name: DNS:*.veeva.link, DNS:veeva.link
| Not valid before: 2024-07-30T00:00:00
|_Not valid after:  2025-02-21T23:59:59
| fingerprint-strings: 
|   FourOhFourRequest, HTTPOptions: 
|     HTTP/1.1 502 Bad Gateway
|     Server: awselb/2.0
|     Date: Fri, 29 Nov 2024 17:27:07 GMT
|     Content-Type: text/html
|     Content-Length: 122
|     Connection: close
|     <html>
|     <head><title>502 Bad Gateway</title></head>
|     <body>
|     <center><h1>502 Bad Gateway</h1></center>
|     </body>
|     </html>
|   GetRequest: 
|     HTTP/1.1 502 Bad Gateway
|     Server: awselb/2.0
|     Date: Fri, 29 Nov 2024 17:27:06 GMT
|     Content-Type: text/html
|     Content-Length: 122
|     Connection: close
|     <html>
|     <head><title>502 Bad Gateway</title></head>
|     <body>
|     <center><h1>502 Bad Gateway</h1></center>
|     </body>
|     </html>
|   Help, SSLSessionReq: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Fri, 29 Nov 2024 17:27:14 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>
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=6749F96A%P=x86_64-redhat-linu
SF:x-gnu%r(GetRequest,110,"HTTP/1\.1\x20502\x20Bad\x20Gateway\r\nServer:\x
SF:20awselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\x202024\x2017:27:06\x20GMT\
SF:r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\r\nConnection:\
SF:x20close\r\n\r\n<html>\r\n<head><title>502\x20Bad\x20Gateway</title></h
SF:ead>\r\n<body>\r\n<center><h1>502\x20Bad\x20Gateway</h1></center>\r\n</
SF:body>\r\n</html>\r\n")%r(HTTPOptions,110,"HTTP/1\.1\x20502\x20Bad\x20Ga
SF:teway\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\x202024\x
SF:2017:27:07\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x201
SF:22\r\nConnection:\x20close\r\n\r\n<html>\r\n<head><title>502\x20Bad\x20
SF:Gateway</title></head>\r\n<body>\r\n<center><h1>502\x20Bad\x20Gateway</
SF:h1></center>\r\n</body>\r\n</html>\r\n")%r(FourOhFourRequest,110,"HTTP/
SF:1\.1\x20502\x20Bad\x20Gateway\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri
SF:,\x2029\x20Nov\x202024\x2017:27:07\x20GMT\r\nContent-Type:\x20text/html
SF:\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n\r\n<html>\r\n<he
SF:ad><title>502\x20Bad\x20Gateway</title></head>\r\n<body>\r\n<center><h1
SF:>502\x20Bad\x20Gateway</h1></center>\r\n</body>\r\n</html>\r\n")%r(RTSP
SF:Request,7A,"<html>\r\n<head><title>400\x20Bad\x20Request</title></head>
SF:\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n</body
SF:>\r\n</html>\r\n")%r(Help,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nSe
SF:rver:\x20awselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\x202024\x2017:27:14\
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(SSLSessionReq,110,"HTTP/1\.1\x20400\x20
SF:Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDate:\x20Fri,\x2029\x20Nov\
SF:x202024\x2017:27:14\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");
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 (86%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 18 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   0.57 ms   gw.mcom-colocationamerica.com (208.64.231.81)
3   1.93 ms   r1b4.n1p1400.lax.multacom.net (64.69.46.9)
4   ...
5   12.43 ms  be2931.ccr31.phx01.atlas.cogentco.com (154.54.44.85)
6   21.29 ms  be5471.ccr21.elp02.atlas.cogentco.com (154.54.166.57)
7   32.34 ms  be3821.ccr31.dfw01.atlas.cogentco.com (154.54.165.25)
8   46.63 ms  be5024.ccr41.atl01.atlas.cogentco.com (154.54.163.41)
9   63.43 ms  be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157)
10  62.97 ms  port-channel5042.ccr92.dca04.atlas.cogentco.com (154.54.162.221)
11  67.85 ms  be4188.ccr42.jfk02.atlas.cogentco.com (154.54.30.122)
12  136.81 ms be4324.ccr51.lhr01.atlas.cogentco.com (154.54.93.10)
13  136.93 ms amazon.demarc.cogentco.com (149.11.167.138)
14  ... 17
18  151.96 ms ec2-18-202-60-163.eu-west-1.compute.amazonaws.com (18.202.60.163)

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 48.64 seconds
Schéma de couleur
Trustpilot
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
18.202.60.163
Statut d'hôte
UP
Pays cible
L'emplacement IP cible est Irlande
Irlande
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 api.veeva.link
Scan date
29 Nov 2024 12:27
API - Scan ID
Durée de l'analyse
48.64seconde
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: