Analyser le rapport pour "wjapi.oswjql.com"

  1. Portscanner en ligne
  2. Analyser le rapport pour "wjapi.oswjql.com"
Niveau d'adhésion: Membre gratuit

wjapi.oswjql.com

47.242.254.41L'emplacement IP cible est Hong Kong

Sommaire

Ports

1

Durée

1min 3seconde (63seconde)

Date

2025-08-01

IP

47.242.254.41

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A wjapi.oswjql.com)
Nmap scan report for wjapi.oswjql.com (47.242.254.41)
Host is up (0.15s latency).
Other addresses for wjapi.oswjql.com (not scanned): 47.242.193.149 47.242.253.98
Not shown: 999 filtered tcp ports (no-response)
PORT    STATE SERVICE   VERSION
443/tcp open  ssl/https
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 404 Not Found
|     Date: Sat, 02 Aug 2025 03:41:06 GMT
|     Content-Type: application/json
|     Content-Length: 130
|     Connection: close
|     Vary: Origin
|     Vary: Access-Control-Request-Method
|     Vary: Access-Control-Request-Headers
|     "timestamp":1754106066021,
|     "status":404,
|     "error":"Not Found",
|     "message":"",
|     "path":"/nice%20ports%2C/Tri%6Eity.txt%2ebak"
|   GetRequest: 
|     HTTP/1.1 200 OK
|     Date: Sat, 02 Aug 2025 03:41:04 GMT
|     Content-Length: 0
|     Connection: close
|     Vary: Origin
|     Vary: Access-Control-Request-Method
|     Vary: Access-Control-Request-Headers
|   HTTPOptions: 
|     HTTP/1.1 200 OK
|     Date: Sat, 02 Aug 2025 03:41:05 GMT
|     Content-Length: 0
|     Connection: close
|     Allow: GET,HEAD,OPTIONS
|     Vary: Origin
|     Vary: Access-Control-Request-Method
|     Vary: Access-Control-Request-Headers
|   RPCCheck: 
|     HTTP/1.1 400 Bad Request
|     Date: Sat, 02 Aug 2025 03:41:13 GMT
|     Content-Type: text/html
|     Content-Length: 164
|     Connection: close
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body bgcolor="white">
|     <center><h1>400 Bad Request</h1></center>
|     <hr><center>alb</center>
|     </body>
|     </html>
|   RTSPRequest: 
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body bgcolor="white">
|     <center><h1>400 Bad Request</h1></center>
|     <hr><center>alb</center>
|     </body>
|     </html>
|   tor-versions: 
|     HTTP/1.1 400 Bad Request
|     Date: Sat, 02 Aug 2025 03:41:06 GMT
|     Content-Type: text/html
|     Content-Length: 164
|     Connection: close
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body bgcolor="white">
|     <center><h1>400 Bad Request</h1></center>
|     <hr><center>alb</center>
|     </body>
|_    </html>
| tls-nextprotoneg: 
|   h2
|_  http/1.1
|_http-cors: HEAD GET POST PUT DELETE TRACE OPTIONS PATCH
|_http-title: Site doesn't have a title.
| ssl-cert: Subject: commonName=wjapi.oswjql.com
| Subject Alternative Name: DNS:wjapi.oswjql.com
| Not valid before: 2024-11-13T00:00:00
|_Not valid after:  2025-11-13T23:59:59
|_ssl-date: TLS randomness does not represent time
| tls-alpn: 
|_  http/1.1
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=8/1%Time=688D88D0%P=x86_64-redhat-linux-
SF:gnu%r(GetRequest,B7,"HTTP/1\.1\x20200\x20OK\r\nDate:\x20Sat,\x2002\x20A
SF:ug\x202025\x2003:41:04\x20GMT\r\nContent-Length:\x200\r\nConnection:\x2
SF:0close\r\nVary:\x20Origin\r\nVary:\x20Access-Control-Request-Method\r\n
SF:Vary:\x20Access-Control-Request-Headers\r\n\r\n")%r(HTTPOptions,D0,"HTT
SF:P/1\.1\x20200\x20OK\r\nDate:\x20Sat,\x2002\x20Aug\x202025\x2003:41:05\x
SF:20GMT\r\nContent-Length:\x200\r\nConnection:\x20close\r\nAllow:\x20GET,
SF:HEAD,OPTIONS\r\nVary:\x20Origin\r\nVary:\x20Access-Control-Request-Meth
SF:od\r\nVary:\x20Access-Control-Request-Headers\r\n\r\n")%r(FourOhFourReq
SF:uest,162,"HTTP/1\.1\x20404\x20Not\x20Found\r\nDate:\x20Sat,\x2002\x20Au
SF:g\x202025\x2003:41:06\x20GMT\r\nContent-Type:\x20application/json\r\nCo
SF:ntent-Length:\x20130\r\nConnection:\x20close\r\nVary:\x20Origin\r\nVary
SF::\x20Access-Control-Request-Method\r\nVary:\x20Access-Control-Request-H
SF:eaders\r\n\r\n{\n\t\"timestamp\":1754106066021,\n\t\"status\":404,\n\t\
SF:"error\":\"Not\x20Found\",\n\t\"message\":\"\",\n\t\"path\":\"/nice%20p
SF:orts%2C/Tri%6Eity\.txt%2ebak\"\n}")%r(tor-versions,126,"HTTP/1\.1\x2040
SF:0\x20Bad\x20Request\r\nDate:\x20Sat,\x2002\x20Aug\x202025\x2003:41:06\x
SF:20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20164\r\nConnec
SF:tion:\x20close\r\n\r\n<html>\r\n<head><title>400\x20Bad\x20Request</tit
SF:le></head>\r\n<body\x20bgcolor=\"white\">\r\n<center><h1>400\x20Bad\x20
SF:Request</h1></center>\r\n<hr><center>alb</center>\r\n</body>\r\n</html>
SF:\r\n")%r(RTSPRequest,A4,"<html>\r\n<head><title>400\x20Bad\x20Request</
SF:title></head>\r\n<body\x20bgcolor=\"white\">\r\n<center><h1>400\x20Bad\
SF:x20Request</h1></center>\r\n<hr><center>alb</center>\r\n</body>\r\n</ht
SF:ml>\r\n")%r(RPCCheck,126,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nDate:\x
SF:20Sat,\x2002\x20Aug\x202025\x2003:41:13\x20GMT\r\nContent-Type:\x20text
SF:/html\r\nContent-Length:\x20164\r\nConnection:\x20close\r\n\r\n<html>\r
SF:\n<head><title>400\x20Bad\x20Request</title></head>\r\n<body\x20bgcolor
SF:=\"white\">\r\n<center><h1>400\x20Bad\x20Request</h1></center>\r\n<hr><
SF:center>alb</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
OS fingerprint not ideal because: Missing a closed TCP port so results incomplete
No OS matches for host
Network Distance: 15 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.63 ms   gw.mcom-colocationamerica.com (208.64.231.81)
3   0.95 ms   r1b4.n1p1400.lax.multacom.net (64.69.46.9)
4   0.52 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   99.16 ms  ae-14.r33.tokyjp05.jp.bb.gin.ntt.net (129.250.3.192)
7   99.38 ms  ae-4.r32.tokyjp05.jp.bb.gin.ntt.net (129.250.5.55)
8   ...
9   155.10 ms ae-20.a01.newthk04.hk.bb.gin.ntt.net (129.250.2.255)
10  ... 11
12  149.28 ms 47.246.116.53
13  ... 14
15  153.93 ms 47.242.254.41

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 63.31 seconds
Schéma de couleur
Trustpilot
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
47.242.254.41
Statut d'hôte
UP
Pays cible
L'emplacement IP cible est Hong Kong
Hong Kong
Scan gratuit
Scan gratuit
Méthode
Analyser les informations du système d'exploitation et Traceroute
État de l'analyse
Ports 1 identifiés
Exécuter la commande
nmap -A wjapi.oswjql.com
Scan date
01 Aug 2025 23:41
API - Scan ID
Durée de l'analyse
1min 3seconde (63seconde)
Copier le rapport de numérisation
Télécharger le rapport
Remove scan result
$
Total scans
Scannez plus
Prix

INSCRITE

Caractéristiques

5 scans/jour

Appels API quotidiens - 20 requêtes

Enregistrer le journal

Analyse publique

Analyse OSINT

Analyse non répertoriée

Analyse privé

Pas de Ads

Supprimer après l'analyse

Supprimer le résultat de l'analyse

Méthodes supplémentaires de numérisation

Cette option convient aux débutants qui souhaitent vérifier si leur hôte dispose de ports ouverts accessibles de l'extérieur.

$0.00

Durée de vie

Enregistrer

PROFESSIONNELLE

Caractéristiques

10 000 scans/jour

Appels API quotidiens - 100 000 requêtes

Enregistrer le journal

Analyse publique

Analyse OSINT

Analyse non répertoriée

Analyse privé

Pas de Ads

Supprimer après l'analyse

Supprimer le résultat de l'analyse

Méthodes supplémentaires de numérisation

Cette option est idéale pour les professionnels qui ont besoin de tester les ports ouverts de leur hôte à partir d'une source externe.

$7.50 $3.75/mois

Facturé annuellement @ $45.00 - 50% réduction

Devenez professionnel