Analyser le rapport pour "ossrs.net"

Niveau d'adhésion: Membre gratuit
Sommaire

Ports

8

Durée

3min 27.86seconde (207.86seconde)

Date

2024-12-25

IP

116.62.157.94

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A ossrs.net)
Nmap scan report for ossrs.net (116.62.157.94)
Host is up (0.15s latency).
Not shown: 992 filtered tcp ports (no-response)
PORT     STATE  SERVICE    VERSION
22/tcp   open   ssh        OpenSSH 8.2p1 Ubuntu 4ubuntu0.1 (Ubuntu Linux; protocol 2.0)
| ssh-hostkey: 
|   3072 b3:a7:54:14:b7:41:8d:6d:39:8a:48:9e:12:01:28:a0 (RSA)
|   256 26:02:3e:02:b6:70:f4:01:5c:31:3c:e4:0f:fa:47:8f (ECDSA)
|_  256 98:8c:64:a6:fa:78:5e:72:80:b8:61:a7:82:1a:f7:ea (ED25519)
80/tcp   open   http       nginx
|_http-title: SRS
443/tcp  open   ssl/http   nginx
|_http-title: SRS
| ssl-cert: Subject: commonName=www.ossrs.net
| Subject Alternative Name: DNS:ossrs.net, DNS:www.ossrs.net
| Not valid before: 2024-10-16T20:30:45
|_Not valid after:  2025-01-14T20:30:44
| tls-nextprotoneg: 
|   h2
|_  http/1.1
| tls-alpn: 
|   h2
|_  http/1.1
|_ssl-date: TLS randomness does not represent time
1935/tcp open   rtmp?
2022/tcp open   down?
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.0 302 Found
|     Access-Control-Allow-Credentials: true
|     Access-Control-Allow-Headers: *
|     Access-Control-Allow-Methods: *
|     Access-Control-Allow-Origin: *
|     Access-Control-Expose-Headers: *
|     Content-Type: text/html; charset=utf-8
|     Location: /mgmt
|     Server: Oryx/v5.15.20
|     Date: Wed, 25 Dec 2024 17:39:25 GMT
|     Content-Length: 28
|     href="/mgmt">Found</a>.
|   GenericLines, Help, Kerberos, RTSPRequest, SSLSessionReq, TLSSessionReq, TerminalServerCookie: 
|     HTTP/1.1 400 Bad Request
|     Content-Type: text/plain; charset=utf-8
|     Connection: close
|     Request
|   GetRequest: 
|     HTTP/1.0 302 Found
|     Access-Control-Allow-Credentials: true
|     Access-Control-Allow-Headers: *
|     Access-Control-Allow-Methods: *
|     Access-Control-Allow-Origin: *
|     Access-Control-Expose-Headers: *
|     Content-Type: text/html; charset=utf-8
|     Location: /mgmt
|     Server: Oryx/v5.15.20
|     Date: Wed, 25 Dec 2024 17:38:57 GMT
|     Content-Length: 28
|     href="/mgmt">Found</a>.
|   HTTPOptions: 
|     HTTP/1.0 200 OK
|     Access-Control-Allow-Credentials: true
|     Access-Control-Allow-Headers: *
|     Access-Control-Allow-Methods: *
|     Access-Control-Allow-Origin: *
|     Access-Control-Expose-Headers: *
|     Server: Oryx/v5.15.20
|     Date: Wed, 25 Dec 2024 17:38:57 GMT
|_    Content-Length: 0
5060/tcp closed sip
7800/tcp open   http       Ajenti http control panel
|_http-title: 404 Not Found
|_http-server-header: nginx
9000/tcp closed cslistener
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-Port2022-TCP:V=7.92%I=7%D=12/25%Time=676C4331%P=x86_64-redhat-linux-gnu
SF:%r(GenericLines,67,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nContent-Type:
SF:\x20text/plain;\x20charset=utf-8\r\nConnection:\x20close\r\n\r\n400\x20
SF:Bad\x20Request")%r(GetRequest,167,"HTTP/1\.0\x20302\x20Found\r\nAccess-
SF:Control-Allow-Credentials:\x20true\r\nAccess-Control-Allow-Headers:\x20
SF:\*\r\nAccess-Control-Allow-Methods:\x20\*\r\nAccess-Control-Allow-Origi
SF:n:\x20\*\r\nAccess-Control-Expose-Headers:\x20\*\r\nContent-Type:\x20te
SF:xt/html;\x20charset=utf-8\r\nLocation:\x20/mgmt\r\nServer:\x20Oryx/v5\.
SF:15\.20\r\nDate:\x20Wed,\x2025\x20Dec\x202024\x2017:38:57\x20GMT\r\nCont
SF:ent-Length:\x2028\r\n\r\n<a\x20href=\"/mgmt\">Found</a>\.\n\n")%r(HTTPO
SF:ptions,10E,"HTTP/1\.0\x20200\x20OK\r\nAccess-Control-Allow-Credentials:
SF:\x20true\r\nAccess-Control-Allow-Headers:\x20\*\r\nAccess-Control-Allow
SF:-Methods:\x20\*\r\nAccess-Control-Allow-Origin:\x20\*\r\nAccess-Control
SF:-Expose-Headers:\x20\*\r\nServer:\x20Oryx/v5\.15\.20\r\nDate:\x20Wed,\x
SF:2025\x20Dec\x202024\x2017:38:57\x20GMT\r\nContent-Length:\x200\r\n\r\n"
SF:)%r(RTSPRequest,67,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nContent-Type:
SF:\x20text/plain;\x20charset=utf-8\r\nConnection:\x20close\r\n\r\n400\x20
SF:Bad\x20Request")%r(Help,67,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nConte
SF:nt-Type:\x20text/plain;\x20charset=utf-8\r\nConnection:\x20close\r\n\r\
SF:n400\x20Bad\x20Request")%r(SSLSessionReq,67,"HTTP/1\.1\x20400\x20Bad\x2
SF:0Request\r\nContent-Type:\x20text/plain;\x20charset=utf-8\r\nConnection
SF::\x20close\r\n\r\n400\x20Bad\x20Request")%r(TerminalServerCookie,67,"HT
SF:TP/1\.1\x20400\x20Bad\x20Request\r\nContent-Type:\x20text/plain;\x20cha
SF:rset=utf-8\r\nConnection:\x20close\r\n\r\n400\x20Bad\x20Request")%r(TLS
SF:SessionReq,67,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nContent-Type:\x20t
SF:ext/plain;\x20charset=utf-8\r\nConnection:\x20close\r\n\r\n400\x20Bad\x
SF:20Request")%r(Kerberos,67,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nConten
SF:t-Type:\x20text/plain;\x20charset=utf-8\r\nConnection:\x20close\r\n\r\n
SF:400\x20Bad\x20Request")%r(FourOhFourRequest,167,"HTTP/1\.0\x20302\x20Fo
SF:und\r\nAccess-Control-Allow-Credentials:\x20true\r\nAccess-Control-Allo
SF:w-Headers:\x20\*\r\nAccess-Control-Allow-Methods:\x20\*\r\nAccess-Contr
SF:ol-Allow-Origin:\x20\*\r\nAccess-Control-Expose-Headers:\x20\*\r\nConte
SF:nt-Type:\x20text/html;\x20charset=utf-8\r\nLocation:\x20/mgmt\r\nServer
SF::\x20Oryx/v5\.15\.20\r\nDate:\x20Wed,\x2025\x20Dec\x202024\x2017:39:25\
SF:x20GMT\r\nContent-Length:\x2028\r\n\r\n<a\x20href=\"/mgmt\">Found</a>\.
SF:\n\n");
Aggressive OS guesses: Linux 2.6.32 - 3.13 (95%), Linux 5.4 (94%), Linux 5.0 - 5.4 (94%), Linux 5.0 (93%), Linux 2.6.32 (92%), Linux 3.2 - 4.9 (92%), Linux 4.15 - 5.6 (92%), Linux 2.6.32 - 3.10 (92%), HP P2000 G3 NAS device (91%), Infomir MAG-250 set-top box (91%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 18 hops
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

TRACEROUTE (using port 80/tcp)
HOP RTT       ADDRESS
1   0.26 ms   208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.82 ms   gw.mcom-colocationamerica.com (208.64.231.81)
3   2.36 ms   r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   0.57 ms   ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   0.37 ms   ae-1.r27.lsanca07.us.bb.gin.ntt.net (129.250.3.242)
6   10.85 ms  ae-7.r26.snjsca04.us.bb.gin.ntt.net (129.250.4.150)
7   9.56 ms   ae-19.a03.snjsca04.us.bb.gin.ntt.net (129.250.5.25)
8   12.08 ms  218.30.53.50
9   130.84 ms 202.97.92.77
10  ...
11  133.49 ms 202.97.24.193
12  136.56 ms 202.97.100.226
13  138.90 ms 115.233.23.162
14  148.07 ms 122.224.214.78
15  ... 17
18  146.36 ms 116.62.157.94

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 207.86 seconds
Schéma de couleur
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
116.62.157.94
Statut d'hôte
UP
Pays cible
L'emplacement IP cible est Chine
Chine
Scan gratuit
Scan gratuit
Méthode de numérisation
Analyser les informations du système d'exploitation et Traceroute
État de l'analyse
Ports 8 identifiés
Exécuter la commande
nmap -A ossrs.net
Scan date
25 Dec 2024 12:42
API - Scan ID
Durée de l'analyse
3min 27.86seconde (207.86seconde)
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: