validcc.su

validcc.su is SSL secured

Free website and domain report on validcc.su

Last Updated: 27th March, 2021 Update Now
Overview

Snoop Summary for validcc.su

This is a free and comprehensive report about validcc.su. Validcc.su is hosted in Netherlands on a server with an IP address of 192.42.118.104, where the local currency is EUR and Dutch is the local language. Validcc.su has the potential to be earning an estimated $1 USD per day from advertising revenue. If validcc.su was to be sold it would possibly be worth $936 USD (based on the daily revenue potential of the website over a 24 month period). Validcc.su receives an estimated 445 unique visitors every day - a decent amount of traffic! This report was last updated 27th March, 2021.

About validcc.su

Site Preview: validcc.su validcc.su
Title: The Spamhaus Project
Description: Spamhaus is the world leader in supplying realtime highly accurate threat intelligence to the Internet's major networks.
Keywords and Tags: block list, block spam, blocklist, botnet, bulk email, dnsbl, internet services, junk email, malware, rokso, sbl, spam, spam filtering, spam filters, spam house, spam statistics, spamhaus, spamhouse, spammers, spamware, the spamhaus project, threat intelligence, unsolicited bulk email, unsolicited commercial email, valcc bazar, validcc, validcc bazar, validcc bz, validcc live new domain, validcc new domain, validcc su, validcc su review, vclub su, www valcc bazar, zen
Related Terms: validcc.su
Fav Icon:
Age: Over 9 years old
Domain Created: 2nd August, 2014
Domain Updated:
Domain Expires: 2nd August, 2021
Review

Snoop Score

1/5

Valuation

$936 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,048,380
Alexa Reach:
SEMrush Rank (US): 807,851
SEMrush Authority Score: 38
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 49 0
Traffic: 1,170 0
Cost: $530 USD $0 USD
Traffic

Visitors

Daily Visitors: 445
Monthly Visitors: 13,544
Yearly Visitors: 162,425
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $39 USD
Yearly Revenue: $463 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 476
Referring Domains: 176
Referring IPs: 163
Validcc.su has 476 backlinks according to SEMrush. 12% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve validcc.su's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of validcc.su's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://validcc.biz/
Target: https://validcc.su/login.php

2
Source: https://www.validcc.market/
Target: https://validcc.su/login.php

Top Ranking Keywords (US)

1
Keyword: valcc bazar
Ranked Page: https://validcc.su/

2
Keyword: validcc su
Ranked Page: https://validcc.su/

3
Keyword: validcc
Ranked Page: https://validcc.su/

4
Keyword: validcc bazar
Ranked Page: https://validcc.su/

5
Keyword: www valcc bazar
Ranked Page: https://validcc.su/

Domain Analysis

Value Length
Domain: validcc.su 10
Domain Name: validcc 7
Extension (TLD): su 2
Expiry Check:

Page Speed Analysis

Average Load Time: 3.63 seconds
Load Time Comparison: Faster than 16% of sites

PageSpeed Insights

Avg. (All Categories) 67
Performance 98
Accessibility 78
Best Practices 60
SEO 82
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.spamhaus.org/
Updated: 27th March, 2021

