Analyser le rapport pour "sdk-metrics.rudderstack.com"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

1

Durée

42.22seconde

Date

2024-09-30

IP

3.214.14.15

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A sdk-metrics.rudderstack.com)
Nmap scan report for sdk-metrics.rudderstack.com (3.214.14.15)
Host is up (0.061s latency).
Other addresses for sdk-metrics.rudderstack.com (not scanned): 107.21.58.244 54.227.104.74
rDNS record for 3.214.14.15: ec2-3-214-14-15.compute-1.amazonaws.com
Not shown: 999 filtered tcp ports (no-response)
PORT    STATE SERVICE   VERSION
443/tcp open  ssl/https awselb/2.0
| ssl-cert: Subject: commonName=*.rudderstack.com
| Subject Alternative Name: DNS:*.rudderstack.com
| Not valid before: 2024-09-21T00:00:00
|_Not valid after:  2025-10-18T23:59:59
|_http-title: Site doesn't have a title (text/plain; charset=utf-8).
| fingerprint-strings: 
|   DNSVersionBindReqTCP: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Mon, 30 Sep 2024 10:23:07 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 404 Not Found
|     Server: awselb/2.0
|     Date: Mon, 30 Sep 2024 10:23:00 GMT
|     Content-Type: text/plain; charset=utf-8
|     Content-Length: 0
|     Connection: close
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Mon, 30 Sep 2024 10:23: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>
|   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: Mon, 30 Sep 2024 10:23:01 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-server-header: awselb/2.0
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/30%Time=66FA7C03%P=x86_64-redhat-linux
SF:-gnu%r(GetRequest,A2,"HTTP/1\.1\x20404\x20Not\x20Found\r\nServer:\x20aw
SF:selb/2\.0\r\nDate:\x20Mon,\x2030\x20Sep\x202024\x2010:23:00\x20GMT\r\nC
SF:ontent-Type:\x20text/plain;\x20charset=utf-8\r\nContent-Length:\x200\r\
SF:nConnection:\x20close\r\n\r\n")%r(HTTPOptions,A2,"HTTP/1\.1\x20404\x20N
SF:ot\x20Found\r\nServer:\x20awselb/2\.0\r\nDate:\x20Mon,\x2030\x20Sep\x20
SF:2024\x2010:23:00\x20GMT\r\nContent-Type:\x20text/plain;\x20charset=utf-
SF:8\r\nContent-Length:\x200\r\nConnection:\x20close\r\n\r\n")%r(FourOhFou
SF:rRequest,A2,"HTTP/1\.1\x20404\x20Not\x20Found\r\nServer:\x20awselb/2\.0
SF:\r\nDate:\x20Mon,\x2030\x20Sep\x202024\x2010:23:00\x20GMT\r\nContent-Ty
SF:pe:\x20text/plain;\x20charset=utf-8\r\nContent-Length:\x200\r\nConnecti
SF:on:\x20close\r\n\r\n")%r(tor-versions,110,"HTTP/1\.1\x20400\x20Bad\x20R
SF:equest\r\nServer:\x20awselb/2\.0\r\nDate:\x20Mon,\x2030\x20Sep\x202024\
SF:x2010:23:01\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20
SF:122\r\nConnection:\x20close\r\n\r\n<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(RTSPRequest,7A,"<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(RP
SF:CCheck,110,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.
SF:0\r\nDate:\x20Mon,\x2030\x20Sep\x202024\x2010:23:06\x20GMT\r\nContent-T
SF:ype:\x20text/html\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n
SF:\r\n<html>\r\n<head><title>400\x20Bad\x20Request</title></head>\r\n<bod
SF:y>\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\n</h
SF:tml>\r\n")%r(DNSVersionBindReqTCP,110,"HTTP/1\.1\x20400\x20Bad\x20Reque
SF:st\r\nServer:\x20awselb/2\.0\r\nDate:\x20Mon,\x2030\x20Sep\x202024\x201
SF:0:23:07\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20122\
SF:r\nConnection:\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Req
SF:uest</title></head>\r\n<body>\r\n<center><h1>400\x20Bad\x20Request</h1>
SF:</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: 16 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.81 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   0.61 ms  r1b4.n1p1400.lax.multacom.net (64.69.46.9)
4   0.49 ms  ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   ...
6   32.67 ms ae-3.r22.dllstx14.us.bb.gin.ntt.net (129.250.7.68)
7   32.79 ms ae-22.a01.dllstx14.us.bb.gin.ntt.net (129.250.3.115)
8   33.24 ms ae-0.amazon.dllstx14.us.bb.gin.ntt.net (128.241.14.138)
9   33.82 ms 15.230.130.149
10  33.12 ms 176.32.125.155
11  ... 15
16  59.29 ms ec2-3-214-14-15.compute-1.amazonaws.com (3.214.14.15)

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 42.22 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
3.214.14.15
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 sdk-metrics.rudderstack.com
Scan date
30 Sep 2024 06:23
Durée de l'analyse
42.22seconde
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: