search

randomcat1234 / test-repo

0 stars 0 forks source link

Pinging test #1

Open randomcat1234 opened 1 year ago

randomcat1234 commented 1 year ago

@gping-dev ping google.com -L 5 --header "AHEADER: BC1"

randomcat1234 commented 1 year ago

@gping-dev dns google.com -L 3 --header "AHEADER: BC1"

randomcat1234 commented 1 year ago

@gping-dev ping yahoo.fr

randomcat1234 commented 1 year ago

@gping-dev dns google.com

randomcat1234 commented 1 year ago

@gping-dev ping google.fr

randomcat1234 commented 1 year ago

@gping-dev dns google.com -L 3 --header "AHEADER: BC15"

randomcat1234 commented 1 year ago

@gping-dev dns google.com from france -L 3

randomcat1234 commented 1 year ago

@gping-dev help

randomcat1234 commented 1 year ago

@gping-dev help

randomcat1234 commented 1 year ago

@gping-dev help

randomcat1234 commented 1 year ago

@gping-dev help

gping-dev commented 1 year ago

Globalping is a platform that allows anyone to run networking commands such as ping, traceroute, dig and mtr on probes distributed all around the world. The Globalping bot allows you to interact with the API in a simple and human-friendly way to debug networking issues like anycast routing and script automated tests and benchmarks.

Usage: /globalping [command]

