Ports
Duration
Date
IP
Nmap scan report for mycarenotifications.dignityhealth.org (104.16.65.119) Host is up (0.00099s latency). Other addresses for mycarenotifications.dignityhealth.org (not scanned): 2606:4700::6810:4177 2606:4700::6810:4277 104.16.66.119 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://mycarenotifications.dignityhealth.org/ 443/tcp open ssl/http Cloudflare http proxy |_http-server-header: cloudflare | ssl-cert: Subject: commonName=dignityhealth.org/organizationName=CommonSpirit Health/stateOrProvinceName=Illinois/countryName=US | Subject Alternative Name: DNS:dignityhealth.org, DNS:api.dignityhealth.org, DNS:apim.dignityhealth.org, DNS:appointments.api.dignityhealth.org, DNS:authentication.api.dignityhealth.org, DNS:biometrics-mgmt.api.dignityhealth.org, DNS:ciam.api.dignityhealth.org, DNS:cms.dignityhealth.org, DNS:devportal.api.dignityhealth.org, DNS:devportal.apim.dignityhealth.org, DNS:edw.api.dignityhealth.org, DNS:facilities.api.dignityhealth.org, DNS:identity-verfication.dignityhealth.org, DNS:identity-verification-staging.dignityhealth.org, DNS:identityspa-staging.dignityhealth.org, DNS:identityspa.dignityhealth.org, DNS:lcr.api.dignityhealth.org, DNS:medicalrecords-staging.dignityhealth.org, DNS:medicalrecords.dignityhealth.org, DNS:membervalidation.api.dignityhealth.org, DNS:myappointments-staging.dignityhealth.org, DNS:myappointments.dignityhealth.org, DNS:mycarenotifications-staging.dignityhealth.org, DNS:mycarenotifications.dignityhealth.org, DNS:myhelp.dignityhealth.org, DNS:myprofile-staging.dignityhealth.org, DNS:myprofile.dignityhealth.org, DNS:ngx-scheduling-staging.dignityhealth.org, DNS:ngx-scheduling.dignityhealth.org, DNS:notifications.api.dignityhealth.org, DNS:patientportals.api.dignityhealth.org, DNS:pdm.dignityhealth.org, DNS:profiles.api.dignityhealth.org, DNS:provider-access.api.dignityhealth.org, DNS:providersearch.api.dignityhealth.org, DNS:scheduling.api.dignityhealth.org, DNS:telehealth.api.dignityhealth.org, DNS:user-profile-preferences.api.dignityhealth.org, DNS:versioningservices.api.dignityhealth.org, DNS:vmr-staging.dignityhealth.org, DNS:vmr.dignityhealth.org, DNS:vrtreg-staging.dignityhealth.org, DNS:vrtreg.dignityhealth.org, DNS:www.dignityhealth.org | Not valid before: 2023-12-01T00:00:00 |_Not valid after: 2024-11-30T23:59:59 |_ssl-date: TLS randomness does not represent time | tls-alpn: | h2 |_ http/1.1 | http-methods: |_ Potentially risky methods: TRACE |_http-title: Site doesn't have a title (text/html). | tls-nextprotoneg: | h2 |_ http/1.1 8080/tcp open http Cloudflare http proxy |_http-server-header: cloudflare |_http-title: Did not follow redirect to https://mycarenotifications.dignityhealth.org/ 8443/tcp open ssl/http Cloudflare http proxy |_ssl-date: TLS randomness does not represent time |_http-server-header: cloudflare | ssl-cert: Subject: commonName=dignityhealth.org/organizationName=CommonSpirit Health/stateOrProvinceName=Illinois/countryName=US | Subject Alternative Name: DNS:dignityhealth.org, DNS:api.dignityhealth.org, DNS:apim.dignityhealth.org, DNS:appointments.api.dignityhealth.org, DNS:authentication.api.dignityhealth.org, DNS:biometrics-mgmt.api.dignityhealth.org, DNS:ciam.api.dignityhealth.org, DNS:cms.dignityhealth.org, DNS:devportal.api.dignityhealth.org, DNS:devportal.apim.dignityhealth.org, DNS:edw.api.dignityhealth.org, DNS:facilities.api.dignityhealth.org, DNS:identity-verfication.dignityhealth.org, DNS:identity-verification-staging.dignityhealth.org, DNS:identityspa-staging.dignityhealth.org, DNS:identityspa.dignityhealth.org, DNS:lcr.api.dignityhealth.org, DNS:medicalrecords-staging.dignityhealth.org, DNS:medicalrecords.dignityhealth.org, DNS:membervalidation.api.dignityhealth.org, DNS:myappointments-staging.dignityhealth.org, DNS:myappointments.dignityhealth.org, DNS:mycarenotifications-staging.dignityhealth.org, DNS:mycarenotifications.dignityhealth.org, DNS:myhelp.dignityhealth.org, DNS:myprofile-staging.dignityhealth.org, DNS:myprofile.dignityhealth.org, DNS:ngx-scheduling-staging.dignityhealth.org, DNS:ngx-scheduling.dignityhealth.org, DNS:notifications.api.dignityhealth.org, DNS:patientportals.api.dignityhealth.org, DNS:pdm.dignityhealth.org, DNS:profiles.api.dignityhealth.org, DNS:provider-access.api.dignityhealth.org, DNS:providersearch.api.dignityhealth.org, DNS:scheduling.api.dignityhealth.org, DNS:telehealth.api.dignityhealth.org, DNS:user-profile-preferences.api.dignityhealth.org, DNS:versioningservices.api.dignityhealth.org, DNS:vmr-staging.dignityhealth.org, DNS:vmr.dignityhealth.org, DNS:vrtreg-staging.dignityhealth.org, DNS:vrtreg.dignityhealth.org, DNS:www.dignityhealth.org | Not valid before: 2023-12-01T00:00:00 |_Not valid after: 2024-11-30T23:59:59 |_http-title: 400 The plain HTTP request was sent to HTTPS port | tls-nextprotoneg: | h2 |_ http/1.1 | tls-alpn: | h2 |_ http/1.1 Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port Aggressive OS guesses: FreeBSD 11.0-STABLE (92%), FreeBSD 11.1-STABLE (92%), FreeBSD 11.0-RELEASE - 12.0-CURRENT (89%), FreeBSD 11.1-RELEASE or 11.2-STABLE (89%), FreeBSD 11.2-RELEASE - 11.3 RELEASE or 11.2-STABLE (89%), FreeBSD 12.0-RELEASE - 13.0-CURRENT (89%), FreeBSD 11.1-RELEASE (88%), FreeBSD 11.2-RELEASE - 11.3-RELEASE (88%), FreeBSD 12.0-RELEASE - 12.1-RELEASE or 12.0-STABLE (88%), FreeBSD 11.0-RELEASE (88%) No exact OS matches for host (test conditions non-ideal). Network Distance: 7 hops TRACEROUTE (using port 8080/tcp) HOP RTT ADDRESS 1 0.23 ms 208.76.251.177.rdns.ColocationAmerica.com (208.76.251.177) 2 0.53 ms gw.mcom-colocationamerica.com (208.64.231.81) 3 0.61 ms r1b4.n1p1400.lax.multacom.net (64.69.46.9) 4 4.32 ms ce-1-4-2.a04.lsanca07.us.bb.gin.ntt.net (128.241.15.73) 5 1.31 ms ae-0.cloudflare.lsanca07.us.bb.gin.ntt.net (128.241.9.245) 6 1.77 ms 141.101.72.31 7 0.91 ms 104.16.65.119 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 94.75 seconds