1.02 seconds
First Contentful Paint (FCP)
74%
23%
3%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for validcc.su. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.4 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive validcc.su as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://validcc.su/
http/1.1
0
339.43499997258
242
0
301
text/html
https://www.spamhaus.org/
h2
340.06100008264
428.83200012147
3876
14806
200
text/html
Document
https://www.spamhaus.org/cdn-cgi/apps/head/FS1Yir6GehjiSIsp5saVdDOg6Nw.js
h2
442.95800011605
500.66599994898
3020
6379
200
application/javascript
Script
https://www.spamhaus.org/styles/sh.css
h2
443.11399990693
537.64199977741
4151
18577
200
text/css
Stylesheet
https://www.spamhaus.org/images/sh_logo1.jpg
h2
504.49700001627
583.19999976084
7004
5999
200
image/jpeg
Image
https://www.spamhaus.org/images/sh_logo2.jpg
h2
504.64500021189
566.25800020993
5392
4387
200
image/jpeg
Image
https://www.spamhaus.org/images/shbn_home_on.gif
h2
504.86399978399
569.50999982655
1501
514
200
image/gif
Image
https://www.spamhaus.org/images/shbn_sbl_s.gif
h2
505.11900009587
570.71400014684
1592
605
200
image/gif
Image
https://www.spamhaus.org/images/shbn_xbl.gif
h2
505.21800015122
564.82800003141
1593
606
200
image/gif
Image
https://www.spamhaus.org/images/shbn_pbl.gif
h2
505.58400014415
569.10800002515
1567
580
200
image/gif
Image
https://www.spamhaus.org/images/shbn_dbl.gif
h2
505.69000001997
588.06400001049
1586
599
200
image/gif
Image
https://www.spamhaus.org/images/shbn_drop.gif
h2
505.93100022525
567.24599981681
1595
608
200
image/gif
Image
https://www.spamhaus.org/images/shbn_rokso.gif
h2
506.07200013474
568.78900015727
1674
687
200
image/gif
Image
https://www.spamhaus.org/images/shbn_blank.gif
h2
506.18899986148
588.54199992493
1502
515
200
image/gif
Image
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
h2
506.53100013733
601.09800007194
207355
206363
200
image/png
Image
https://www.spamhaus.org/images/shad02.gif
h2
506.71500014141
539.54999987036
1116
130
200
image/gif
Image
https://www.spamhaus.org/images/sbl_badge_hp.gif
h2
506.83900015429
568.51400015876
2629
1641
200
image/gif
Image
https://www.spamhaus.org/images/spacer.gif
h2
507.11600016803
563.70500009507
1034
49
200
image/gif
Image
https://www.spamhaus.org/images/xbl_badge_hp.gif
h2
507.28400005028
540.19800014794
2574
1586
200
image/gif
Image
https://www.spamhaus.org/images/pbl_badge_hp.gif
h2
507.52400001511
582.59399980307
2855
1867
200
image/gif
Image
https://www.spamhaus.org/images/dbl_badge_hp.gif
h2
507.69199989736
568.1579997763
2715
1727
200
image/gif
Image
https://www.spamhaus.org/images/zen_badge3.gif
h2
508.28400021419
576.95099990815
3225
2237
200
image/gif
Image
https://www.spamhaus.org/images/pointer.gif
h2
508.450999856
538.06499997154
1258
271
200
image/gif
Image
https://www.spamhaus.org/images/spot_filterdata.jpg
h2
508.5909999907
543.98600012064
8399
7394
200
image/jpeg
Image
https://www.spamhaus.org/images/spot_datafeed.jpg
h2
508.72399983928
550.34000007436
8069
7064
200
image/jpeg
Image
https://www.spamhaus.org/images/rokso_hp.gif
h2
508.9090000838
538.89800002798
2493
1505
200
image/gif
Image
https://www.spamhaus.org/images/spot_top10.jpg
h2
509.0729999356
538.42099988833
8599
7594
200
image/jpeg
Image
https://www.spamhaus.org/cookieinfo.min.js
h2
502.39699985832
534.8459999077
4000
7701
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
h2
509.25499992445
532.94900013134
39879
98778
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
h2
554.97100017965
581.29800017923
41813
111544
200
application/javascript
Script
559.73799992353
559.75200003013
0
0
-1
Image
https://www.google-analytics.com/analytics.js
h2
595.12000018731
598.85999979451
19610
47332
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j88&a=545532871&t=pageview&_s=1&dl=https%3A%2F%2Fwww.spamhaus.org%2F&ul=en-us&de=UTF-8&dt=The%20Spamhaus%20Project&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=304979903&gjid=1700016559&cid=781730708.1616843247&tid=UA-120927734-1&_gid=1843270245.1616843247&_r=1&gtm=2ou3h0&z=2056522550
h2
642.57400017232
645.89599985629
619
1
200
text/plain
XHR
https://static.hotjar.com/c/hotjar-1643020.js?sv=7
h2
650.53599979728
744.10100001842
2870
5732
200
application/javascript
Script
https://script.hotjar.com/modules.35981999a656a5a28309.js
h2
747.36399995163
767.23700016737
59187
222202
200
application/javascript
Script
https://vars.hotjar.com/box-f8697186ca3a8d08bfff6b2981bb517b.html
h2
804.64900005609
819.8839998804
1326
1896
200
text/html
Document
https://in.hotjar.com/api/v2/client/sites/1643020/visit-data?sv=7
h2
841.55000001192
944.90000000224
373
171
200
application/json
XHR
https://ws14.hotjar.com/api/v2/sites/1643020/recordings/content
http/1.1
951.34499995038
1449.698000215
397
69
200
application/json
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
460.806
8.18
531.419
7.584
569.366
12.334
583.197
7.1
593.3
7.894
601.638
8.542
616.513
8.269
634.804
11.28
647.939
23.39
671.344
8.949
804.427
24.776
851.723
6.175
862.54
42.621
974.572
7.443
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Validcc.su should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Validcc.su should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Validcc.su should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Validcc.su should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Validcc.su should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Validcc.su should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 90 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.spamhaus.org/
89.767
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Validcc.su should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://validcc.su/
190
https://www.spamhaus.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Validcc.su should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
0

Diagnostics

Avoids enormous network payloads — Total size was 448 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
207355
https://script.hotjar.com/modules.35981999a656a5a28309.js
59187
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
41813
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
39879
https://www.google-analytics.com/analytics.js
19610
https://www.spamhaus.org/images/spot_top10.jpg
8599
https://www.spamhaus.org/images/spot_filterdata.jpg
8399
https://www.spamhaus.org/images/spot_datafeed.jpg
8069
https://www.spamhaus.org/images/sh_logo1.jpg
7004
https://www.spamhaus.org/images/sh_logo2.jpg
5392
Avoids an excessive DOM size — 292 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
292
Maximum DOM Depth
17
Maximum Child Elements
20
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Validcc.su should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://script.hotjar.com/modules.35981999a656a5a28309.js
83.211
71.359
3.596
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
140.901
Other
55.223
Style & Layout
16.136
Script Parsing & Compilation
15.349
Parse HTML & CSS
12.075
Rendering
7.123
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 37 requests • 448 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
37
458690
Image
23
277327
Script
7
170379
Document
2
5202
Stylesheet
1
4151
Other
4
1631
Media
0
0
Font
0
0
Third-party
10
166316
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
81692
0
64153
0
20229
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Remove unused JavaScript — Potential savings of 75 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://script.hotjar.com/modules.35981999a656a5a28309.js
59187
32150
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
41813
23499
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
39879
20952
Serve images in next-gen formats — Potential savings of 174 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
206363
178283

Diagnostics

