Is sec.gov down or not working?

What happened to sec.gov, why did the website go down and not work? Here you can see who else is having the same problem with sec.gov, 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, sec.gov is working fine, but single failures are possible. If sec.gov does not work for you, then report your problem and write a comment.

Add comment

What to do if the site sec.gov is not available? Try our guide.

sec.gov outage reports in the last 24 hours

sec.gov - 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.

Your name:

Message:

Technical information

Main page title:

SEC.gov | Request Rate Threshold Exceeded

Protocol:

http

Status code:

403

Page size:

1.9 KB

Response time:

0.038sec.

IP:

23.42.164.141

Response headers:

server:	AkamaiGHost
mime-version:	1.0
content-length:	1925
cache-control:	no-cache, no-store, must-revalidate
pragma:	no-cache
expires:	0
content-type:	text/html
date:	Mon, 30 Sep 2024 21:03:13 GMT
connection:	close

DNS records:

A	address	184.24.23.18
A	ttl	20
AAAA	address	2a02:26f0:1180:189::17b2
AAAA	ttl	20
AAAA	address	2a02:26f0:1180:184::17b2
AAAA	ttl	20
MX	exchange	d1-ip01.sec.gov
MX	priority	10
MX	exchange	d2-ip01.sec.gov
MX	priority	10
NS	value	a1-32.akam.net
NS	value	a20-66.akam.net
NS	value	a7-65.akam.net
NS	value	a3-67.akam.net
NS	value	a18-65.akam.net
NS	value	a6-64.akam.net
TXT	entries	cisco-ci-domain-verification=6916e9cd0609e361edcbea866535f0538c7de04c019c5d4669caf5eeefd6ca58
TXT	entries	v=spf1 redirect=_spf.sec.gov
TXT	entries	spf2.0/pra
TXT	entries	apple-domain-verification=S8k2enqunoaJUuJA
TXT	entries	X4U/iY9l80yKA4myted6fgTySSIGMnzLSdq/xloixnLrcdKk/Vv/iv0ilF4VuFx0pmVEMwe5HvDilwYRg72RGA==
TXT	entries	google-site-verification=9GMDw2_WQPOazSHPiWGVPuC5PKpwfADDisMN7sEhMM0
TXT	entries	MS=ms60731568
TXT	entries	webexdomainverification.7GA36=c6ae2a26-765a-4237-b87d-f6bddc7a9cd8
TXT	entries	y2tqkx3t30c3sr5smhvn1d0rvcy647qq
TXT	entries	dtm-domain-verification=BcAH-g0ZVzOswh5LL4axbbHI3sWosnxP15V8LAgmmPw
TXT	entries	adobe-idp-site-verification=97319342-419d-4786-87b7-130e1e301d13
TXT	entries	apple-domain-verification=jlno4yB7g7OgHZk5
SOA	nsname	d1-dns-f1.sec.gov
	hostmaster	hostmaster.sec.gov
	serial	2020112703
	refresh	10800
	retry	3600
	expire	2419200
	minttl	300
CAA	critical	0
CAA	issue	digicert.com
CAA	critical	0
CAA	issue	letsencrypt.org
CAA	critical	0
CAA	issue	entrust.net
CAA	critical	0
CAA	iodef	mailto:[email protected]
CAA	critical	0
CAA	issuewild	;

SEO headers

h1 Automated access to our sites must comply with SEC.gov's Privacy and Security Policy.

How to solve problems with sec.gov

Errors on the sec.gov 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 sec.gov on your own.