Is investigationdiscovery.com down or not working?

What happened to investigationdiscovery.com, why did the website go down and not work? Here you can see who else is having the same problem with investigationdiscovery.com, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, investigationdiscovery.com is working fine, but single failures are possible. If investigationdiscovery.com does not work for you, then report your problem and write a comment.
Add comment

What to do if the site investigationdiscovery.com is not available? Try our guide.

investigationdiscovery.com outage reports in the last 24 hours

investigationdiscovery.com - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Protocol:
https
Status code:
200
Page size:
71.8 KB
Response time:
0.815sec.
IP:
34.225.104.126
Response headers:
content-type: text/html
content-length: 73527
connection: close
date: Tue, 01 Oct 2024 03:25:58 GMT
last-modified: Wed, 25 Sep 2024 13:49:36 GMT
etag: "66f414f0-11f37"
cache-control: public, max-age=60
strict-transport-security: max-age=31536000; includeSubDomains, max-age=15724800; includeSubDomains;
x-content-type-options: nosniff
accept-ranges: bytes
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 3da92f19744e3229b09a019ec66be172.cloudfront.net (CloudFront)
x-amz-cf-pop: PRG50-C1
x-amz-cf-id: w6yjQtdSEY6O6AKWHTBGI3jHWPMKNAG-8oj9jylYXxBNeFTdzbz-Xw==
DNS records:
A address3.229.109.26
ttl60
A address34.225.104.126
ttl60
MX exchangestr-mx07.discovery.com
priority10
MX exchangestr-mx08.discovery.com
priority10
MX exchangemx08.discovery.com
priority10
NS valuens-628.awsdns-14.net
NS valuens-1640.awsdns-13.co.uk
NS valuens-1174.awsdns-18.org
NS valuens-393.awsdns-49.com
TXT entriesfacebook-domain-verification=l96itwud8hpzfj58pdidfpnlf14thk
TXT entriesgoogle-site-verification=SefsTX-CsgtjvXWMGsPYjB_bWXnJtznXH6aT33BRcz8
TXT entriesgoogle-site-verification=e39x3cBosFuJl-GzCVHORnXM1YnXwXDTimNT6iEXQ2U
TXT entriesd264c0ghuxiscr.cloudfront.net
TXT entriesded0pn04lzm7x.cloudfront.net
TXT entriesgoogle-site-verification=xsMf6EoZlCePRgfd9biJpYIl3UuFjk94PfzlyPYRFh8
TXT entriesgoogle-site-verification=XlTEjhkidHyKiYi64WSzb6JC2RlQPs7vRovsJMlVSh4
SOA nsnamens-1640.awsdns-13.co.uk
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with investigationdiscovery.com

Errors on the investigationdiscovery.com website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of investigationdiscovery.com on your own.