Serve static assets with an efficient cache policy — 27 resources found
Validcc.su can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://static.hotjar.com/c/hotjar-1643020.js?sv=7
60000
2870
https://www.spamhaus.org/cookieinfo.min.js
1800000
4000
https://www.google-analytics.com/analytics.js
7200000
19610
https://www.spamhaus.org/styles/sh.css
86400000
4151
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
604800000
207355
https://www.spamhaus.org/images/spot_top10.jpg
604800000
8599
https://www.spamhaus.org/images/spot_filterdata.jpg
604800000
8399
https://www.spamhaus.org/images/spot_datafeed.jpg
604800000
8069
https://www.spamhaus.org/images/sh_logo1.jpg
604800000
7004
https://www.spamhaus.org/images/sh_logo2.jpg
604800000
5392
https://www.spamhaus.org/images/zen_badge3.gif
604800000
3225
https://www.spamhaus.org/images/pbl_badge_hp.gif
604800000
2855
https://www.spamhaus.org/images/dbl_badge_hp.gif
604800000
2715
https://www.spamhaus.org/images/sbl_badge_hp.gif
604800000
2629
https://www.spamhaus.org/images/xbl_badge_hp.gif
604800000
2574
https://www.spamhaus.org/images/rokso_hp.gif
604800000
2493
https://www.spamhaus.org/images/shbn_rokso.gif
604800000
1674
https://www.spamhaus.org/images/shbn_drop.gif
604800000
1595
https://www.spamhaus.org/images/shbn_xbl.gif
604800000
1593
https://www.spamhaus.org/images/shbn_sbl_s.gif
604800000
1592
https://www.spamhaus.org/images/shbn_dbl.gif
604800000
1586
https://www.spamhaus.org/images/shbn_pbl.gif
604800000
1567
https://www.spamhaus.org/images/shbn_blank.gif
604800000
1502
https://www.spamhaus.org/images/shbn_home_on.gif
604800000
1501
https://www.spamhaus.org/images/pointer.gif
604800000
1258
https://www.spamhaus.org/images/shad02.gif
604800000
1116
https://www.spamhaus.org/images/spacer.gif
604800000
1034
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of validcc.su. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Validcc.su may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
60

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that validcc.su should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://validcc.su/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://www.spamhaus.org/images/shad02.gif
920 x 15 (61.33)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 13 (12.92)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/spacer.gif
10 x 12 (0.83)
10 x 10 (1.00)
Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.spamhaus.org/images/shad02.gif
920 x 15
10 x 15
920 x 15
https://www.spamhaus.org/images/spacer.gif
10 x 12
10 x 10
10 x 12

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
[Report Only] Refused to connect to 'wss://ws14.hotjar.com/api/v2/client/ws' because it violates the following Content Security Policy directive: "default-src https://www.spamhaus.org https: 'unsafe-inline' 'unsafe-eval'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.
[Report Only] Refused to load the image 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==' because it violates the following Content Security Policy directive: "default-src https://www.spamhaus.org https: 'unsafe-inline' 'unsafe-eval'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Refused to connect to 'wss://ws14.hotjar.com/api/v2/client/ws' because it violates the following Content Security Policy directive: "default-src https://www.spamhaus.org https: 'unsafe-inline' 'unsafe-eval'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.
Refused to load the image 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==' because it violates the following Content Security Policy directive: "default-src https://www.spamhaus.org https: 'unsafe-inline' 'unsafe-eval'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Content security policy
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for validcc.su. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of validcc.su on mobile screens.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
18

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of validcc.su. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of validcc.su on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 61
Performance 82
Accessibility 78
Best Practices 60
SEO 69
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.spamhaus.org/
Updated: 27th March, 2021

1.50 seconds
First Contentful Paint (FCP)
58%
36%
6%

0.25 seconds
First Input Delay (FID)
2%
96%
2%

