flibusta.net

flibusta.net is SSL secured

Free website and domain report on flibusta.net

Last Updated: 6th August, 2022 Update Now
Overview

Snoop Summary for flibusta.net

This is a free and comprehensive report about flibusta.net. The domain flibusta.net is currently hosted on a server located in Switzerland with the IP address 81.17.19.227, where CHE is the local currency and the local language is French. Our records indicate that flibusta.net is privately registered by Whois Privacy Corp.. Flibusta.net has the potential to be earning an estimated $4 USD per day from advertising revenue. If flibusta.net was to be sold it would possibly be worth $3,052 USD (based on the daily revenue potential of the website over a 24 month period). Flibusta.net receives an estimated 1,462 unique visitors every day - a large amount of traffic! This report was last updated 6th August, 2022.

About flibusta.net

Site Preview: flibusta.net flibusta.net
Title:
Description:
Keywords and Tags: entertainment, opinions, politics, religion
Related Terms: flibusta is
Fav Icon:
Age: Over 14 years old
Domain Created: 8th October, 2009
Domain Updated: 1st October, 2020
Domain Expires: 8th October, 2022
Review

Snoop Score

2/5

Valuation

$3,052 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 568,463
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,462
Monthly Visitors: 44,499
Yearly Visitors: 533,630
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $127 USD
Yearly Revenue: $1,521 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: flibusta.net 12
Domain Name: flibusta 8
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.87 seconds
Load Time Comparison: Faster than 80% of sites

PageSpeed Insights

Avg. (All Categories) 66
Performance 96
Accessibility 83
Best Practices 77
SEO 64
PWA 11
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
96

Performance

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

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.6 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).
Largest Contentful Paint — 0.6 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.022
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.6 s
The time taken for the primary content of the page to be rendered.
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://flibusta.net/
http/1.1
0
781.09399974346
333
0
302
text/html
http://flibusta.is/
http/1.1
781.41399985179
1197.1649997868
15127
47680
200
text/html
Document
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
http/1.1
1210.7029999606
2799.5609999634
7823
25949
200
text/css
Stylesheet
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
http/1.1
1211.6769999266
2274.8329997994
49564
130013
200
application/x-javascript
Script
http://flibusta.is/sites/default/files/bluebreeze_logo.png
http/1.1
2285.1579999551
3340.360999573
13452
13172
200
image/png
Image
http://flibusta.is/sites/default/files/pictures/picture-4.png
http/1.1
2801.2429997325
3288.8159998693
12959
12695
200
image/png
Image
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
http/1.1
2817.7669998258
3326.3559998013
19126
18861
200
image/jpeg
Image
http://flibusta.is/sites/default/files/pictures/picture-2215.png
http/1.1
2817.939999979
3195.6619997509
10049
9786
200
image/png
Image
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
http/1.1
2818.0669997819
3074.4929998182
3779
3516
200
image/jpeg
Image
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
http/1.1
2818.3100000024
2967.0329997316
2801
2538
200
image/jpeg
Image
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
http/1.1
2818.4419996105
3185.2549999021
4761
4498
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-header.gif
http/1.1
2826.3009996153
3366.3219995797
809
509
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-primary.gif
http/1.1
2827.3809999228
3366.1479996517
424
146
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-mission.gif
http/1.1
2828.1419998966
3367.3849999905
614
336
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/menu-leaf.gif
http/1.1
2830.248999875
3372.0599999651
453
175
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/mini-comment.png
http/1.1
2830.4019998759
3365.9739997238
495
217
200
image/png
Image
http://flibusta.is/themes/bluebreeze/images/mini-readmore.png
http/1.1
2830.5759998038
3365.725999698
1271
993
200
image/png
Image
data
2835.2969996631
2835.4379995726
0
484
200
image/svg+xml
Image
http://flibusta.is/modules/openid/login-bg.png
http/1.1
2836.9669998065
3365.2689997107
501
223
200
image/png
Image
http://flibusta.is/themes/bluebreeze/images/menu-expanded.gif
http/1.1
2837.7009998076
3401.8669999205
461
183
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/menu-collapsed.gif
http/1.1
2838.6689997278
3401.4059999026
454
176
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-footer.gif
http/1.1
2839.8759998381
3402.441999875
465
187
200
image/gif
Image
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)
1251.73
8.705
2853.52
91.715
2945.252
15.798
3256.235
5.595
3435.222
10.067
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Flibusta.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Flibusta.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Flibusta.net should consider minifying CSS files.
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Flibusta.net should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
5532
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Flibusta.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 27 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
27615
Efficiently encode images — Potential savings of 16 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
18861
16515
Serve images in next-gen formats — Potential savings of 38 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
18861
17664.9
http://flibusta.is/sites/default/files/bluebreeze_logo.png
13172
11245.25
http://flibusta.is/sites/default/files/pictures/picture-4.png
12695
10238.8
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 420 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)
http://flibusta.is/
416.742
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Flibusta.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://flibusta.net/
190
http://flibusta.is/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Flibusta.net 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.
Avoids enormous network payloads — Total size was 142 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
19126
http://flibusta.is/
15127
http://flibusta.is/sites/default/files/bluebreeze_logo.png
13452
http://flibusta.is/sites/default/files/pictures/picture-4.png
12959
http://flibusta.is/sites/default/files/pictures/picture-2215.png
10049
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
7823
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
4761
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
3779
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
2801
Avoids an excessive DOM size — 670 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
670
Maximum DOM Depth
14
Maximum Child Elements
31
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Flibusta.net 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.0 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)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
87.107
25.103
2.107
http://flibusta.is/
78.452
3.964
1.211
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)
Style & Layout
67.487
Rendering
43.238
Other
39.147
Script Evaluation
31.697
Parse HTML & CSS
9.213
Script Parsing & Compilation
3.461
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 — 21 requests • 142 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
21
145721
Image
17
72874
Script
1
49564
Document
1
15127
Stylesheet
1
7823
Other
1
333
Media
0
0
Font
0
0
Third-party
1
333
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.020179750386715
0.00099499539657144
0.00071515294128572
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.

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

