Is urlscan.io down or not working?

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

Add comment

What to do if the site urlscan.io is not available? Try our guide.

urlscan.io outage reports in the last 24 hours

urlscan.io - 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:

URL and website scanner - urlscan.io

Main page description:

urlscan.io - Website scanner for suspicious and malicious URLs

Main page keywords:

url,website,web,scanner,analyze,analyzer

Protocol:

https

Status code:

200

Page size:

30.8 KB

Response time:

0.120sec.

IP:

49.12.22.106

Response headers:

server:	nginx
date:	Tue, 01 Oct 2024 04:49:43 GMT
content-type:	text/html; charset=utf-8
content-length:	31496
connection:	close
cache-control:	public, max-age=60
etag:	W/"7b08-xa++SeBM3R5XMQ8m+2cSFpuW3ls"
content-security-policy:	default-src 'self' data:; script-src 'self' data: developers.google.com www.google.com www.gstatic.com; style-src 'self' fonts.googleapis.com www.google.com; img-src * data:; font-src 'self' fonts.gstatic.com; child-src 'self'; frame-src https://www.google.com/recaptcha/; form-action 'self'; connect-src 'self'; upgrade-insecure-requests; frame-ancestors 'none'
referrer-policy:	unsafe-url
strict-transport-security:	max-age=63072000; includeSubdomains; preload
x-content-type-options:	nosniff
x-frame-options:	DENY
x-xss-protection:	0
x-proxy-cache:	HIT
x-robots-tag:	all

DNS records:

A	address	49.12.22.106
A	ttl	300
MX	exchange	alt1.aspmx.l.google.com
MX	priority	5
MX	exchange	aspmx.l.google.com
MX	priority	1
MX	exchange	alt2.aspmx.l.google.com
MX	priority	5
MX	exchange	alt4.aspmx.l.google.com
MX	priority	10
MX	exchange	alt3.aspmx.l.google.com
MX	priority	10
NS	value	ns-1558.awsdns-02.co.uk
NS	value	ns-483.awsdns-60.com
NS	value	ns-940.awsdns-53.net
NS	value	ns-1198.awsdns-21.org
TXT	entries	google-site-verification=wnDEcrkl2YX6qfKYzO7oAtAx_6fetr3zo_-iFeZWf1c
TXT	entries	google-site-verification=7xPs7Atnb1EgiDKcrE8nIi4OFX5qPogpH_KCxkot7D4
TXT	entries	v=spf1 include:_spf.mlsend.com include:mailgun.org include:_spf.google.com include:servers.mcsv.net -all
SOA	nsname	ns-1198.awsdns-21.org
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400

SEO headers

h1 urlscan.io

h3 Recent scans

h4 Thanks to our corporate sponsors

h4 0 0

h4 0 0 0

How to solve problems with urlscan.io

Errors on the urlscan.io 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 urlscan.io on your own.