Simulate loading on mobile
82

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for validcc.su. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.5 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive validcc.su as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://validcc.su/
http/1.1
0
388.19000031799
245
0
301
text/html
https://www.spamhaus.org/
h2
388.64000001922
425.7570002228
3874
14806
200
text/html
Document
https://www.spamhaus.org/cdn-cgi/apps/head/FS1Yir6GehjiSIsp5saVdDOg6Nw.js
h2
439.48900001124
467.81700011343
3020
6379
200
application/javascript
Script
https://www.spamhaus.org/styles/sh.css
h2
439.63700020686
495.42000005022
4113
18228
200
text/css
Stylesheet
https://www.spamhaus.org/images/sh_logo1.jpg
h2
472.10500016809
522.34499994665
7004
5999
200
image/jpeg
Image
https://www.spamhaus.org/images/sh_logo2.jpg
h2
472.26200019941
531.33800020441
5392
4387
200
image/jpeg
Image
https://www.spamhaus.org/images/shbn_home_on.gif
h2
472.46500011533
509.98800015077
1501
514
200
image/gif
Image
https://www.spamhaus.org/images/shbn_sbl_s.gif
h2
472.60500025004
503.07000009343
1592
605
200
image/gif
Image
https://www.spamhaus.org/images/shbn_xbl.gif
h2
473.02599996328
519.47800023481
1593
606
200
image/gif
Image
https://www.spamhaus.org/images/shbn_pbl.gif
h2
473.18500000983
505.27800014243
1567
580
200
image/gif
Image
https://www.spamhaus.org/images/shbn_dbl.gif
h2
473.31300005317
504.58599999547
1586
599
200
image/gif
Image
https://www.spamhaus.org/images/shbn_drop.gif
h2
473.5440001823
537.83100005239
1595
608
200
image/gif
Image
https://www.spamhaus.org/images/shbn_rokso.gif
h2
473.77400007099
506.40700012445
1674
687
200
image/gif
Image
https://www.spamhaus.org/images/shbn_blank.gif
h2
473.95000001416
505.0000003539
1502
515
200
image/gif
Image
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
h2
474.98199995607
517.26499991491
207355
206363
200
image/png
Image
https://www.spamhaus.org/images/shad02.gif
h2
475.07600020617
532.58900018409
1116
130
200
image/gif
Image
https://www.spamhaus.org/images/sbl_badge_hp.gif
h2
475.16399994493
502.80500017107
2629
1641
200
image/gif
Image
https://www.spamhaus.org/images/spacer.gif
h2
475.2650000155
503.95300006494
1034
49
200
image/gif
Image
https://www.spamhaus.org/images/xbl_badge_hp.gif
h2
475.63000023365
537.55100024864
2574
1586
200
image/gif
Image
https://www.spamhaus.org/images/pbl_badge_hp.gif
h2
475.74499994516
503.33099998534
2855
1867
200
image/gif
Image
https://www.spamhaus.org/images/dbl_badge_hp.gif
h2
475.83000035957
537.17300016433
2715
1727
200
image/gif
Image
https://www.spamhaus.org/images/zen_badge3.gif
h2
475.9329999797
532.19299996272
3225
2237
200
image/gif
Image
https://www.spamhaus.org/images/pointer.gif
h2
476.11499996856
516.94100024179
1258
271
200
image/gif
Image
https://www.spamhaus.org/images/spot_filterdata.jpg
h2
476.26100014895
508.42600036412
8399
7394
200
image/jpeg
Image
https://www.spamhaus.org/images/spot_datafeed.jpg
h2
476.38500016183
516.46000007167
8069
7064
200
image/jpeg
Image
https://www.spamhaus.org/images/rokso_hp.gif
h2
476.50300012901
509.09600034356
2493
1505
200
image/gif
Image
https://www.spamhaus.org/images/spot_top10.jpg
h2
476.61700006574
534.54399993643
8599
7594
200
image/jpeg
Image
https://www.spamhaus.org/cookieinfo.min.js
h2
470.16500029713
845.95400001854
3998
7701
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
h2
476.79700003937
502.17600027099
39880
98778
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
h2
499.8130002059
528.71300000697
41809
111544
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
555.32000027597
559.70699992031
19610
47332
200
text/javascript
Script
https://static.hotjar.com/c/hotjar-1643020.js?sv=7
h2
574.76800028235
610.0860000588
2878
5732
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j88&a=996593538&t=pageview&_s=1&dl=https%3A%2F%2Fwww.spamhaus.org%2F&ul=en-us&de=UTF-8&dt=The%20Spamhaus%20Project&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IEBAAUABAAAAAC~&jid=945077980&gjid=1855215834&cid=425605359.1616843262&tid=UA-120927734-1&_gid=1666845743.1616843262&_r=1&gtm=2ou3h0&z=778651814
h2
593.49300013855
597.2569999285
619
1
200
text/plain
XHR
https://script.hotjar.com/modules.35981999a656a5a28309.js
h2
613.18300012499
634.83799993992
59187
222202
200
application/javascript
Script
854.65600015596
854.67300005257
0
0
-1
Image
https://vars.hotjar.com/box-f8697186ca3a8d08bfff6b2981bb517b.html
h2
903.94800016657
919.75100012496
1326
1896
200
text/html
Document
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
459.33
8.276
500.465
7.2
530.434
18.04
561.155
5.245
567.104
7.367
578.367
7.835
586.626
9.198
598.893
6.719
605.855
18.868
674.501
21.477
878.006
8.704
886.728
7.638
953.558
8.042
966.264
7.172
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 2810 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Validcc.su should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Validcc.su should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Validcc.su should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Validcc.su should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Validcc.su should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Validcc.su should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 40 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.spamhaus.org/
38.113
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Validcc.su should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://validcc.su/
630
https://www.spamhaus.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Validcc.su should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
0

