Ports
Duration
Date
IP
Nmap scan report for telegraph.co.uk.edgekey.net (23.222.205.88) Host is up (0.00079s latency). rDNS record for 23.222.205.88: a23-222-205-88.deploy.static.akamaitechnologies.com Not shown: 998 filtered tcp ports (no-response) PORT STATE SERVICE VERSION 80/tcp open http AkamaiGHost (Akamai's HTTP Acceleration/Mirror service) |_http-title: Invalid URL 443/tcp open ssl/http AkamaiGHost (Akamai's HTTP Acceleration/Mirror service) |_http-title: Invalid URL |_ssl-date: TLS randomness does not represent time | ssl-cert: Subject: commonName=www.telegraph.co.uk/organizationName=Telegraph Media Group Holdings Limited/countryName=GB | Subject Alternative Name: DNS:www.telegraph.co.uk, DNS:api-preprod.telegraph.co.uk, DNS:api.telegraph.co.uk, DNS:app.telegraph.co.uk, DNS:betting.telegraph.co.uk, DNS:ci-app.telegraph.co.uk, DNS:ci.telegraph.co.uk, DNS:ci1-app.telegraph.co.uk, DNS:ci1.telegraph.co.uk, DNS:ci10.telegraph.co.uk, DNS:extra.telegraph.co.uk, DNS:i.telegraph.co.uk, DNS:preview-image-dev-full.telegraph.co.uk, DNS:preview-image-dev3.telegraph.co.uk, DNS:preview-image-rde19.telegraph.co.uk, DNS:preview-image-staging.telegraph.co.uk, DNS:preview-image.telegraph.co.uk, DNS:prod-hzn-app.telegraph.co.uk, DNS:prod-hzn.telegraph.co.uk, DNS:puzzles-qa.telegraph.co.uk, DNS:puzzles-uat.telegraph.co.uk, DNS:qa1-app.telegraph.co.uk, DNS:qa1.telegraph.co.uk, DNS:qa10-app.telegraph.co.uk, DNS:qa10.telegraph.co.uk, DNS:qa11-app.telegraph.co.uk, DNS:qa11.telegraph.co.uk, DNS:qa12-app.telegraph.co.uk, DNS:qa12.telegraph.co.uk, DNS:qa13-app.telegraph.co.uk, DNS:qa13.telegraph.co.uk, DNS:qa14-app.telegraph.co.uk, DNS:qa14.telegraph.co.uk, DNS:qa15-app.telegraph.co.uk, DNS:qa15.telegraph.co.uk, DNS:qa16-app.telegraph.co.uk, DNS:qa16.telegraph.co.uk, DNS:qa17-app.telegraph.co.uk, DNS:qa17.telegraph.co.uk, DNS:qa18-app.telegraph.co.uk, DNS:qa18.telegraph.co.uk, DNS:qa19-app.telegraph.co.uk, DNS:qa19.telegraph.co.uk, DNS:qa2-app.telegraph.co.uk, DNS:qa2.telegraph.co.uk, DNS:qa20-app.telegraph.co.uk, DNS:qa20.telegraph.co.uk, DNS:qa21-app.telegraph.co.uk, DNS:qa21.telegraph.co.uk, DNS:qa22-app.telegraph.co.uk, DNS:qa22.telegraph.co.uk, DNS:qa23-app.telegraph.co.uk, DNS:qa23.telegraph.co.uk, DNS:qa24-app.telegraph.co.uk, DNS:qa24.telegraph.co.uk, DNS:qa3-app.telegraph.co.uk, DNS:qa3.telegraph.co.uk, DNS:qa4-app.telegraph.co.uk, DNS:qa4.telegraph.co.uk, DNS:qa5-app.telegraph.co.uk, DNS:qa5.telegraph.co.uk, DNS:qa6-app.telegraph.co.uk, DNS:qa6.telegraph.co.uk, DNS:qa7-app.telegraph.co.uk, DNS:qa7.telegraph.co.uk, DNS:qa8-app.telegraph.co.uk, DNS:qa8.telegraph.co.uk, DNS:qa9-app.telegraph.co.uk, DNS:qa9.telegraph.co.uk, DNS:s.telegraph.co.uk, DNS:shop.telegraph.co.uk, DNS:staging-ams.telegraph.co.uk, DNS:staging-ams64-app.telegraph.co.uk, DNS:staging-ams64.telegraph.co.uk, DNS:staging-app.telegraph.co.uk, DNS:staging-extra.telegraph.co.uk, DNS:staging-hzn-app.telegraph.co.uk, DNS:staging-hzn.telegraph.co.uk, DNS:staging.telegraph.co.uk, DNS:telegraph.co.uk, DNS:testlink.telegraph.co.uk | Not valid before: 2024-09-19T00:00:00 |_Not valid after: 2025-01-23T23:59:59 | tls-nextprotoneg: | http/1.1 |_ http/1.0 | tls-alpn: | http/1.1 |_ http/1.0 Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port Aggressive OS guesses: Linux 5.4 (94%), Linux 4.15 - 5.6 (92%), Linux 4.10 (92%), Linux 5.0 - 5.3 (91%), Linux 5.0 - 5.4 (90%), Crestron XPanel control system (90%), Linux 2.6.32 (88%), Linux 3.10 - 4.11 (88%), Linux 3.2 - 3.16 (88%), Linux 3.2 - 4.9 (88%) No exact OS matches for host (test conditions non-ideal). Network Distance: 8 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.59 ms gw.mcom-colocationamerica.com (208.64.231.81) 3 0.69 ms r2b4.n1.p1401.lax.multacom.net (64.69.46.11) 4 0.74 ms 206.72.211.131.any2ix.coresite.com (206.72.211.131) 5 ... 6 0.82 ms 192.168.230.41 7 0.87 ms 192.168.192.145 8 0.79 ms a23-222-205-88.deploy.static.akamaitechnologies.com (23.222.205.88) 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 25.83 seconds