Scan report for "www.disneyfoodblog.com"

Membership level: Free member
Scan OS information and Traceroute (nmap -A www.disneyfoodblog.com)
Nmap scan report for www.disneyfoodblog.com (104.17.67.92)
Host is up (0.00092s latency).
Other addresses for www.disneyfoodblog.com (not scanned): 2606:4700::6811:435c 2606:4700::6812:9956 104.18.153.86
Not shown: 996 filtered tcp ports (no-response)
PORT     STATE SERVICE  VERSION
80/tcp   open  http     Cloudflare http proxy
|_http-server-header: cloudflare
|_http-title: Did not follow redirect to https://www.disneyfoodblog.com/
443/tcp  open  ssl/http Cloudflare http proxy
|_ssl-date: TLS randomness does not represent time
| tls-alpn: 
|   h2
|_  http/1.1
|_http-server-header: cloudflare
|_http-generator: WordPress 6.2.3
| tls-nextprotoneg: 
|   h2
|_  http/1.1
|_http-title: the disney food blog | food IS a theme park
| ssl-cert: Subject: commonName=sni.cloudflaressl.com/organizationName=Cloudflare, Inc./stateOrProvinceName=California/countryName=US
| Subject Alternative Name: DNS:disneyfoodblog.com, DNS:sni.cloudflaressl.com, DNS:*.disneyfoodblog.com
| Not valid before: 2023-05-17T00:00:00
|_Not valid after:  2024-05-16T23:59:59
8080/tcp open  http     Cloudflare http proxy
|_http-server-header: cloudflare
|_http-title: Did not follow redirect to https://www.disneyfoodblog.com/
8443/tcp open  ssl/http Cloudflare http proxy
|_http-server-header: cloudflare
| ssl-cert: Subject: commonName=sni.cloudflaressl.com/organizationName=Cloudflare, Inc./stateOrProvinceName=California/countryName=US
| Subject Alternative Name: DNS:disneyfoodblog.com, DNS:sni.cloudflaressl.com, DNS:*.disneyfoodblog.com
| Not valid before: 2023-05-17T00:00:00
|_Not valid after:  2024-05-16T23:59:59
|_ssl-date: TLS randomness does not represent time
| tls-alpn: 
|   h2
|_  http/1.1
| tls-nextprotoneg: 
|   h2
|_  http/1.1
|_http-title: Site doesn't have a title (text/plain; charset=UTF-8).
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Aggressive OS guesses: Linux 3.1 (91%), Linux 3.2 (91%), AXIS 210A or 211 Network Camera (Linux 2.6.17) (91%), Linux 4.15 - 5.6 (89%), Linux 5.4 (89%), Linux 5.3 - 5.4 (89%), Crestron XPanel control system (88%), Linux 2.6.32 (88%), ASUS RT-N56U WAP (Linux 3.4) (88%), Linux 3.16 (88%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 8 hops

TRACEROUTE (using port 8080/tcp)
HOP RTT     ADDRESS
1   0.19 ms 208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177)
2   0.60 ms gw.mcom-colocationamerica.com (208.64.231.81)
3   0.64 ms r1b4.n1p1400.lax.multacom.net (64.69.46.9)
4   1.12 ms be5361.ccr42.lax01.atlas.cogentco.com (38.99.219.57)
5   0.83 ms be3359.ccr41.lax05.atlas.cogentco.com (154.54.3.70)
6   1.06 ms 38.104.84.254
7   1.29 ms 162.158.88.3
8   0.78 ms 104.17.67.92

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 26.06 seconds
Color Scheme
Target
www.disneyfoodblog.com
Target IP
104.17.67.92
Scan method
Scan OS information and Traceroute
Run command
nmap -A www.disneyfoodblog.com
Scan date
12 Feb 2024 23:00
Copy scan report
Download report
Remove scan result
$
Total scans
About 2 times
Some firewalls blocks Port scans. For get true positive results add portscanner.online IP addresses (208.76.253.232-208.76.253.239 or CIDR 208.76.253.232/29 ) to the whitelist
[scan_method]
Visibility:
Scan method: