Yale.edu - Connect.yale.edu
Sign in to Outlook
Domain Summary
What is the traffic rank for Connect.yale.edu?
• Connect.yale.edu ranks #3,728 globally on HypeStat.
What percent of global Internet users visit Connect.yale.edu?
• 0.0198% of global Internet users visit Connect.yale.edu
How many people visit Connect.yale.edu each day?
• Connect.yale.edu receives approximately 1M visitors and 2,186,521 page impressions per day.
Which countries does Connect.yale.edu receive most of its visitors from?
• Connect.yale.edu is mostly visited by people located in United States,India,Canada.
How much Connect.yale.edu can earn?
• Connect.yale.edu should earn about $7,991.27/day from advertising revenue.
What is Connect.yale.edu estimated value?
• Estimated value of Connect.yale.edu is $7,523,928.35.
What IP addresses does Connect.yale.edu resolve to?
• Connect.yale.edu resolves to the IP addresses 130.132.35.62.
Where are Connect.yale.edu servers located in?
• Connect.yale.edu has servers located in New Haven, Connecticut, 06511, United States.
connect.yale.edu Profile
Title:Sign in to Outlook
About:
A leading private, independent research institution. Founded in 1701 in New Haven, Connecticut.
Edit Site Info
What technologies does connect.yale.edu use?
These are the technologies used at connect.yale.edu. connect.yale.edu has a total of 6 technologies installed in 4 different categories.
connect.yale.edu Traffic Analysis
Connect.yale.edu is ranked #3,728 in the world. This website is viewed by an estimated 1M visitors daily, generating a total of 2.2M pageviews. This equates to about 29.6M monthly visitors.Daily Visitors1M
Monthly Visits29.6M
Pages per Visit2.24
Visit duration03:16
Bounce Rate59.80%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 976,125
- Monthly Visits:
- 29,576,588
- Pages per Visit:
- 2.24
- Daily Pageviews:
- 2,186,521
- Avg. visit duration:
- 03:16
- Bounce rate:
- 59.80%
- Global Reach:
- 0.0198%
- HypeRank:
- 3,728
- SEMrush Rank:
- 1,131
Traffic sources
- Direct:
- 27.89%
- Referral:
- 3.81%
- Search:
- 57.76%
- Social:
- 2.23%
- Paid:
- 0.04%
Visitors by country
- Country
- Users%
- United States 53.1%
- India 7.8%
- Canada 3.4%
- China 2.9%
- Nigeria 2.9%
Where do visitors go on connect.yale.edu?
- Reach%Pageviews%PerUser
- law.yale.edu
- 11.13%8.04%1.6
- yale.edu
- 10.27%6.23%1.3
- its.yale.edu
- 7.72%4.54%1.3
- medicine.yale.edu
- 6.02%4.72%1.7
- som.yale.edu
- 5.83%7.80%3.0
Backlinks Report ▼
Connect.yale.edu has a total of 1,863,384 backlinks from 58,829 referring domains.- Total Backlinks:
- 1,863,384
- Follow Links:
- 1,637,943
- Nofollow Links:
- 225,441
- Referring Domains:
- 58,829
- Referring IPs:
- 48,559
- Authority Domain Score:
- 52
Last update was 2054 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with yale.edu in any way. Only publicly available statistics data are displayed.
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- connect.yale.edu
- Rank:
(Rank based on keywords, cost and organic traffic) - 1,131
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 1,094,339
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 1,579,150
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $3,145,313.00
Revenue report ▼
Google.com would generate approximately $8K per day if the source of income were advertisements, which equates to an estimated monthly revenue of $239.7K and annual gross revenue of approximately $2.9M. Based on these figures, the site's net worth is estimated at around $7.5M.How much would connect.yale.edu make?
- Daily Revenue:
- $7,991.27
- Monthly Revenue:
- $239,738.10
- Yearly Revenue:
- $2,916,813.55
Daily earning by country
- CountryPageviewsEarning
- India 153,056$58.16
- Egypt 0$0.00
- Malaysia 0$0.00
- Pakistan 0$0.00
- Philippines 0$0.00
Loss of money due to Adblock?
- Daily Revenue Loss:
- $1,187.46
- Monthly Revenue Loss:
- $35,623.94
- Yearly Revenue Loss:
- $433,424.57
- Daily Pageviews Blocked:
- 297,586
- Monthly Pageviews Blocked:
- 8,927,565
- Yearly Pageviews Blocked:
- 108,618,710
Daily revenue loss by country
- CountryBlockedLost Money
- India 42,856$16.29
- Egypt 0$0.00
- Malaysia 0$0.00
- Pakistan 0$0.00
- Philippines 0$0.00
How much is connect.yale.edu worth?
- Website Value:
- $7.5M
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- yale.edu
- Last Change Time:
(The last time that the site changed status.) - 2019-03-11 11:49:56
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Passing
Desktop summary
- Root domain:
- yale.edu
- Last Change Time:
(The last time that the site changed status.) - 2019-03-11 11:49:56
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Passing
Abusive Experience Report ▼
Summary of the abusive experience rating of a website.- Root domain:
- yale.edu
- Last Change Time:
(The last time that the site changed status.) - 2019-03-11 11:49:56
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Passing
Where is connect.yale.edu hosted? ▼
Connect.yale.edu may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 130.132.35.62
- ASN:
- AS29
- ISP:
- Yale University
- Server Location:
- New Haven
Connecticut, CT
06511
United States, US
Other sites hosted on 130.132.35.62
There are no other sites hosted on this IPHow fast does connect.yale.edu load? ▼
The average loading time of connect.yale.edu is 1262 ms. The Desktop speed index is 83 and mobile speed index is 55.- Average Load Time:
- 1262 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Origin Data
All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Lab Data
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First CPU Idle 1.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
Time to Interactive 1.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Origin Data
All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Lab Data
Estimated Input Latency 80 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 10058 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Speed Index 5.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First CPU Idle 5.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First Contentful Paint 5.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Meaningful Paint 5.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Max Potential First Input Delay 300 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
Time to Interactive 5.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Does connect.yale.edu use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on connect.yale.edu are reduced by %.
connect.yale.edu does not use compression.
Original size: n/a
Compressed size: n/a
File reduced by: (%)
Compressed size: n/a
File reduced by: (%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious
MyWot.com Reputation Ratings
MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. connect.yale.edu has 63 Safety Reputations.- Status:
- SAFE
- Safety Reputations:
- 63
- Safety Confidence:
- 4
- Child Safety Reputations:
- 93
- Child Safety Confidence:
- 14
SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. connect.yale.edu supports HTTPS. connect.yale.edu supports HTTPS
Verifying SSL Support. Please wait...
Common Name: connect.yale.edu
Organization: Yale University
Location: New Haven, Connecticut, US
Issuer: GlobalSign Organization Validation CA - SHA256 - G2
Valid from: Sep 14 05:01:09 2018 GMT
Valid until: Sep 14 05:01:09 2020 GMT
Authority: Is not a CA
Keysize:
Organization: Yale University
Location: New Haven, Connecticut, US
Issuer: GlobalSign Organization Validation CA - SHA256 - G2
Valid from: Sep 14 05:01:09 2018 GMT
Valid until: Sep 14 05:01:09 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: GlobalSign Organization Validation CA - SHA256 - G2
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Aug 2 10:00:00 2011 GMT
Valid until: Aug 2 10:00:00 2022 GMT
Authority: Is a CA
Keysize: 2048 Bits
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Aug 2 10:00:00 2011 GMT
Valid until: Aug 2 10:00:00 2022 GMT
Authority: Is a CA
Keysize: 2048 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. connect.yale.edu does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Site Categories ▼
Website categories are used to classify websites based on their content or purpose. These categories provide a way to organize and filter websites, allowing users to find relevant information or ensure compliance with specific regulations or policies.- Connecticut/Yale University
- Europe/United Kingdom
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.Location: https://connect.yale.edu/
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
HTTP/1.0 301 Moved Permanently
Location: https://outlook.office365.com/yale.edu
Server: BigIP
Connection: close
Content-Length: 0
HTTP/1.1 302 Found
Content-Type: text/html; charset=utf-8
Location: /owa/yale.edu
Server: Microsoft-IIS/10.0
request-id: a147b40f-ee40-4d9d-9a53-e9e8b3b7d59c
X-Powered-By: ASP.NET
X-FEServer: SN6PR16CA0043
Date: Tue, 17 Dec 2019 23:31:16 GMT
Connection: close
Content-Length: 130
HTTP/1.1 302 Found
Content-Length: 714
Content-Type: text/html; charset=utf-8
Location: https://login.microsoftonline.com/common/oauth2/authorize?client_id=00000002-0000-0ff1-ce00-000000000000&redirect_uri=https%3a%2f%2foutlook.office365.com%2fowa%2f&resource=00000002-0000-0ff1-ce00-000000000000&response_mode=form_post&response_type=code+id_token&scope=openid&msafed=0&client-request-id=f9b607f5-71d0-42b7-8b03-80e1a0257264&protectedtoken=true&domain_hint=yale.edu&nonce=637122222770449570.ef858b7f-16e1-48ce-a0d7-5d49a00c5d88&state=FYtBDoAgDMCGnn0KMpSx8RyEcTLxZIy_dzZpb3UAMJuT6dACnHeO2w8zplSIcdUhJAcPH7NGn6Spr9jZU0-lIjbqIs7eJVxPDW89ddV-fw
Server: Microsoft-IIS/10.0
request-id: f9b607f5-71d0-42b7-8b03-80e1a0257264
X-CalculatedFETarget: CY4PR01CU001.internal.outlook.com
X-BackEndHttpStatus: 302
P3P: CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"
Set-Cookie: ClientId=78D0EDE2CBBC4F23AC575B4BD24BAC9C; expires=Thu, 17-Dec-2020 23:31:17 GMT; path=/; secure
Set-Cookie: ClientId=78D0EDE2CBBC4F23AC575B4BD24BAC9C; expires=Thu, 17-Dec-2020 23:31:17 GMT; path=/; secure
Set-Cookie: OIDC=1; expires=Wed, 17-Jun-2020 23:31:17 GMT; path=/; secure; HttpOnly
Set-Cookie: domainName=yale.edu; path=/; secure; HttpOnly
Set-Cookie: RoutingKeyCookie=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.token.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.token.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.id_token.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.code.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_nonce.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_correlation_id=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.tokenPostPath=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.id_token.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.code.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_nonce.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_correlation_id=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.tokenPostPath=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.nonce.v3.Kf-b9htY5-JQ1_cbMy2ZmusXL_sMqe4G1udB0omwNrQ=637122222770449570.ef858b7f-16e1-48ce-a0d7-5d49a00c5d88; expires=Wed, 18-Dec-2019 00:31:17 GMT; path=/; secure; HttpOnly
Set-Cookie: HostSwitchPrg=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OptInPrg=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: SuiteServiceProxyKey=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: ClientId=78D0EDE2CBBC4F23AC575B4BD24BAC9C; expires=Thu, 17-Dec-2020 23:31:17 GMT; path=/; secure
Set-Cookie: OIDC=1; expires=Wed, 17-Jun-2020 23:31:17 GMT; path=/; secure; HttpOnly
Set-Cookie: domainName=yale.edu; path=/; secure; HttpOnly
Set-Cookie: RoutingKeyCookie=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.token.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.token.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.id_token.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.code.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_nonce.v1=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_correlation_id=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.tokenPostPath=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.id_token.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.code.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_nonce.v1=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.idp_correlation_id=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.tokenPostPath=; domain=outlook.office365.com; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OpenIdConnect.nonce.v3.Kf-b9htY5-JQ1_cbMy2ZmusXL_sMqe4G1udB0omwNrQ=637122222770449570.ef858b7f-16e1-48ce-a0d7-5d49a00c5d88; expires=Wed, 18-Dec-2019 00:31:17 GMT; path=/; secure; HttpOnly
Set-Cookie: HostSwitchPrg=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: OptInPrg=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: SuiteServiceProxyKey=; expires=Sun, 17-Dec-1989 23:31:17 GMT; path=/; secure
Set-Cookie: X-OWA-RedirectHistory=ArLym14Bp5O9NkmD1wg; expires=Wed, 18-Dec-2019 05:33:17 GMT; path=/; secure; HttpOnly
X-FEProxyInfo: CY4PR01CA0001.PROD.EXCHANGELABS.COM
X-CalculatedBETarget: CY4PR16MB1736.namprd16.prod.outlook.com
X-BackEndHttpStatus: 302
X-RUM-Validated: 1
X-Content-Type-Options: nosniff
X-BackEnd-Begin: 2019-12-17T23:31:17.043
X-BackEnd-End: 2019-12-17T23:31:17.045
X-DiagInfo: CY4PR16MB1736
X-BEServer: CY4PR16MB1736
X-UA-Compatible: IE=EmulateIE7
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Proxy-RoutingCorrectness: 1
X-Proxy-BackendServerStatus: 302
X-FEServer: CY4PR01CA0001
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Proxy-RoutingCorrectness: 1
X-FEServer: SN6PR16CA0070
Date: Tue, 17 Dec 2019 23:31:16 GMT
Connection: close
HTTP/1.1 200 OK
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Expires: -1
Vary: Accept-Encoding
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Link: <https://aadcdn.msauth.net>; rel=preconnect; crossorigin
Link: <https://aadcdn.msauth.net>; rel=dns-prefetch
Link: <https://aadcdn.msftauth.net>; rel=dns-prefetch
X-DNS-Prefetch-Control: on
x-ms-request-id: c815f3b0-eb63-418a-aba0-02a2b91e0b00
x-ms-ests-server: 2.1.9767.22 - WST ProdSlices
P3P: CP="DSP CUR OTPi IND OTRi ONL FIN"
Set-Cookie: buid=AQABAAEAAACQN9QBRU3jT6bcBQLZNUj75NmOomNeXmb6j2HLSKUkZahTobUkM_WUYcTWyeno1USpC8HRYvDHVdWlDQr5q1ZloiW1y07GM4MWayH2b5QzwfQ-mX7YgFHpOqGff8MmjZkgAA; expires=Thu, 16-Jan-2020 23:31:17 GMT; path=/; secure; HttpOnly; SameSite=None
Set-Cookie: fpc=AlAYgr39aC9LkY9Wg_4tqH6erOTJAQAAAERci9UOAAAA; expires=Thu, 16-Jan-2020 23:31:17 GMT; path=/; secure; HttpOnly; SameSite=None
Set-Cookie: esctx=AQABAAAAAACQN9QBRU3jT6bcBQLZNUj7RvyJLNJ3DmARW1VGCLD8rHNA5FHXbt9lPNNrBib0MHBkJxd3dLaAfsbEw6sY2KtMDe6SCBKlsR6JlMfDG2MVEBNXjQnWUCgdzln12Rxet5OoPBS0VX5obKzQlKoBoKk_FZmYqaRXa8gv7GiKmHgT0WtAToarpafNFQ4E2CptcPwgAA; domain=.login.microsoftonline.com; path=/; secure; HttpOnly; SameSite=None
Set-Cookie: x-ms-gateway-slice=prod; path=/; SameSite=None; secure; HttpOnly
Set-Cookie: stsservicecookie=ests; path=/; SameSite=None; secure; HttpOnly
Date: Tue, 17 Dec 2019 23:31:16 GMT
Connection: close
Content-Length: 44868