Diagnostics

Avoids enormous network payloads — Total size was 447 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
207355
https://script.hotjar.com/modules.35981999a656a5a28309.js
59187
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
41809
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
39880
https://www.google-analytics.com/analytics.js
19610
https://www.spamhaus.org/images/spot_top10.jpg
8599
https://www.spamhaus.org/images/spot_filterdata.jpg
8399
https://www.spamhaus.org/images/spot_datafeed.jpg
8069
https://www.spamhaus.org/images/sh_logo1.jpg
7004
https://www.spamhaus.org/images/sh_logo2.jpg
5392
Avoids an excessive DOM size — 292 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
292
Maximum DOM Depth
17
Maximum Child Elements
20
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Validcc.su should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.spamhaus.org/
227.644
17.324
4.64
https://script.hotjar.com/modules.35981999a656a5a28309.js
128.972
102.128
14.352
Unattributable
110.108
4.356
1.024
https://www.google-analytics.com/analytics.js
80.372
68.416
6.04
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
70.776
56
10.572
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
67.656
52.636
11.516
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
345.756
Other
194.46
Style & Layout
89.1
Script Parsing & Compilation
61.68
Rendering
48.1
Parse HTML & CSS
41.884
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 35 requests • 447 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
35
457886
Image
23
277327
Script
7
170382
Document
2
5200
Stylesheet
1
4113
Other
2
864
Media
0
0
Font
0
0
Third-party
8
165554
Minimize third-party usage — Third-party code blocked the main thread for 30 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
20229
14.96
63391
10.868
81689
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://script.hotjar.com/modules.35981999a656a5a28309.js
5711
86
https://www.google-analytics.com/analytics.js
3751
75
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 5.1 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.4 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Serve images in next-gen formats — Potential savings of 174 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
206363
178283

Diagnostics

Serve static assets with an efficient cache policy — 27 resources found
Validcc.su can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://static.hotjar.com/c/hotjar-1643020.js?sv=7
60000
2878
https://www.spamhaus.org/cookieinfo.min.js
1800000
3998
https://www.google-analytics.com/analytics.js
7200000
19610
https://www.spamhaus.org/styles/sh.css
86400000
4113
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
604800000
207355
https://www.spamhaus.org/images/spot_top10.jpg
604800000
8599
https://www.spamhaus.org/images/spot_filterdata.jpg
604800000
8399
https://www.spamhaus.org/images/spot_datafeed.jpg
604800000
8069
https://www.spamhaus.org/images/sh_logo1.jpg
604800000
7004
https://www.spamhaus.org/images/sh_logo2.jpg
604800000
5392
https://www.spamhaus.org/images/zen_badge3.gif
604800000
3225
https://www.spamhaus.org/images/pbl_badge_hp.gif
604800000
2855
https://www.spamhaus.org/images/dbl_badge_hp.gif
604800000
2715
https://www.spamhaus.org/images/sbl_badge_hp.gif
604800000
2629
https://www.spamhaus.org/images/xbl_badge_hp.gif
604800000
2574
https://www.spamhaus.org/images/rokso_hp.gif
604800000
2493
https://www.spamhaus.org/images/shbn_rokso.gif
604800000
1674
https://www.spamhaus.org/images/shbn_drop.gif
604800000
1595
https://www.spamhaus.org/images/shbn_xbl.gif
604800000
1593
https://www.spamhaus.org/images/shbn_sbl_s.gif
604800000
1592
https://www.spamhaus.org/images/shbn_dbl.gif
604800000
1586
https://www.spamhaus.org/images/shbn_pbl.gif
604800000
1567
https://www.spamhaus.org/images/shbn_blank.gif
604800000
1502
https://www.spamhaus.org/images/shbn_home_on.gif
604800000
1501
https://www.spamhaus.org/images/pointer.gif
604800000
1258
https://www.spamhaus.org/images/shad02.gif
604800000
1116
https://www.spamhaus.org/images/spacer.gif
604800000
1034

