Analyser le rapport pour "adsapi.snapchat.com"

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

Ports

2

Durée

1min 20.07seconde (80.07seconde)

Date

2024-09-28

IP

34.102.183.120

Rapporter
Analyser les informations du système d'exploitation et Traceroute (nmap -A adsapi.snapchat.com)
Nmap scan report for adsapi.snapchat.com (34.102.183.120)
Host is up (0.00043s latency).
rDNS record for 34.102.183.120: 120.183.102.34.bc.googleusercontent.com
Not shown: 998 filtered tcp ports (no-response)
PORT    STATE SERVICE    VERSION
80/tcp  open  tcpwrapped
443/tcp open  ssl/https  API Gateway
|_http-title: Site doesn't have a title.
| tls-nextprotoneg: 
|   grpc-exp
|   h2
|_  http/1.1
| tls-alpn: 
|   grpc-exp
|   h2
|_  http/1.1
|_ssl-date: TLS randomness does not represent time
| ssl-cert: Subject: commonName=*.snap.com/organizationName=Snap Inc./stateOrProvinceName=California/countryName=US
| Subject Alternative Name: DNS:*.snap.com, DNS:*.snapchat.com, DNS:*.ats.snapchat.com, DNS:*.snapads.com, DNS:*.snap-dev.net, DNS:*.snappcm.com, DNS:*.snappcm-dev.com, DNS:*.snapar.com, DNS:*.snapkit.com, DNS:*.arcadiacreativestudio.com, DNS:*.bitmoji.com, DNS:*.lensstudio.com, DNS:*.pixy.com, DNS:*.spectacles.com, DNS:snap.com, DNS:snapchat.com, DNS:ats.snapchat.com, DNS:snapads.com, DNS:snap-dev.net, DNS:snappcm.com, DNS:snappcm-dev.com, DNS:snapar.com, DNS:snapkit.com, DNS:arcadiacreativestudio.com, DNS:bitmoji.com, DNS:lensstudio.com, DNS:pixy.com, DNS:spectacles.com
| Not valid before: 2024-07-23T00:00:00
|_Not valid after:  2025-07-22T23:59:59
|_http-server-header: API Gateway
| fingerprint-strings: 
|   DNSStatusRequestTCP, DNSVersionBindReqTCP: 
|     HTTP/1.0 400 Bad Request
|     Content-Length: 54
|     Content-Type: text/html; charset=UTF-8
|     Date: Sat, 28 Sep 2024 11:17:09 GMT
|     <html><title>Error 400 (Bad Request)!!1</title></html>
|   FourOhFourRequest, GetRequest, HTTPOptions: 
|     HTTP/1.0 404 Not Found
|     date: Sat, 28 Sep 2024 11:16:58 GMT
|     server: API Gateway
|     Content-Length: 0
|     Via: 1.1 google
|     Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
|   RTSPRequest: 
|     HTTP/1.0 400 Bad Request
|     Content-Type: text/html; charset=UTF-8
|     Referrer-Policy: no-referrer
|     Content-Length: 273
|     Date: Sat, 28 Sep 2024 11:17:03 GMT
|     <html><head>
|     <meta http-equiv="content-type" content="text/html;charset=utf-8">
|     <title>400 Bad Request</title>
|     </head>
|     <body text=#000000 bgcolor=#ffffff>
|     <h1>Error: Bad Request</h1>
|     <h2>Your client has issued a malformed or illegal request.</h2>
|     <h2></h2>
|     </body></html>
|   tor-versions: 
|     HTTP/1.0 400 Bad Request
|     Content-Length: 54
|     Content-Type: text/html; charset=UTF-8
|     Date: Sat, 28 Sep 2024 11:16:58 GMT
|_    <html><title>Error 400 (Bad Request)!!1</title></html>
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/28%Time=66F7E5A9%P=x86_64-redhat-linux
SF:-gnu%r(GetRequest,B1,"HTTP/1\.0\x20404\x20Not\x20Found\r\ndate:\x20Sat,
SF:\x2028\x20Sep\x202024\x2011:16:58\x20GMT\r\nserver:\x20API\x20Gateway\r
SF:\nContent-Length:\x200\r\nVia:\x201\.1\x20google\r\nAlt-Svc:\x20h3=\":4
SF:43\";\x20ma=2592000,h3-29=\":443\";\x20ma=2592000\r\n\r\n")%r(HTTPOptio
SF:ns,B1,"HTTP/1\.0\x20404\x20Not\x20Found\r\ndate:\x20Sat,\x2028\x20Sep\x
SF:202024\x2011:16:58\x20GMT\r\nserver:\x20API\x20Gateway\r\nContent-Lengt
SF:h:\x200\r\nVia:\x201\.1\x20google\r\nAlt-Svc:\x20h3=\":443\";\x20ma=259
SF:2000,h3-29=\":443\";\x20ma=2592000\r\n\r\n")%r(FourOhFourRequest,B1,"HT
SF:TP/1\.0\x20404\x20Not\x20Found\r\ndate:\x20Sat,\x2028\x20Sep\x202024\x2
SF:011:16:58\x20GMT\r\nserver:\x20API\x20Gateway\r\nContent-Length:\x200\r
SF:\nVia:\x201\.1\x20google\r\nAlt-Svc:\x20h3=\":443\";\x20ma=2592000,h3-2
SF:9=\":443\";\x20ma=2592000\r\n\r\n")%r(tor-versions,B3,"HTTP/1\.0\x20400
SF:\x20Bad\x20Request\r\nContent-Length:\x2054\r\nContent-Type:\x20text/ht
SF:ml;\x20charset=UTF-8\r\nDate:\x20Sat,\x2028\x20Sep\x202024\x2011:16:58\
SF:x20GMT\r\n\r\n<html><title>Error\x20400\x20\(Bad\x20Request\)!!1</title
SF:></html>")%r(RTSPRequest,1AD,"HTTP/1\.0\x20400\x20Bad\x20Request\r\nCon
SF:tent-Type:\x20text/html;\x20charset=UTF-8\r\nReferrer-Policy:\x20no-ref
SF:errer\r\nContent-Length:\x20273\r\nDate:\x20Sat,\x2028\x20Sep\x202024\x
SF:2011:17:03\x20GMT\r\n\r\n\n<html><head>\n<meta\x20http-equiv=\"content-
SF:type\"\x20content=\"text/html;charset=utf-8\">\n<title>400\x20Bad\x20Re
SF:quest</title>\n</head>\n<body\x20text=#000000\x20bgcolor=#ffffff>\n<h1>
SF:Error:\x20Bad\x20Request</h1>\n<h2>Your\x20client\x20has\x20issued\x20a
SF:\x20malformed\x20or\x20illegal\x20request\.</h2>\n<h2></h2>\n</body></h
SF:tml>\n")%r(DNSVersionBindReqTCP,B3,"HTTP/1\.0\x20400\x20Bad\x20Request\
SF:r\nContent-Length:\x2054\r\nContent-Type:\x20text/html;\x20charset=UTF-
SF:8\r\nDate:\x20Sat,\x2028\x20Sep\x202024\x2011:17:09\x20GMT\r\n\r\n<html
SF:><title>Error\x20400\x20\(Bad\x20Request\)!!1</title></html>")%r(DNSSta
SF:tusRequestTCP,B3,"HTTP/1\.0\x20400\x20Bad\x20Request\r\nContent-Length:
SF:\x2054\r\nContent-Type:\x20text/html;\x20charset=UTF-8\r\nDate:\x20Sat,
SF:\x2028\x20Sep\x202024\x2011:17:09\x20GMT\r\n\r\n<html><title>Error\x204
SF:00\x20\(Bad\x20Request\)!!1</title></html>");
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: 7 hops

TRACEROUTE (using port 443/tcp)
HOP RTT     ADDRESS
1   0.21 ms 208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.67 ms gw.mcom-colocationamerica.com (208.64.231.81)
3   0.72 ms r2b4.n1.p1401.lax.multacom.net (64.69.46.11)
4   1.59 ms google.as15169.any2ix.coresite.com (206.72.210.41)
5   1.72 ms 142.251.232.55
6   1.02 ms 142.250.226.45
7   0.47 ms 120.183.102.34.bc.googleusercontent.com (34.102.183.120)

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 80.07 seconds
Schéma de couleur
Trustpilot
Online Port scanner - portscanner, nmap, unicornscan | Product Hunt
Rapport détaillé
Cible
IP cible
34.102.183.120
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 2 identifiés
Exécuter la commande
nmap -A adsapi.snapchat.com
Scan date
28 Sep 2024 07:18
Durée de l'analyse
1min 20.07seconde (80.07seconde)
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: