Analyser le rapport pour "my.telegram.org"
Sommaire
Ports
2
Durée
39.66seconde
Date
2024-11-26
IP
149.154.167.99
Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A my.telegram.org)
Nmap scan report for my.telegram.org (149.154.167.99) Host is up (0.14s latency). Other addresses for my.telegram.org (not scanned): 2001:67c:4e8:f004::9 Not shown: 991 filtered tcp ports (no-response), 7 filtered tcp ports (admin-prohibited) PORT STATE SERVICE VERSION 80/tcp open http nginx 1.18.0 |_http-title: Did not follow redirect to https://my.telegram.org/ |_http-server-header: nginx/1.18.0 443/tcp open ssl/http nginx 1.18.0 | http-title: Authorization |_Requested resource was /auth |_http-trane-info: Problem with XML parsing of /evox/about | ssl-cert: Subject: commonName=*.telegram.org | Subject Alternative Name: DNS:*.telegram.org, DNS:telegram.org | Not valid before: 2024-08-10T13:33:14 |_Not valid after: 2025-09-11T13:33:14 |_ssl-date: TLS randomness does not represent time |_http-server-header: nginx/1.18.0 Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port Device type: general purpose|specialized|storage-misc Running (JUST GUESSING): Linux 3.X|4.X (88%), Crestron 2-Series (87%), HP embedded (85%) OS CPE: cpe:/o:linux:linux_kernel:3 cpe:/o:linux:linux_kernel:4 cpe:/o:crestron:2_series cpe:/h:hp:p2000_g3 Aggressive OS guesses: Linux 3.10 - 4.11 (88%), Linux 3.2 - 4.9 (88%), Linux 4.10 (88%), Crestron XPanel control system (87%), Linux 3.16 (86%), Linux 3.2 (86%), HP P2000 G3 NAS device (85%) No exact OS matches for host (test conditions non-ideal). Network Distance: 19 hops TRACEROUTE (using port 443/tcp) HOP RTT ADDRESS 1 0.19 ms 208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177) 2 0.60 ms gw.mcom-colocationamerica.com (208.64.231.81) 3 0.62 ms r1b4.n1p1400.lax.multacom.net (64.69.46.9) 4 ... 5 12.38 ms be2931.ccr31.phx01.atlas.cogentco.com (154.54.44.85) 6 21.31 ms be5471.ccr21.elp02.atlas.cogentco.com (154.54.166.57) 7 32.61 ms be3821.ccr31.dfw01.atlas.cogentco.com (154.54.165.25) 8 46.96 ms be5024.ccr41.atl01.atlas.cogentco.com (154.54.163.41) 9 63.67 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 140.86 ms be4155.ccr41.jfk02.atlas.cogentco.com (154.54.30.42) 12 135.71 ms be2490.ccr42.lon13.atlas.cogentco.com (154.54.42.86) 13 144.29 ms be3393.ccr51.lhr01.atlas.cogentco.com (154.54.47.142) 14 152.70 ms be3487.ccr41.lon13.atlas.cogentco.com (154.54.60.5) 15 144.37 ms be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94) 16 ... 18 19 138.54 ms 149.154.167.99 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 39.66 seconds
Schéma de couleur
-
- Cible
-
IP cible
149.154.167.99
-
Statut d'hôte
UP
-
Pays cible
Royaume-Uni de Grande-Bretagne et d'Irlande du Nord
- 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.telegram.org
-
Scan date
26 Nov 2024 23:53
- API - Scan ID
-
Durée de l'analyse
39.66seconde
-
Copier le rapport de numérisation
- Télécharger le rapport
- Remove scan result
- Total scans
- Scannez plus
- 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
- 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