Metrics

Largest Contentful Paint — 4.3 s
The timing of the largest text or image that is painted.

Opportunities

Remove unused JavaScript — Potential savings of 82 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://script.hotjar.com/modules.35981999a656a5a28309.js
59187
39783
https://www.googletagmanager.com/gtm.js?id=GTM-K9S544M
41809
23497
https://www.googletagmanager.com/gtag/js?id=UA-120927734-1
39880
20953
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of validcc.su. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Validcc.su may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
60

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that validcc.su should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://validcc.su/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://www.spamhaus.org/images/shad02.gif
920 x 15 (61.33)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 8 (21.00)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 13 (12.92)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/shad02.gif
168 x 15 (11.20)
10 x 15 (0.67)
https://www.spamhaus.org/images/spacer.gif
10 x 12 (0.83)
10 x 10 (1.00)
Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.spamhaus.org/images/SH-HomePage-Image-2018-01.png
920 x 380
920 x 380
1840 x 760
https://www.spamhaus.org/images/spot_datafeed.jpg
168 x 126
168 x 126
336 x 252
https://www.spamhaus.org/images/spot_filterdata.jpg
168 x 126
168 x 126
336 x 252
https://www.spamhaus.org/images/spot_top10.jpg
168 x 126
168 x 126
336 x 252
https://www.spamhaus.org/images/shad02.gif
920 x 15
10 x 15
1840 x 30
https://www.spamhaus.org/images/sh_logo1.jpg
260 x 32
260 x 32
520 x 64
https://www.spamhaus.org/images/sh_logo2.jpg
260 x 32
260 x 32
520 x 64
https://www.spamhaus.org/images/dbl_badge_hp.gif
168 x 36
168 x 36
336 x 72
https://www.spamhaus.org/images/pbl_badge_hp.gif
168 x 36
168 x 36
336 x 72
https://www.spamhaus.org/images/sbl_badge_hp.gif
168 x 36
168 x 36
336 x 72
https://www.spamhaus.org/images/xbl_badge_hp.gif
168 x 36
168 x 36
336 x 72
https://www.spamhaus.org/images/zen_badge3.gif
168 x 36
168 x 36
336 x 72
https://www.spamhaus.org/images/rokso_hp.gif
168 x 26
168 x 26
336 x 52
https://www.spamhaus.org/images/shbn_blank.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_dbl.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_drop.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_home_on.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_pbl.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_rokso.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_sbl_s.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/shbn_xbl.gif
92 x 28
92 x 28
184 x 56
https://www.spamhaus.org/images/spacer.gif
10 x 12
10 x 10
20 x 24
https://www.spamhaus.org/images/pointer.gif
10 x 10
10 x 10
20 x 20

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
[Report Only] Refused to load the image 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==' because it violates the following Content Security Policy directive: "default-src https://www.spamhaus.org https: 'unsafe-inline' 'unsafe-eval'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Refused to load the image 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==' because it violates the following Content Security Policy directive: "default-src https://www.spamhaus.org https: 'unsafe-inline' 'unsafe-eval'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Content security policy
69

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for validcc.su. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of validcc.su on mobile screens.
Document doesn't use legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
17

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of validcc.su. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of validcc.su on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 192.42.118.104
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Very Risky
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: spamhaus.org
Issued By: Cloudflare Inc ECC CA-3
Valid From: 7th December, 2020
Valid To: 6th December, 2021
Subject: CN = spamhaus.org
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: b5f7e468
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 14768660890765207177169660947572244588
Serial Number (Hex): 0B1C57332FE31B7F844DFD970CD0C06C
Valid From: 7th December, 2024
Valid To: 6th December, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Dec 7 10:50:16.571 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:D2:B7:25:C5:FB:94:1A:A6:EB:67:A7:
A3:3D:79:6B:AD:9D:C6:95:CB:56:86:D6:EC:06:78:58:
68:B8:48:78:13:02:21:00:83:91:8D:7B:61:75:B3:63:
CF:D6:81:75:BB:C2:87:0D:66:27:FC:63:3C:09:42:C4:
9E:67:F2:C0:D1:E6:2F:96
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Dec 7 10:50:16.694 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:2F:27:B3:D2:08:A1:C4:1B:CD:9F:1A:3F:
01:FD:8D:4D:D5:A5:7C:CB:70:4C:48:7C:E9:54:27:62:
68:3B:FA:6E:02:21:00:F9:0C:40:82:93:79:BB:78:A8:
6B:98:EE:E0:D2:13:8B:56:0A:59:BF:87:F4:B2:03:46:
4E:23:CB:0D:49:9E:04
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:spamhaus.org
DNS:*.spamhaus.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
validcc.su. 192.42.118.104 IN 899