Speed Index — 2.0 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Flibusta.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
7823
70
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
110
Serve static assets with an efficient cache policy — 6 resources found
Flibusta.net 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)
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
0
19126
http://flibusta.is/sites/default/files/pictures/picture-4.png
0
12959
http://flibusta.is/sites/default/files/pictures/picture-2215.png
0
10049
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
0
4761
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
0
3779
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
0
2801

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
http://flibusta.is/sites/default/files/pictures/picture-2215.png
http://flibusta.is/sites/default/files/pictures/picture-4.png
http://flibusta.is/sites/default/files/pictures/picture-4.png
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
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 flibusta.net on mobile screens.
83

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of flibusta.net. 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.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[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.
Links 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.
`<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"]`
Flibusta.net may provide assistance to deaf or hearing-impaired users with captions on videos.

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
TOR
I2P

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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.
77

Best Practices

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

Audits

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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.9.0
Drupal
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
http://flibusta.is/sites/default/files/js/jquery.min.map;
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 21 insecure requests 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://flibusta.net/
Allowed
http://flibusta.is/
Allowed
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
Allowed
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
Allowed
http://flibusta.is/sites/default/files/bluebreeze_logo.png
Allowed
http://flibusta.is/sites/default/files/pictures/picture-4.png
Allowed
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
Allowed
http://flibusta.is/sites/default/files/pictures/picture-2215.png
Allowed
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
Allowed
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
Allowed
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-header.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-primary.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-mission.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/menu-leaf.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/mini-comment.png
Allowed
http://flibusta.is/themes/bluebreeze/images/mini-readmore.png
Allowed
http://flibusta.is/modules/openid/login-bg.png
Allowed
http://flibusta.is/themes/bluebreeze/images/menu-expanded.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/menu-collapsed.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-footer.gif
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
5
Medium

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for flibusta.net. 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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.
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 flibusta.net on mobile screens.

Content Best Practices

Document does not have 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.

Crawling and Indexing

Links are not 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 is 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.
Blocking Directive Source

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.
11

PWA

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

PWA Optimized

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.
Provides 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.

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 flibusta.net on mobile screens.
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 89
Accessibility 83
Best Practices 69
SEO 54
PWA 10
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
89

Performance

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

Metrics

Time to Interactive — 2.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 50 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).
Largest Contentful Paint — 2.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.024
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 2.1 s
The time taken for the primary content of the page to be rendered.
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://flibusta.net/
http/1.1
0
835.63299989328
333
0
302
text/html
http://flibusta.is/
http/1.1
836.01199975237
1829.3840000406
15127
47680
200
text/html
Document
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
http/1.1
1840.017999988
4395.0229999609
7823
25949
200
text/css
Stylesheet
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
http/1.1
1840.2459998615
4875.6809998304
49564
130013
200
application/x-javascript
Script
http://flibusta.is/sites/default/files/bluebreeze_logo.png
http/1.1
4396.2480002083
5798.7130000256
13452
13172
200
image/png
Image
http://flibusta.is/sites/default/files/pictures/picture-4.png
http/1.1
4885.1040001027
5170.3429999761
12959
12695
200
image/png
Image
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
http/1.1
4904.1209998541
5398.4779999591
19126
18861
200
image/jpeg
Image
http://flibusta.is/sites/default/files/pictures/picture-2215.png
http/1.1
4904.2299999855
5294.0719998442
10049
9786
200
image/png
Image
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
http/1.1
4904.32399977
5164.4379999489
3779
3516
200
image/jpeg
Image
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
http/1.1
4904.4309998862
5169.0480001271
2801
2538
200
image/jpeg
Image
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
http/1.1
4904.5750000514
5276.0529997759
4761
4498
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-header.gif
http/1.1
4909.2040001415
5899.8879999854
809
509
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-primary.gif
http/1.1
4909.9280000664
5895.180999767
424
146
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-mission.gif
http/1.1
4910.2969998494
5897.0039999112
614
336
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/menu-leaf.gif
http/1.1
4911.1230000854
5896.7989999801
453
175
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/mini-comment.png
http/1.1
4911.3289997913
5899.6779997833
495
217
200
image/png
Image
http://flibusta.is/themes/bluebreeze/images/mini-readmore.png
http/1.1
4911.545000039
5981.8110000342
1271
993
200
image/png
Image
data
4915.3009997681
4915.4179999605
0
484
200
image/svg+xml
Image
http://flibusta.is/modules/openid/login-bg.png
http/1.1
4916.6049999185
5899.1910000332
501
223
200
image/png
Image
http://flibusta.is/themes/bluebreeze/images/menu-expanded.gif
http/1.1
4917.1230001375
5898.5600001179
461
183
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/menu-collapsed.gif
http/1.1
4917.7190000191
5899.4080000557
454
176
200
image/gif
Image
http://flibusta.is/themes/bluebreeze/images/bg-footer.gif
http/1.1
4918.8399999402
5896.5179999359
465
187
200
image/gif
Image
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)
1872.171
6.603
4925.274
80.99
5006.28
10.917
5949.502
6.217
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Flibusta.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Flibusta.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Flibusta.net should consider minifying CSS files.
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Flibusta.net should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
5532
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Flibusta.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
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.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Flibusta.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://flibusta.net/
630
http://flibusta.is/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Flibusta.net 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.
Avoids enormous network payloads — Total size was 142 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
19126
http://flibusta.is/
15127
http://flibusta.is/sites/default/files/bluebreeze_logo.png
13452
http://flibusta.is/sites/default/files/pictures/picture-4.png
12959
http://flibusta.is/sites/default/files/pictures/picture-2215.png
10049
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
7823
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
4761
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
3779
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
2801
Avoids an excessive DOM size — 670 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
670
Maximum DOM Depth
14
Maximum Child Elements
31
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Flibusta.net 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)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
309.948
98.404
12.04
http://flibusta.is/
209.224
9.404
6.244
Unattributable
93.728
11.86
0.664
Minimizes main-thread work — 0.6 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)
Style & Layout
204.856
Other
134.12
Script Evaluation
119.668
Rendering
114.216
Parse HTML & CSS
28.72
Script Parsing & Compilation
18.948
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 — 21 requests • 142 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
21
145721
Image
17
72874
Script
1
49564
Document
1
15127
Stylesheet
1
7823
Other
1
333
Media
0
0
Font
0
0
Third-party
1
333
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.024164296720164
0.00031245719701287
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 — 1 long task 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)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
2070
162
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

First Contentful Paint — 2.1 s
The time taken for the first image or text on the page to be rendered.

Audits

Max Potential First Input Delay — 160 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 670 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Flibusta.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
7823
180
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
330
Reduce unused JavaScript — Potential savings of 27 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
49564
27615
Efficiently encode images — Potential savings of 16 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
18861
16515
Serve images in next-gen formats — Potential savings of 38 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
18861
17664.9
http://flibusta.is/sites/default/files/bluebreeze_logo.png
13172
11245.25
http://flibusta.is/sites/default/files/pictures/picture-4.png
12695
10238.8
Serve static assets with an efficient cache policy — 6 resources found
Flibusta.net 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)
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
0
19126
http://flibusta.is/sites/default/files/pictures/picture-4.png
0
12959
http://flibusta.is/sites/default/files/pictures/picture-2215.png
0
10049
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
0
4761
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
0
3779
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
0
2801
First Contentful Paint (3G) — 3882 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Speed Index — 8.2 s
The time taken for the page contents to be visibly populated.

Other

Reduce initial server response time — Root document took 990 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)
http://flibusta.is/
994.365
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
http://flibusta.is/sites/default/files/pictures/picture-2215.png
http://flibusta.is/sites/default/files/pictures/picture-4.png
http://flibusta.is/sites/default/files/pictures/picture-4.png
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
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 flibusta.net on mobile screens.
83

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of flibusta.net. 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.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[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.
Links 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.
`<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"]`
Flibusta.net may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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.
69

Best Practices

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

Audits

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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.9.0
Drupal
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
http://flibusta.is/sites/default/files/js/jquery.min.map;
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 21 insecure requests 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://flibusta.net/
Allowed
http://flibusta.is/
Allowed
http://flibusta.is/sites/default/files/css/css_541b6da58ae4dff17f932324504056f9.css
Allowed
http://flibusta.is/sites/default/files/js/js_65bd89c41ff1e065c43cc27e23c28553.js
Allowed
http://flibusta.is/sites/default/files/bluebreeze_logo.png
Allowed
http://flibusta.is/sites/default/files/pictures/picture-4.png
Allowed
http://flibusta.is/sites/default/files/pictures/picture-8052.jpg
Allowed
http://flibusta.is/sites/default/files/pictures/picture-2215.png
Allowed
http://flibusta.is/sites/default/files/pictures/picture-37400.jpg
Allowed
http://flibusta.is/sites/default/files/pictures/picture-7176.jpg
Allowed
http://flibusta.is/sites/default/files/pictures/picture-124185.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-header.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-primary.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-mission.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/menu-leaf.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/mini-comment.png
Allowed
http://flibusta.is/themes/bluebreeze/images/mini-readmore.png
Allowed
http://flibusta.is/modules/openid/login-bg.png
Allowed
http://flibusta.is/themes/bluebreeze/images/menu-expanded.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/menu-collapsed.gif
Allowed
http://flibusta.is/themes/bluebreeze/images/bg-footer.gif
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
5
Medium

Audits

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
http://flibusta.is/sites/default/files/bluebreeze_logo.png
106 x 102
106 x 102
212 x 204
http://flibusta.is/sites/default/files/pictures/picture-4.png
70 x 70
70 x 70
140 x 140

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for flibusta.net. 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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.
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 flibusta.net 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

Document does not have 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.

Crawling and Indexing

Links are not 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 is 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.
Blocking Directive Source

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.
10

PWA

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

PWA Optimized

Provides 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.

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 flibusta.net on mobile screens.
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: 81.17.19.227
Continent: Europe
Country: Switzerland
Switzerland Flag
Region:
City:
Longitude: 8.1551
Latitude: 47.1449
Currencies: CHE
CHF
CHW
Languages: French
Swiss German
Italian
Romansh

Web Hosting Provider

Registration

Domain Registrant

Private Registration: Yes
Name: Domain Admin
Organization: Whois Privacy Corp.
Country: BS
City: Nassau
State: New Providence
Post Code:
Email: flibusta.net-owner@customers.whoisprivacycorp.com
Phone: +1.5163872248
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Internet Domain Service BS Corp. 172.67.37.162
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 92/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: flibusta.is
Issued By: R3
Valid From: 6th October, 2021
Valid To: 4th January, 2022
Subject: CN = flibusta.is
Hash: ccf0051b
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04FE54BED938014B9F5D1B5E735B843BBF05
Serial Number (Hex): 04FE54BED938014B9F5D1B5E735B843BBF05
Valid From: 6th October, 2024
Valid To: 4th January, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Oct 6 04:53:20.290 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:8C:26:B1:4D:AE:8C:8F:34:0E:2E:B3:
E5:38:9F:5C:50:80:F2:A7:11:08:55:4B:76:12:5D:51:
70:0D:C0:C0:88:02:21:00:C5:FF:9C:E7:AD:8D:92:A3:
8D:62:47:8F:F7:19:11:FE:10:02:B2:81:14:3C:F8:45:
86:33:EE:E2:87:3C:74:8E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Oct 6 04:53:20.318 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:CA:AB:C4:2D:1A:07:74:DC:FF:B3:C0:
A1:E3:CD:A1:9D:D0:37:02:83:98:D2:32:9F:42:91:63:
5E:9C:39:55:84:02:20:12:C7:6A:3C:3D:9A:2A:71:D4:
9F:8B:B8:65:E3:03:4C:C1:85:F2:60:98:49:34:98:B4:
58:DD:E3:A3:2C:82:32
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:flibusta.is
DNS:*.flibusta.is
Technical

DNS Lookup

A Records

Host IP Address Class TTL
flibusta.net. 81.17.19.227 IN 14440

NS Records

Host Nameserver Class TTL
flibusta.net. dns1.orangewebsite.com. IN 21600
flibusta.net. dns2.orangewebsite.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
flibusta.net. dns1.orangewebsite.com. reports.orangewebsite.com. 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html; charset=utf-8
Cache-Control: public, max-age=600
Expires: 11th March, 1984
Date: 7th December, 2021
Last-Modified: 7th December, 2021
ETag: W/"1638899508"
Vary: Accept-Encoding
Age: 548
Connection: keep-alive

Whois Lookup

Created: 8th October, 2009
Changed: 1st October, 2020
Expires: 8th October, 2022
Registrar: Internet Domain Service BS Corp.
Status: clientTransferProhibited
Nameservers: dns1.orangewebsite.com
dns2.orangewebsite.com
Owner Name: Domain Admin
Owner Organization: Whois Privacy Corp.
Owner Street: Ocean Centre, Montagu Foreshore, East Bay Street
Owner City: Nassau
Owner State: New Providence
Owner Country: BS
Owner Phone: +1.5163872248
Owner Email: flibusta.net-owner@customers.whoisprivacycorp.com
Admin Name: Domain Admin
Admin Organization: Whois Privacy Corp.
Admin Street: Ocean Centre, Montagu Foreshore, East Bay Street
Admin City: Nassau
Admin State: New Providence
Admin Country: BS
Admin Phone: +1.5163872248
Admin Email: flibusta.net-admin@customers.whoisprivacycorp.com
Tech Name: Domain Admin
Tech Organization: Whois Privacy Corp.
Tech Street: Ocean Centre, Montagu Foreshore, East Bay Street
Tech City: Nassau
Tech State: New Providence
Tech Country: BS
Tech Phone: +1.5163872248
Tech Email: flibusta.net-tech@customers.whoisprivacycorp.com
Full Whois: Domain Name: FLIBUSTA.NET
Registry Domain ID: 1571672958_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.internet.bs
Registrar URL: http://www.internetbs.net
Updated Date: 2020-10-01T04:40:59Z
Creation Date: 2009-10-08T20:43:40Z
Registrar Registration Expiration Date: 2022-10-08T20:43:40Z
Registrar: Internet Domain Service BS Corp.
Registrar IANA ID: 2487
Registrar Abuse Contact Email: abuse@internet.bs
Registrar Abuse Contact Phone: +1.5163015301
Reseller:
Domain Status: clientTransferProhibited - http://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not disclosed
Registrant Name: Domain Admin
Registrant Organization: Whois Privacy Corp.
Registrant Street: Ocean Centre, Montagu Foreshore, East Bay Street
Registrant City: Nassau
Registrant State/Province: New Providence
Registrant Postal Code:
Registrant Country: BS
Registrant Phone: +1.5163872248
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: flibusta.net-owner@customers.whoisprivacycorp.com
Registry Admin ID: Not disclosed
Admin Name: Domain Admin
Admin Organization: Whois Privacy Corp.
Admin Street: Ocean Centre, Montagu Foreshore, East Bay Street
Admin City: Nassau
Admin State/Province: New Providence
Admin Postal Code:
Admin Country: BS
Admin Phone: +1.5163872248
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: flibusta.net-admin@customers.whoisprivacycorp.com
Registry Tech ID: Not disclosed
Tech Name: Domain Admin
Tech Organization: Whois Privacy Corp.
Tech Street: Ocean Centre, Montagu Foreshore, East Bay Street
Tech City: Nassau
Tech State/Province: New Providence
Tech Postal Code:
Tech Country: BS
Tech Phone: +1.5163872248
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: flibusta.net-tech@customers.whoisprivacycorp.com
Name Server: dns1.orangewebsite.com
Name Server: dns2.orangewebsite.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-08-06T19:18:10Z <<<


For more information on Whois status codes, please visit https://icann.org/epp


Nameservers

Name IP Address
dns1.orangewebsite.com 82.221.128.185
dns2.orangewebsite.com 82.221.128.186
Related

Subdomains

Domain Subdomain
mobi
proxy

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$570 USD
0/5
$278 USD

Sites hosted on the same IP address