Measurement Commands:


  http          Perform a HEAD or GET request to a host
  mtr           Run an MTR test, similar to traceroute
  ping          Run a ping test
  traceroute    Run a traceroute test```

*Additional Commands*:
```  help          Help about any command```

*Flags*:
```  -F, --from string   Comma-separated list of location values to match against. For example the partial or full name of a continent, region (e.g eastern europe), country, US state, city or network (default "world"). (default "world")
  -h, --help          help for globalping
      --latency       Output only the stats of a measurement (default false). Only applies to the dns, http and ping commands
  -L, --limit int     Limit the number of probes to use (default 1)
      --share         Prints a link at the end the results, allowing to vizualize the results online (default false)

  Use "globalping [command] --help" for more information about a command.```
randomcat1234 commented 1 year ago

@gping-dev mtr help

randomcat1234 commented 1 year ago

@gping-dev help

gping-dev commented 1 year ago

Globalping is a platform that allows anyone to run networking commands such as ping, traceroute, dig and mtr on probes distributed all around the world. The Globalping bot allows you to interact with the API in a simple and human-friendly way to debug networking issues like anycast routing and script automated tests and benchmarks.

Usage:

/globalping [command]

Measurement Commands:

  dns           Resolve a DNS record similarly to dig
  http          Perform a HEAD or GET request to a host
  mtr           Run an MTR test, similar to traceroute
  ping          Run a ping test
  traceroute    Run a traceroute test

Additional Commands:

  help          Help about any command

Flags:

  -F, --from string   Comma-separated list of location values to match against. For example the partial or full name of a continent, region (e.g eastern europe), country, US state, city or network (default "world"). (default "world")
  -h, --help          help for globalping
      --latency       Output only the stats of a measurement (default false). Only applies to the dns, http and ping commands
  -L, --limit int     Limit the number of probes to use (default 1)
      --share         Prints a link at the end the results, allowing to vizualize the results online (default false)

  Use "globalping [command] --help" for more information about a command.
randomcat1234 commented 1 year ago

@gping-dev help

gping-dev commented 1 year ago

Globalping is a platform that allows anyone to run networking commands such as ping, traceroute, dig and mtr on probes distributed all around the world. The Globalping bot allows you to interact with the API in a simple and human-friendly way to debug networking issues like anycast routing and script automated tests and benchmarks.

Usage:

@gping-dev [command]

Measurement Commands:

  dns           Resolve a DNS record similarly to dig
  http          Perform a HEAD or GET request to a host
  mtr           Run an MTR test, similar to traceroute
  ping          Run a ping test
  traceroute    Run a traceroute test

Additional Commands:

  help          Help about any command

Flags:

  -F, --from string   Comma-separated list of location values to match against. For example the partial or full name of a continent, region (e.g eastern europe), country, US state, city or network (default "world"). (default "world")
  -h, --help          help for globalping
      --latency       Output only the stats of a measurement (default false). Only applies to the dns, http and ping commands
  -L, --limit int     Limit the number of probes to use (default 1)
      --share         Prints a link at the end the results, allowing to vizualize the results online (default false)

  Use "globalping [command] --help" for more information about a command.
randomcat1234 commented 1 year ago

@gping-dev help dns

gping-dev commented 1 year ago

Performs DNS lookups and displays the answers that are returned from the name server(s) that were queried. The default nameserver depends on the probe and is defined by the user's local settings or DHCP. This command provides 2 different ways to provide the dns resolver: Using the --resolver argument. For example:

dns jsdelivr.com from Berlin --resolver 1.1.1.1

Using the dig format @resolver. For example:

dns jsdelivr.com @1.1.1.1 from Berlin

Examples: Resolve google.com from 2 probes in New York:

dns google.com from New York --limit 2

Resolve google.com from 2 probes from London or Belgium with trace enabled

dns google.com from London,Belgium --limit 2 --trace

Resolve google.com from a probe in Paris using the TCP protocol

dns google.com from Paris --protocol tcp

Resolve jsdelivr.com from a probe in Berlin using the type MX and the resolver 1.1.1.1

dns jsdelivr.com from Berlin --type MX --resolver 1.1.1.1

Resolve jsdelivr.com from a probe that is from the AWS network and is located in Montreal with latency output

dns jsdelivr.com from aws+montreal --latency

Usage:

@gping-dev dns [target] from [location] [flags]

Flags:

  -h, --help              Help for dns
      --port int          Send the query to a non-standard port on the server (default 53)
      --protocol string   Specifies the protocol to use for the DNS query (TCP or UDP) (default "udp")
      --resolver string   Resolver is the hostname or IP address of the name server to use (default empty)
      --trace             Toggle tracing of the delegation path from the root name servers (default false)
      --type string       Specifies the type of DNS query to perform (default "A")

Global Flags:

  -F, --from string       Comma-separated list of location values to match against. For example the partial or full name of a continent, region (e.g eastern europe), country, US state, city or network (default "world"). (default "world")
      --latency           Output only the stats of a measurement (default false). Only applies to the dns, http and ping commands
  -L, --limit int         Limit the number of probes to use (default 1)
      --share             Prints a link at the end the results, allowing to vizualize the results online (default false)
randomcat1234 commented 1 year ago

@gping-dev help http

gping-dev commented 1 year ago

The http command sends an HTTP request to a host and can perform HEAD or GET operations. GET is limited to 10KB responses, everything above will be cut by the API. Detailed performance stats as available for every request. The tool supports 2 formats for this command: When the full url is supplied, the tool autoparses the scheme, host, port, domain, path and query. For example:

http https://www.jsdelivr.com:443/package/npm/test?nav=stats

As an alternative that can be useful for scripting, the scheme, host, port, domain, path and query can be provided as separate command line flags. For example:

http jsdelivr.com --host www.jsdelivr.com --protocol https --port 443 --path "/package/npm/test" --query "nav=stats"

This command also provides 2 different ways to provide the dns resolver: Using the --resolver argument. For example:

http jsdelivr.com from Berlin --resolver 1.1.1.1

Using the dig format @resolver. For example:

http jsdelivr.com @1.1.1.1 from Berlin

Examples: HTTP HEAD request to jsdelivr.com from 2 probes in New York (protocol, port and path are inferred from the URL)

http https://www.jsdelivr.com:443/package/npm/test?nav=stats from New York --limit 2

HTTP GET request to google.com from 2 probes from London or Belgium

http google.com from London,Belgium --limit 2 --method get

HTTP GET request to google.com from a probe in London. Returns the full output

http google.com from London --method get --full

HTTP HEAD request to jsdelivr.com from a probe that is from the AWS network and is located in Montreal using HTTP2. 2 http headers are added to the request.

http jsdelivr.com from aws+montreal --protocol http2 --header "Accept-Encoding: br,gzip" -H "Accept-Language: *"

HTTP HEAD request to jsdelivr.com from a probe that is located in Paris, using the /robots.txt path with "test=1" query string

http jsdelivr.com from Paris --path /robots.txt --query "test=1"

HTTP HEAD request to example.com from a probe that is located in Berlin, specifying a different host example.org in the request headers

http example.com from Berlin --host example.org

HTTP GET request google.com from a probe in ASN 123 with a dns resolver 1.1.1.1

http google.com from 123 --resolver 1.1.1.1

Usage:

@gping-dev http [target] from [location] [flags]

Flags:

      --full                 Full output. Uses an HTTP GET request, and outputs the status, headers and body to the output
  -H, --header string        Specifies a HTTP header to be added to the request, in the format "Key: Value". Multiple headers can be added by adding multiple flags
  -h, --help                 Help for http
      --host string          Specifies the Host header, which is going to be added to the request (default host defined in target)
      --method string        Specifies the HTTP method to use (HEAD or GET) (default "HEAD")
      --path string          A URL pathname (default "/")
      --port int             Specifies the port to use (default 80 for HTTP, 443 for HTTPS and HTTP2)
      --protocol string      Specifies the query protocol (HTTP, HTTPS, HTTP2) (default "HTTP")
      --query string         A query-string
      --resolver string      Specifies the resolver server used for DNS lookup (default is defined by the probe's network)

Global Flags:

  -F, --from string          Comma-separated list of location values to match against. For example the partial or full name of a continent, region (e.g eastern europe), country, US state, city or network (default "world"). (default "world")
      --latency              Output only the stats of a measurement (default false). Only applies to the dns, http and ping commands
  -L, --limit int            Limit the number of probes to use (default 1)
      --share                Prints a link at the end the results, allowing to vizualize the results online (default false)
randomcat1234 commented 1 year ago

@gping-dev ping usatoday.com from "Europe" -L 5

randomcat1234 commented 1 year ago

@gping-dev ping usatoday.com from "Europe" -L 5

gping-dev commented 1 year ago

Failed to process command ping usatoday.com from "Europe" -L 5.

No suitable probes found at location "europe"

Documentation and Support: https://github.com/jsdelivr/globalping

randomcat1234 commented 1 year ago

@gping-dev ping usatoday.com from "france" -L 5 --packets 10

gping-dev commented 1 year ago

Failed to process command ping usatoday.com from "france" -L 5 --packets 10.

No suitable probes found at location "france"

Documentation and Support: https://github.com/jsdelivr/globalping

randomcat1234 commented 1 year ago

@gping-dev ping usatoday.com from "canada" -L 5 --packets 10

gping-dev commented 1 year ago

Failed to process command ping usatoday.com from "canada" -L 5 --packets 10.

No suitable probes found at location "canada"

Documentation and Support: https://github.com/jsdelivr/globalping

randomcat1234 commented 1 year ago

@gping-dev ping usatoday.com from canada -L 5 --packets 10

gping-dev commented 1 year ago

Here are the results for ping usatoday.com from canada -L 5 --packets 10

NA, CA, Montreal, ASN:62788, Karl Morin Holdings Inc.


PING usatoday.com (146.75.30.62) 56(84) bytes of data.
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=1 ttl=53 time=15.5 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=2 ttl=53 time=15.5 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=3 ttl=53 time=15.4 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=4 ttl=53 time=15.5 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=5 ttl=53 time=15.5 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=6 ttl=53 time=15.6 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=7 ttl=53 time=15.5 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=8 ttl=53 time=15.4 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=9 ttl=53 time=15.5 ms
64 bytes from 146.75.30.62 (146.75.30.62): icmp_seq=10 ttl=53 time=15.5 ms

--- usatoday.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 1807ms rtt min/avg/max/mdev = 15.421/15.490/15.559/0.040 ms

gping-dev commented 1 year ago

Here are the results for ping usatoday.com from canada -L 5 --packets 10

NA, CA, Toronto, ASN:26383, Baxet Group Inc.


PING usatoday.com (151.101.126.62) 56(84) bytes of data.
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=1 ttl=61 time=3.18 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=2 ttl=61 time=1.94 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=3 ttl=61 time=0.447 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=4 ttl=61 time=2.79 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=5 ttl=61 time=1.92 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=6 ttl=61 time=3.53 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=7 ttl=61 time=0.712 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=8 ttl=61 time=1.46 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=9 ttl=61 time=0.604 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=10 ttl=61 time=0.728 ms

--- usatoday.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 1807ms rtt min/avg/max/mdev = 0.447/1.730/3.530/1.076 ms

gping-dev commented 1 year ago

Here are the results for ping usatoday.com from canada -L 5 --packets 10

NA, CA, Toronto, ASN:31898, Oracle Cloud


PING usatoday.com (151.101.126.62) 56(84) bytes of data.
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=1 ttl=61 time=0.780 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=2 ttl=61 time=0.784 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=3 ttl=61 time=0.943 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=4 ttl=61 time=0.749 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=5 ttl=61 time=1.10 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=6 ttl=61 time=0.813 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=7 ttl=61 time=0.969 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=8 ttl=61 time=0.857 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=9 ttl=61 time=0.763 ms
64 bytes from 151.101.126.62 (151.101.126.62): icmp_seq=10 ttl=61 time=0.803 ms

--- usatoday.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 1805ms rtt min/avg/max/mdev = 0.749/0.855/1.095/0.106 ms

gping-dev commented 1 year ago

Here are the results for ping usatoday.com from canada -L 5 --packets 10

NA, CA, Montreal, ASN:16509, Amazon.com (aws-ca-central-1)


PING usatoday.com (199.232.38.62) 56(84) bytes of data.
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=1 ttl=45 time=8.46 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=2 ttl=45 time=8.46 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=3 ttl=45 time=8.48 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=4 ttl=45 time=8.48 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=5 ttl=45 time=8.49 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=6 ttl=45 time=8.46 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=7 ttl=45 time=8.57 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=8 ttl=45 time=8.68 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=9 ttl=45 time=8.68 ms
64 bytes from 199.232.38.62 (199.232.38.62): icmp_seq=10 ttl=45 time=8.48 ms

--- usatoday.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 1806ms rtt min/avg/max/mdev = 8.456/8.522/8.683/0.084 ms

gping-dev commented 1 year ago

Full results available here: https://www.jsdelivr.com/globalping?measurement=ggbdyAP063fpEOvQ

randomcat1234 commented 1 year ago

@gping-dev dns jsdelivr.com @1.1.1.1 from Germany -L 5

gping-dev commented 1 year ago

Here are the results for dns jsdelivr.com @1.1.1.1 from Germany -L 5

EU, DE, Frankfurt, ASN:137409, GSL Networks Pty

; <<>> DiG 9.16.37-Debian <<>> -t A jsdelivr.com @1.1.1.1 -p 53 -4 +timeout=3 +tries=2 +nocookie +nsid ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 447 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; NSID: 36 39 36 6d 31 31 ("696m11") ;; QUESTION SECTION: ;jsdelivr.com. IN A

;; ANSWER SECTION: jsdelivr.com. 300 IN A 104.21.23.24 jsdelivr.com. 300 IN A 172.67.208.113

;; Query time: 4 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Jul 13 08:32:32 UTC 2023 ;; MSG SIZE rcvd: 83

>**EU, DE, Frankfurt, ASN:199785, Miglovets Egor Andreevich**

; <<>> DiG 9.16.27-Debian <<>> -t A jsdelivr.com @1.1.1.1 -p 53 -4 +timeout=3 +tries=2 +nocookie +nsid ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59211 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; NSID: 36 39 36 6d 37 ("696m7") ;; QUESTION SECTION: ;jsdelivr.com. IN A

;; ANSWER SECTION: jsdelivr.com. 300 IN A 104.21.23.24 jsdelivr.com. 300 IN A 172.67.208.113

;; Query time: 8 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Jul 13 08:32:32 UTC 2023 ;; MSG SIZE rcvd: 82

>**EU, DE, Frankfurt, ASN:16276, OVH SAS**

; <<>> DiG 9.16.37-Debian <<>> -t A jsdelivr.com @1.1.1.1 -p 53 -4 +timeout=3 +tries=2 +nocookie +nsid ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60165 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; NSID: 36 33 36 6d 31 37 31 ("636m171") ;; QUESTION SECTION: ;jsdelivr.com. IN A

;; ANSWER SECTION: jsdelivr.com. 300 IN A 172.67.208.113 jsdelivr.com. 300 IN A 104.21.23.24

;; Query time: 4 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Jul 13 08:32:32 UTC 2023 ;; MSG SIZE rcvd: 84

>**EU, DE, Frankfurt, ASN:20473, Choopa, LLC**

; <<>> DiG 9.16.37-Debian <<>> -t A jsdelivr.com @1.1.1.1 -p 53 -4 +timeout=3 +tries=2 +nocookie +nsid ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26321 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; NSID: 36 30 39 6d 34 ("609m4") ;; QUESTION SECTION: ;jsdelivr.com. IN A

;; ANSWER SECTION: jsdelivr.com. 300 IN A 172.67.208.113 jsdelivr.com. 300 IN A 104.21.23.24

;; Query time: 4 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Jul 13 08:32:32 UTC 2023 ;; MSG SIZE rcvd: 82


>**Full results available here: [https://www.jsdelivr.com/globalping?measurement=0zU88FjUHFNzUIr6](https://www.jsdelivr.com/globalping?measurement=0zU88FjUHFNzUIr6)**
randomcat1234 commented 1 year ago

@gping-dev http help

gping-dev commented 1 year ago

The http command sends an HTTP request to a host and can perform HEAD or GET operations. GET is limited to 10KB responses, everything above will be cut by the API. Detailed performance stats as available for every request. The tool supports 2 formats for this command: When the full url is supplied, the tool autoparses the scheme, host, port, domain, path and query. For example:

http https://www.jsdelivr.com:443/package/npm/test?nav=stats

As an alternative that can be useful for scripting, the scheme, host, port, domain, path and query can be provided as separate command line flags. For example:

http jsdelivr.com --host www.jsdelivr.com --protocol https --port 443 --path "/package/npm/test" --query "nav=stats"

This command also provides 2 different ways to provide the dns resolver: Using the --resolver argument. For example:

http jsdelivr.com from Berlin --resolver 1.1.1.1

Using the dig format @resolver. For example:

http jsdelivr.com @1.1.1.1 from Berlin

Examples: HTTP HEAD request to jsdelivr.com from 2 probes in New York (protocol, port and path are inferred from the URL)

http https://www.jsdelivr.com:443/package/npm/test?nav=stats from New York --limit 2

HTTP GET request to google.com from 2 probes from London or Belgium

http google.com from London,Belgium --limit 2 --method get

HTTP GET request to google.com from a probe in London. Returns the full output

http google.com from London --method get --full

HTTP HEAD request to jsdelivr.com from a probe that is from the AWS network and is located in Montreal using HTTP2. 2 http headers are added to the request.

http jsdelivr.com from aws+montreal --protocol http2 --header "Accept-Encoding: br,gzip" -H "Accept-Language: *"

HTTP HEAD request to jsdelivr.com from a probe that is located in Paris, using the /robots.txt path with "test=1" query string

http jsdelivr.com from Paris --path /robots.txt --query "test=1"

HTTP HEAD request to example.com from a probe that is located in Berlin, specifying a different host example.org in the request headers

http example.com from Berlin --host example.org

HTTP GET request google.com from a probe in ASN 123 with a dns resolver 1.1.1.1

http google.com from 123 --resolver 1.1.1.1

Usage:

@gping-dev http [target] from [location] [flags]

Flags:

      --full                 Full output. Uses an HTTP GET request, and outputs the status, headers and body to the output
  -H, --header string        Specifies a HTTP header to be added to the request, in the format "Key: Value". Multiple headers can be added by adding multiple flags
  -h, --help                 Help for http
      --host string          Specifies the Host header, which is going to be added to the request (default host defined in target)
      --method string        Specifies the HTTP method to use (HEAD or GET) (default "HEAD")
      --path string          A URL pathname (default "/")
      --port int             Specifies the port to use (default 80 for HTTP, 443 for HTTPS and HTTP2)
      --protocol string      Specifies the query protocol (HTTP, HTTPS, HTTP2) (default "HTTP")
      --query string         A query-string
      --resolver string      Specifies the resolver server used for DNS lookup (default is defined by the probe's network)

Global Flags:

  -F, --from string          Comma-separated list of location values to match against. For example the partial or full name of a continent, region (e.g eastern europe), country, US state, city or network (default "world"). (default "world")
      --latency              Output only the stats of a measurement (default false). Only applies to the dns, http and ping commands
  -L, --limit int            Limit the number of probes to use (default 1)
      --share                Prints a link at the end the results, allowing to vizualize the results online (default false)
randomcat1234 commented 1 year ago

@gping-dev http google.com from London --method get --full

gping-dev commented 1 year ago

Here are the results for http google.com from London --method get --full

EU, GB, London, ASN:63949, Akamai Connected Cloud


HTTP/1.1 301
Location: http://www.google.com/
Content-Type: text/html; charset=UTF-8
Content-Security-Policy-Report-Only: object-src 'none';base-uri 'self';script-src 'nonce-LervvKrvzCOmu-ok0omvRQ' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp
Date: Thu, 13 Jul 2023 08:34:24 GMT
Expires: Sat, 12 Aug 2023 08:34:24 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 219
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
301 Moved

301 Moved

The document has moved here.
randomcat1234 commented 1 year ago

@gping-dev http jsdelivr.com from London --method get --full -L 2

gping-dev commented 1 year ago

Here are the results for http jsdelivr.com from London --method get --full -L 2

EU, GB, London, ASN:199524, G-Core Labs S.A.


HTTP/1.1 301
Date: Thu, 13 Jul 2023 08:35:16 GMT
Transfer-Encoding: chunked
Connection: close
Cache-Control: max-age=3600
Expires: Thu, 13 Jul 2023 09:35:16 GMT
Location: https://jsdelivr.com/
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=viB9iGSwcrqT9mYKUt5OB%2FEguN5d6Nv4LZ3cbT7pCWn1y8bK7pRciEeqrbvOPkrORL6RQzyQlhxnAcPKjcTN44xSq1rNYffqsmMmQzKsPhKtO6wXzVi%2F8pa%2B0Ou6xbc%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
Server: cloudflare
CF-RAY: 7e60310a4882dc39-LHR
alt-svc: h3=":443"; ma=86400
>**EU, GB, London, ASN:3214, xTom GmbH**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 08:35:16 GMT Transfer-Encoding: chunked Connection: close Cache-Control: max-age=3600 Expires: Thu, 13 Jul 2023 09:35:16 GMT Location: https://jsdelivr.com/ Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=LGHVExb4YzpByfucyfzmpOnuMrFh2Xl7p%2BGqZlSPu6E0wxFTOi%2BLPnDsbDBOdgUASW3wX%2BUyiFzmWk1OisEtC%2FBxb0ZYBdjvQXufzW4Ovt07PelgftYLpCLwDnGJvkI%3D"}],"group":"cf-nel","max_age":604800} NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} Vary: Accept-Encoding X-Content-Type-Options: nosniff Server: cloudflare CF-RAY: 7e60310a6e9676d8-LHR alt-svc: h3=":443"; ma=86400

randomcat1234 commented 1 year ago

@gping-dev http jsdelivr.com from London --method get --full -L 2

randomcat1234 commented 1 year ago

@gping-dev http jsdelivr.com from London --method get --full -L 2

gping-dev commented 1 year ago

Here are the results for http jsdelivr.com from London --method get --full -L 2

EU, GB, London, ASN:14061, DigitalOcean, LLC


HTTP/1.1 301
Date: Thu, 13 Jul 2023 09:05:51 GMT
Transfer-Encoding: chunked
Connection: close
Cache-Control: max-age=3600
Expires: Thu, 13 Jul 2023 10:05:51 GMT
Location: https://jsdelivr.com/
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=HG0TAsB0g5Ec5k3iqWclFhLoJjD2iGPK0LD6tWGi3A1%2BdCcoAq8TiHZPMeAzFuz03U8LSuBzO7G5ru6k5DzCT3k0Y6F6Bx1Mf%2FIQvjj%2F9elbXc4ZBJHXVQMuPItamkU%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
Server: cloudflare
CF-RAY: 7e605dda0a317423-LHR
alt-svc: h3=":443"; ma=86400
>**EU, GB, London, ASN:20326, TeraSwitch Networks**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 09:05:51 GMT Transfer-Encoding: chunked Connection: close Cache-Control: max-age=3600 Expires: Thu, 13 Jul 2023 10:05:51 GMT Location: https://jsdelivr.com/ Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=pGxiGxjjHAppYLSCi1vLIeZ2EN%2B%2FzpqkpkxdLKnndfDVKXvJy8PqypChLzk4tSQ6p0edVHYiaLWMjeT12RyI8kC5xL7mRadRQ3IC905uD50%2BUNv34Hny7%2FMsU9ATnjs%3D"}],"group":"cf-nel","max_age":604800} NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} Vary: Accept-Encoding X-Content-Type-Options: nosniff Server: cloudflare CF-RAY: 7e605dda2ff448c9-LHR alt-svc: h3=":443"; ma=86400

randomcat1234 commented 1 year ago

@gping-dev http elmundo.es from London --method head --full -L 3

gping-dev commented 1 year ago

Here are the results for http elmundo.es from London --method head --full -L 3

EU, GB, London, ASN:62240, Clouvider Limited


HTTP/1.1 301
Date: Thu, 13 Jul 2023 09:06:36 GMT
Server: Varnish
X-Varnish: 891168677
Location: https://elmundo.es/
Content-Length: 0
Connection: close
>**EU, GB, London, ASN:39326, HighSpeed Office Limited**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 09:06:36 GMT Server: Varnish X-Varnish: 890881870 Location: https://elmundo.es/ Content-Length: 0 Connection: close

>**EU, GB, London, ASN:63473, HostHatch**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 09:06:36 GMT Server: Varnish X-Varnish: 908774660 Location: https://elmundo.es/ Content-Length: 0 Connection: close

randomcat1234 commented 1 year ago

@gping-dev http elmundo.es from London,Paris --method head --full -L 6

randomcat1234 commented 1 year ago

@gping-dev http elmundo.es from London,Paris --method head --full -L 7

gping-dev commented 1 year ago

Here are the results for http elmundo.es from London,Paris --method head --full -L 7

EU, GB, London, ASN:9009, M247 Europe SRL


HTTP/1.1 301
Date: Thu, 13 Jul 2023 09:11:26 GMT
Server: Varnish
X-Varnish: 937826017
Location: https://elmundo.es/
Content-Length: 0
Connection: close
>**EU, GB, London, ASN:61046, HZ Hosting Ltd**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 09:11:26 GMT Server: Varnish X-Varnish: 941853468 Location: https://elmundo.es/ Content-Length: 0 Connection: close

>**EU, GB, London, ASN:42831, Rochut Group**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 09:11:26 GMT Server: Varnish X-Varnish: 941230905 Location: https://elmundo.es/ Content-Length: 0 Connection: close

>**EU, GB, London, ASN:20473, The Constant Company, LLC**

HTTP/1.1 301 Date: Thu, 13 Jul 2023 09:11:26 GMT Server: Varnish X-Varnish: 906806236 Location: https://elmundo.es/ Content-Length: 0 Connection: close


>**Full results available here: [https://www.jsdelivr.com/globalping?measurement=7GA4GSHkmdUm893S](https://www.jsdelivr.com/globalping?measurement=7GA4GSHkmdUm893S)**