NS Records

Host Nameserver Class TTL
validcc.su. ns1.1984.is. IN 21599
validcc.su. ns2.1984.is. IN 21599
validcc.su. ns2.1984hosting.com. IN 21599
validcc.su. ns0.1984.is. IN 21599
validcc.su. ns1.1984hosting.com. IN 21599

AAAA Records

IP Address Class TTL
2001:67c:6ec:205::ffff:104 IN 899

MX Records

Priority Host Server Class TTL
10 validcc.su. mx1.1984.is. IN 899
20 validcc.su. mx2.1984.is. IN 899

SOA Records

Domain Name Primary NS Responsible Email TTL
validcc.su. ns0.1984.is. hostmaster.1984.is. 21599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th March, 2021
Content-Type: text/html; charset=UTF-8
Expires: 27th March, 2021
Cache-Control: public, max-age=1800
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Content-Security-Policy: default-src https://www.spamhaus.org https
Content-Security-Policy-Report-Only: default-src https://www.spamhaus.org https
Strict-Transport-Security: max-age=31536000; includeSubDomains
CF-Cache-Status: HIT
Age: 39
cf-request-id: 0914f7130e00003dd25d984000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
CF-RAY: 636827981c193dd2-EWR
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 2nd August, 2014
Changed:
Expires: 2nd August, 2021
Registrar: R01-SU
Status:
Nameservers: ns1.1984hosting.com
ns2.1984hosting.com
Owner Email: fenley@mailalt.com
Full Whois: % By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: VALIDCC.SU
nserver: ns1.1984hosting.com.
nserver: ns2.1984hosting.com.
state: REGISTERED, DELEGATED
person: Private Person
e-mail: fenley@mailalt.com
registrar: R01-SU
created: 2014-08-02T15:52:22Z
paid-till: 2021-08-02T16:52:22Z
free-date: 2021-09-04
source: TCI

Last updated on 2021-03-27T11:06:30Z

Nameservers

Name IP Address
ns1.1984hosting.com 185.42.137.114
ns2.1984hosting.com 93.95.226.53
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$351 USD
0/5
0/5
0/5

Sites hosted on the same IP address