Analyser le rapport pour "testfairy.com"

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

Ports

3

Durée

31.6seconde

Date

2024-09-25

IP

44.194.165.184

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A testfairy.com)
Nmap scan report for testfairy.com (44.194.165.184)
Host is up (0.062s latency).
Other addresses for testfairy.com (not scanned): 18.213.92.46
rDNS record for 44.194.165.184: ec2-44-194-165-184.compute-1.amazonaws.com
Not shown: 997 filtered tcp ports (no-response)
PORT    STATE  SERVICE  VERSION
22/tcp  closed ssh
80/tcp  open   http     awselb/2.0
| fingerprint-strings: 
|   FourOhFourRequest: 
|     HTTP/1.1 301 Moved Permanently
|     Server: awselb/2.0
|     Date: Wed, 25 Sep 2024 12:20:53 GMT
|     Content-Type: text/html
|     Content-Length: 134
|     Connection: close
|     Location: https://www-load-balancer-912276808.us-east-1.elb.amazonaws.com:443/nice%20ports%2C/Tri%6Eity.txt%2ebak
|     <html>
|     <head><title>301 Moved Permanently</title></head>
|     <body>
|     <center><h1>301 Moved Permanently</h1></center>
|     </body>
|     </html>
|   GetRequest, HTTPOptions: 
|     HTTP/1.1 301 Moved Permanently
|     Server: awselb/2.0
|     Date: Wed, 25 Sep 2024 12:20:53 GMT
|     Content-Type: text/html
|     Content-Length: 134
|     Connection: close
|     Location: https://www-load-balancer-912276808.us-east-1.elb.amazonaws.com:443/
|     <html>
|     <head><title>301 Moved Permanently</title></head>
|     <body>
|     <center><h1>301 Moved Permanently</h1></center>
|     </body>
|     </html>
|   RTSPRequest: 
|     <html>
|     <head><title>400 Bad Request</title></head>
|     <body>
|     <center><h1>400 Bad Request</h1></center>
|     </body>
|     </html>
|   X11Probe: 
|     HTTP/1.1 400 Bad Request
|     Server: awselb/2.0
|     Date: Wed, 25 Sep 2024 12:20:53 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-title: Did not follow redirect to https://testfairy.com:443/
|_http-server-header: awselb/2.0
443/tcp open   ssl/http Apache httpd
| tls-nextprotoneg: 
|   h2
|_  http/1.1
| ssl-cert: Subject: commonName=*.testfairy.com
| Subject Alternative Name: DNS:*.testfairy.com, DNS:testfairy.com
| Not valid before: 2024-08-20T00:00:00
|_Not valid after:  2025-08-19T23:59:59
|_ssl-date: TLS randomness does not represent time
| http-methods: 
|_  Potentially risky methods: TRACE
|_http-title: TestFairy - Mobile Beta Testing
| tls-alpn: 
|   h2
|_  http/1.1
|_http-server-header: Apache
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-Port80-TCP:V=7.92%I=7%D=9/25%Time=66F40024%P=x86_64-redhat-linux-gnu%r(
SF:GetRequest,172,"HTTP/1\.1\x20301\x20Moved\x20Permanently\r\nServer:\x20
SF:awselb/2\.0\r\nDate:\x20Wed,\x2025\x20Sep\x202024\x2012:20:53\x20GMT\r\
SF:nContent-Type:\x20text/html\r\nContent-Length:\x20134\r\nConnection:\x2
SF:0close\r\nLocation:\x20https://www-load-balancer-912276808\.us-east-1\.
SF:elb\.amazonaws\.com:443/\r\n\r\n<html>\r\n<head><title>301\x20Moved\x20
SF:Permanently</title></head>\r\n<body>\r\n<center><h1>301\x20Moved\x20Per
SF:manently</h1></center>\r\n</body>\r\n</html>\r\n")%r(HTTPOptions,172,"H
SF:TTP/1\.1\x20301\x20Moved\x20Permanently\r\nServer:\x20awselb/2\.0\r\nDa
SF:te:\x20Wed,\x2025\x20Sep\x202024\x2012:20:53\x20GMT\r\nContent-Type:\x2
SF:0text/html\r\nContent-Length:\x20134\r\nConnection:\x20close\r\nLocatio
SF:n:\x20https://www-load-balancer-912276808\.us-east-1\.elb\.amazonaws\.c
SF:om:443/\r\n\r\n<html>\r\n<head><title>301\x20Moved\x20Permanently</titl
SF:e></head>\r\n<body>\r\n<center><h1>301\x20Moved\x20Permanently</h1></ce
SF:nter>\r\n</body>\r\n</html>\r\n")%r(RTSPRequest,7A,"<html>\r\n<head><ti
SF:tle>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<center><h1>400\x
SF:20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n")%r(X11Probe,1
SF:10,"HTTP/1\.1\x20400\x20Bad\x20Request\r\nServer:\x20awselb/2\.0\r\nDat
SF:e:\x20Wed,\x2025\x20Sep\x202024\x2012:20:53\x20GMT\r\nContent-Type:\x20
SF:text/html\r\nContent-Length:\x20122\r\nConnection:\x20close\r\n\r\n<htm
SF:l>\r\n<head><title>400\x20Bad\x20Request</title></head>\r\n<body>\r\n<c
SF:enter><h1>400\x20Bad\x20Request</h1></center>\r\n</body>\r\n</html>\r\n
SF:")%r(FourOhFourRequest,195,"HTTP/1\.1\x20301\x20Moved\x20Permanently\r\
SF:nServer:\x20awselb/2\.0\r\nDate:\x20Wed,\x2025\x20Sep\x202024\x2012:20:
SF:53\x20GMT\r\nContent-Type:\x20text/html\r\nContent-Length:\x20134\r\nCo
SF:nnection:\x20close\r\nLocation:\x20https://www-load-balancer-912276808\
SF:.us-east-1\.elb\.amazonaws\.com:443/nice%20ports%2C/Tri%6Eity\.txt%2eba
SF:k\r\n\r\n<html>\r\n<head><title>301\x20Moved\x20Permanently</title></he
SF:ad>\r\n<body>\r\n<center><h1>301\x20Moved\x20Permanently</h1></center>\
SF:r\n</body>\r\n</html>\r\n");
Aggressive OS guesses: Linux 2.6.32 (91%), Linux 3.2 - 4.9 (91%), Linux 2.6.32 - 3.10 (91%), Linux 3.10 - 3.13 (88%), Linux 3.1 (87%), Linux 3.2 (87%), Linux 2.6.32 - 2.6.35 (87%), Linux 2.6.32 - 3.5 (87%), Android 5.0 - 7.0 (Linux 3.4 - 3.10) (87%), Linux 2.6.32 - 3.13 (87%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 16 hops

TRACEROUTE (using port 22/tcp)
HOP RTT      ADDRESS
1   0.20 ms  208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.64 ms  gw.mcom-colocationamerica.com (208.64.231.81)
3   0.59 ms  r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   0.43 ms  ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73)
5   1.39 ms  ae-16.r24.lsanca07.us.bb.gin.ntt.net (129.250.3.78)
6   32.65 ms ae-3.r22.dllstx14.us.bb.gin.ntt.net (129.250.7.68)
7   32.74 ms ae-29.a00.dllstx14.us.bb.gin.ntt.net (129.250.3.47)
8   33.03 ms ae-1.amazon.dllstx14.us.bb.gin.ntt.net (128.241.14.222)
9   34.03 ms 15.230.130.159
10  33.12 ms 15.230.48.42
11  ... 15
16  62.74 ms ec2-44-194-165-184.compute-1.amazonaws.com (44.194.165.184)

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 31.60 seconds
Schéma de couleur
Trustpilot
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
44.194.165.184
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 3 identifiés
Exécuter la commande
nmap -A testfairy.com
Scan date
25 Sep 2024 08:21
Durée de l'analyse
31.6seconde
Copier le rapport de numérisation
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: