rarbgaccess.org

rarbgaccess.org is SSL secured

Free website and domain report on rarbgaccess.org

Last Updated: 29th June, 2022 Update Now
Overview

Snoop Summary for rarbgaccess.org

This is a free and comprehensive report about rarbgaccess.org. The domain rarbgaccess.org is currently hosted on a server located in United States with the IP address 104.31.16.9, where the local currency is USD and English is the local language. Rarbgaccess.org is expected to earn an estimated $411 USD per day from advertising revenue. The sale of rarbgaccess.org would possibly be worth $299,785 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Rarbgaccess.org receives an estimated 97,106 unique visitors every day - a massive amount of traffic! This report was last updated 29th June, 2022.

About rarbgaccess.org

Site Preview: rarbgaccess.org rarbgaccess.org
Title: Just a moment...
Description:
Keywords and Tags: potential illegal software
Related Terms:
Fav Icon:
Age: Over 7 years old
Domain Created: 12th September, 2017
Domain Updated: 7th October, 2021
Domain Expires: 12th September, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$299,785 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 13,638
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: 97,106
Monthly Visitors: 2,955,601
Yearly Visitors: 35,443,690
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $411 USD
Monthly Revenue: $12,499 USD
Yearly Revenue: $149,888 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: rarbgaccess.org 15
Domain Name: rarbgaccess 11
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 56
Performance 94
Accessibility 51
Best Practices 69
SEO 64
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://rarbgaccess.org/index80.php
Updated: 25th January, 2022

1.32 seconds
First Contentful Paint (FCP)
83%
10%
7%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
94

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for rarbgaccess.org. 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.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
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.9 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 20 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://rarbgaccess.org/
http/1.1
0
129.66899992898
748
0
301
text/html
http://rarbgaccess.org/index80.php
http/1.1
130.00100012869
369.97999995947
6522
17246
200
text/html
Document
https://dyncdn.me/static/20/css/styles_v38.css?c=0125
h2
381.88400026411
477.61800000444
4326
14688
200
text/css
Stylesheet
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
http/1.1
382.04100029543
416.27100016922
14384
39479
200
text/javascript
Script
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
h2
382.366000209
574.41999996081
39167
95957
200
application/javascript
Script
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
h2
385.790000204
481.25200020149
2635
2354
200
image/png
Image
https://dyncdn.me/static/20/img/utorrent3.png
h2
386.0850003548
480.39099993184
881
601
200
image/png
Image
https://dyncdn.me/static/20/img/bookmark2.png
h2
386.35100005195
573.08500027284
959
679
200
image/png
Image
https://dyncdn.me/static/20/img/ff2.png
h2
386.4440000616
480.85500020534
1196
916
200
image/png
Image
https://dyncdn.me/static/20/js/showads.js
h2
385.41000010446
572.80099997297
308
17
200
application/javascript
Script
https://dyncdn.me/static/20/js/expla95.js
h2
385.61600027606
569.6459999308
13274
40417
200
application/javascript
Script
https://dyncdn.me/static/20/img/bknd_body.jpg
h2
481.17300029844
644.40200012177
2844
2562
200
image/jpeg
Image
http://statsy.net/a.php?ref=&res=600x800&ab=2&_=1643110874205
http/1.1
639.44600010291
818.19600006565
614
18
200
text/html
XHR
http://rarbgaccess.org/ajax_news_v2.php?mode=multi&ssl=1
http/1.1
644.29800026119
847.49100031331
2341
6534
200
text/html
XHR
https://dyncdn.me/static/20/img/loading.gif
h2
645.00200003386
740.32500013709
11102
10819
200
image/gif
Image
https://imagecurl.com/images/28794347650858572794_thumb.jpg
h2
852.1030000411
877.30300007388
25756
24835
200
image/jpeg
Image
https://imagecurl.com/images/52925450958837082968_thumb.jpg
h2
852.32100030407
873.19900002331
23602
22684
200
image/jpeg
Image
https://imagecurl.com/images/80693367402661092034_thumb.jpg
h2
852.63800015673
878.11199994758
23654
22734
200
image/jpeg
Image
https://imagecurl.com/images/43560711672985725227_thumb.jpg
h2
852.89500001818
893.81700009108
56020
55102
200
image/jpeg
Image
https://imagecurl.com/images/35841184033357467014_thumb.jpg
h2
853.07600023225
874.78000018746
15293
14380
200
image/jpeg
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)
410.586
7.314
619.031
18.405
637.446
16.135
654.901
28.55
885.641
5.516
891.195
6.301
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

Eliminate render-blocking resources — Potential savings of 40 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rarbgaccess.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://dyncdn.me/static/20/css/styles_v38.css?c=0125
4326
230
Properly size images — Potential savings of 126 KiB
Images can slow down the page's load time. Rarbgaccess.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://imagecurl.com/images/43560711672985725227_thumb.jpg
55102
50749
https://imagecurl.com/images/28794347650858572794_thumb.jpg
24835
22875
https://imagecurl.com/images/80693367402661092034_thumb.jpg
22734
20940
https://imagecurl.com/images/52925450958837082968_thumb.jpg
22684
20889
https://imagecurl.com/images/35841184033357467014_thumb.jpg
14380
13244
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rarbgaccess.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rarbgaccess.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rarbgaccess.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rarbgaccess.org 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 24 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://dyncdn.me/static/20/js/jquery-1.11.3.min.js
39167
24433
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 41 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)
https://imagecurl.com/images/43560711672985725227_thumb.jpg
55102
15401.4
https://imagecurl.com/images/28794347650858572794_thumb.jpg
24835
9455.3
https://imagecurl.com/images/80693367402661092034_thumb.jpg
22734
9122.35
https://imagecurl.com/images/52925450958837082968_thumb.jpg
22684
8343.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 240 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://rarbgaccess.org/index80.php
240.971
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Rarbgaccess.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://rarbgaccess.org/
190
http://rarbgaccess.org/index80.php
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rarbgaccess.org 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 240 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://imagecurl.com/images/43560711672985725227_thumb.jpg
56020
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
39167
https://imagecurl.com/images/28794347650858572794_thumb.jpg
25756
https://imagecurl.com/images/80693367402661092034_thumb.jpg
23654
https://imagecurl.com/images/52925450958837082968_thumb.jpg
23602
https://imagecurl.com/images/35841184033357467014_thumb.jpg
15293
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
14384
https://dyncdn.me/static/20/js/expla95.js
13274
https://dyncdn.me/static/20/img/loading.gif
11102
http://rarbgaccess.org/index80.php
6522
Uses efficient cache policy on static assets — 16 resources found
Rarbgaccess.org 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://imagecurl.com/images/43560711672985725227_thumb.jpg
604800000
56020
https://imagecurl.com/images/28794347650858572794_thumb.jpg
604800000
25756
https://imagecurl.com/images/80693367402661092034_thumb.jpg
604800000
23654
https://imagecurl.com/images/52925450958837082968_thumb.jpg
604800000
23602
https://imagecurl.com/images/35841184033357467014_thumb.jpg
604800000
15293
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
604800000
14384
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
864000000
39167
https://dyncdn.me/static/20/js/expla95.js
864000000
13274
https://dyncdn.me/static/20/img/loading.gif
864000000
11102
https://dyncdn.me/static/20/css/styles_v38.css?c=0125
864000000
4326
https://dyncdn.me/static/20/img/bknd_body.jpg
864000000
2844
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
864000000
2635
https://dyncdn.me/static/20/img/ff2.png
864000000
1196
https://dyncdn.me/static/20/img/bookmark2.png
864000000
959
https://dyncdn.me/static/20/img/utorrent3.png
864000000
881
https://dyncdn.me/static/20/js/showads.js
864000000
308
Avoids an excessive DOM size — 271 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
271
Maximum DOM Depth
25
Maximum Child Elements
22
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rarbgaccess.org 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://rarbgaccess.org/index80.php
60.532
10.006
2.85
Minimizes main-thread work — 0.1 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
59.258
Other
32.363
Style & Layout
23.246
Rendering
13.668
Parse HTML & CSS
7.624
Script Parsing & Compilation
6.121
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 — 20 requests • 240 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
20
245626
Image
11
163942
Script
4
67133
Document
1
6522
Stylesheet
1
4326
Other
3
3703
Media
0
0
Font
0
0
Third-party
16
221631
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.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.15981278998135
0.010911670608051
0.0075542334978815
0.0066129430337111
0.0039170099618645
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

Cumulative Layout Shift — 0.189
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

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
https://imagecurl.com/images/43560711672985725227_thumb.jpg
https://imagecurl.com/images/28794347650858572794_thumb.jpg
https://imagecurl.com/images/80693367402661092034_thumb.jpg
https://imagecurl.com/images/52925450958837082968_thumb.jpg
https://imagecurl.com/images/35841184033357467014_thumb.jpg
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
https://dyncdn.me/static/20/img/utorrent3.png
https://dyncdn.me/static/20/img/bookmark2.png
https://dyncdn.me/static/20/img/ff2.png
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 rarbgaccess.org on mobile screens.
51

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rarbgaccess.org. 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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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.

Contrast

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

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 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"]`
Rarbgaccess.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
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.
69

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that rarbgaccess.org 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.11.3
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 5 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://rarbgaccess.org/
Allowed
http://rarbgaccess.org/index80.php
Allowed
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
Allowed
http://statsy.net/a.php?ref=&res=600x800&ab=2&_=1643110874205
Allowed
http://rarbgaccess.org/ajax_news_v2.php?mode=multi&ssl=1
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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
4
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.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
The Notification API may no longer be used from insecure origins. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
64

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rarbgaccess.org. 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.
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.
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 rarbgaccess.org 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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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.

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

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 rarbgaccess.org. 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.

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 rarbgaccess.org 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) 49
Performance 80
Accessibility 51
Best Practices 62
SEO 54
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://rarbgaccess.org/index80.php
Updated: 25th January, 2022

1.56 seconds
First Contentful Paint (FCP)
80%
13%
7%

0.23 seconds
First Input Delay (FID)
27%
70%
3%

Simulate loading on mobile
80

Performance

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

Metrics

Time to Interactive — 2.1 s
The time taken for the page to become fully interactive.
Speed Index — 2.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 10 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).

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.0 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://rarbgaccess.org/
http/1.1
0
218.13299972564
743
0
301
text/html
http://rarbgaccess.org/index80.php
http/1.1
218.62499974668
432.61999962851
6577
17322
200
text/html
Document
https://dyncdn.me/static/20/css/styles_v38.css?c=0125
h2
446.0719996132
542.41799982265
4326
14688
200
text/css
Stylesheet
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
http/1.1
446.38899993151
483.62799966708
14884
40841
200
text/javascript
Script
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
h2
446.76099997014
638.06799985468
39167
95957
200
application/javascript
Script
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
h2
450.09899977595
546.0039996542
2635
2354
200
image/png
Image
https://dyncdn.me/static/20/img/utorrent3.png
h2
450.27599995956
546.34299967438
881
601
200
image/png
Image
https://dyncdn.me/static/20/img/bookmark2.png
h2
450.63499966636
641.41599973664
959
679
200
image/png
Image
https://dyncdn.me/static/20/img/ff2.png
h2
450.92999981716
637.5569999218
1196
916
200
image/png
Image
https://dyncdn.me/static/20/js/showads.js
h2
449.68499988317
544.9659996666
308
17
200
application/javascript
Script
https://dyncdn.me/static/20/js/expla95.js
h2
449.92599962279
639.23099962994
13274
40417
200
application/javascript
Script
https://dyncdn.me/static/20/img/bknd_body.jpg
h2
547.74899967015
642.76599977165
2844
2562
200
image/jpeg
Image
http://statsy.net/a.php?ref=&res=640x360&ab=2&_=1643110887702
http/1.1
712.10499992594
803.45899984241
614
18
200
text/html
XHR
http://rarbgaccess.org/ajax_news_v2.php?mode=multi&ssl=1
http/1.1
717.65299979597
968.73299963772
2345
6534
200
text/html
XHR
https://dyncdn.me/static/20/img/loading.gif
h2
719.4789997302
814.56899968907
11102
10819
200
image/gif
Image
https://imagecurl.com/images/28794347650858572794_thumb.jpg
h2
973.82699977607
1003.8549997844
25755
24835
200
image/jpeg
Image
https://imagecurl.com/images/52925450958837082968_thumb.jpg
h2
974.06899975613
1039.5259996876
23602
22684
200
image/jpeg
Image
https://imagecurl.com/images/80693367402661092034_thumb.jpg
h2
974.41799985245
1000.6479998119
23646
22734
200
image/jpeg
Image
https://imagecurl.com/images/43560711672985725227_thumb.jpg
h2
974.86600000411
1015.3119997121
56016
55102
200
image/jpeg
Image
https://imagecurl.com/images/35841184033357467014_thumb.jpg
h2
975.02899961546
1016.1799998023
15307
14380
200
image/jpeg
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)
479.001
8.24
688.867
23.172
712.233
14.504
732.242
30.055
1012.422
5.768
1018.211
10.585
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

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rarbgaccess.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rarbgaccess.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rarbgaccess.org should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rarbgaccess.org 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 210 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://rarbgaccess.org/index80.php
214.982
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Rarbgaccess.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://rarbgaccess.org/
630
http://rarbgaccess.org/index80.php
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rarbgaccess.org 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 240 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://imagecurl.com/images/43560711672985725227_thumb.jpg
56016
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
39167
https://imagecurl.com/images/28794347650858572794_thumb.jpg
25755
https://imagecurl.com/images/80693367402661092034_thumb.jpg
23646
https://imagecurl.com/images/52925450958837082968_thumb.jpg
23602
https://imagecurl.com/images/35841184033357467014_thumb.jpg
15307
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
14884
https://dyncdn.me/static/20/js/expla95.js
13274
https://dyncdn.me/static/20/img/loading.gif
11102
http://rarbgaccess.org/index80.php
6577
Uses efficient cache policy on static assets — 16 resources found
Rarbgaccess.org 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://imagecurl.com/images/43560711672985725227_thumb.jpg
604800000
56016
https://imagecurl.com/images/28794347650858572794_thumb.jpg
604800000
25755
https://imagecurl.com/images/80693367402661092034_thumb.jpg
604800000
23646
https://imagecurl.com/images/52925450958837082968_thumb.jpg
604800000
23602
https://imagecurl.com/images/35841184033357467014_thumb.jpg
604800000
15307
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
604800000
14884
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
864000000
39167
https://dyncdn.me/static/20/js/expla95.js
864000000
13274
https://dyncdn.me/static/20/img/loading.gif
864000000
11102
https://dyncdn.me/static/20/css/styles_v38.css?c=0125
864000000
4326
https://dyncdn.me/static/20/img/bknd_body.jpg
864000000
2844
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
864000000
2635
https://dyncdn.me/static/20/img/ff2.png
864000000
1196
https://dyncdn.me/static/20/img/bookmark2.png
864000000
959
https://dyncdn.me/static/20/img/utorrent3.png
864000000
881
https://dyncdn.me/static/20/js/showads.js
864000000
308
Avoids an excessive DOM size — 271 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
271
Maximum DOM Depth
25
Maximum Child Elements
22
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rarbgaccess.org 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)
http://rarbgaccess.org/index80.php
302.288
58.852
14.364
https://dyncdn.me/static/20/js/jquery-1.11.3.min.js
132.98
98.9
7.72
Unattributable
100.892
16.448
0.824
https://dyncdn.me/static/20/js/expla95.js
94.076
90.044
3.18
Minimizes main-thread work — 0.7 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
273.068
Other
143.536
Style & Layout
106.48
Rendering
62.104
Parse HTML & CSS
35.972
Script Parsing & Compilation
30.196
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 — 20 requests • 240 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
20
246181
Image
11
163943
Script
4
67633
Document
1
6577
Stylesheet
1
4326
Other
3
3702
Media
0
0
Font
0
0
Third-party
16
221632
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.77117585699014
0.019246990464109
0.012831326976073
0.011288332262305
0.0064156634880364
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://dyncdn.me/static/20/js/jquery-1.11.3.min.js
1890
93
https://dyncdn.me/static/20/js/showads.js
2190
60
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.0 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.7 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rarbgaccess.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://dyncdn.me/static/20/css/styles_v38.css?c=0125
4326
780
Properly size images — Potential savings of 62 KiB
Images can slow down the page's load time. Rarbgaccess.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://imagecurl.com/images/43560711672985725227_thumb.jpg
55102
25108
https://imagecurl.com/images/28794347650858572794_thumb.jpg
24835
11332
https://imagecurl.com/images/80693367402661092034_thumb.jpg
22734
10373
https://imagecurl.com/images/52925450958837082968_thumb.jpg
22684
10316
https://imagecurl.com/images/35841184033357467014_thumb.jpg
14380
6552
Reduce unused JavaScript — Potential savings of 24 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://dyncdn.me/static/20/js/jquery-1.11.3.min.js
39167
24433
Serve images in next-gen formats — Potential savings of 41 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)
https://imagecurl.com/images/43560711672985725227_thumb.jpg
55102
15401.4
https://imagecurl.com/images/28794347650858572794_thumb.jpg
24835
9455.3
https://imagecurl.com/images/80693367402661092034_thumb.jpg
22734
9122.35
https://imagecurl.com/images/52925450958837082968_thumb.jpg
22684
8343.8
First Contentful Paint (3G) — 3783 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Cumulative Layout Shift — 0.823
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

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
https://imagecurl.com/images/43560711672985725227_thumb.jpg
https://imagecurl.com/images/28794347650858572794_thumb.jpg
https://imagecurl.com/images/80693367402661092034_thumb.jpg
https://imagecurl.com/images/52925450958837082968_thumb.jpg
https://imagecurl.com/images/35841184033357467014_thumb.jpg
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
https://dyncdn.me/static/20/img/utorrent3.png
https://dyncdn.me/static/20/img/bookmark2.png
https://dyncdn.me/static/20/img/ff2.png
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 rarbgaccess.org on mobile screens.
51

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rarbgaccess.org. 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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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.

Contrast

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

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 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"]`
Rarbgaccess.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
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.
62

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that rarbgaccess.org 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.11.3
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 5 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://rarbgaccess.org/
Allowed
http://rarbgaccess.org/index80.php
Allowed
http://rarbgaccess.org/cdn-cgi/challenge-platform/h/b/scripts/invisible.js
Allowed
http://statsy.net/a.php?ref=&res=640x360&ab=2&_=1643110887702
Allowed
http://rarbgaccess.org/ajax_news_v2.php?mode=multi&ssl=1
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 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
4
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
https://dyncdn.me/static/20/img/logo_dark_nodomain2_optimized.png
188 x 70
188 x 70
376 x 140
https://dyncdn.me/static/20/img/bookmark2.png
16 x 16
16 x 16
32 x 32
https://dyncdn.me/static/20/img/ff2.png
16 x 16
16 x 16
32 x 32
https://dyncdn.me/static/20/img/utorrent3.png
16 x 16
16 x 16
32 x 32

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

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
The Notification API may no longer be used from insecure origins. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
54

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rarbgaccess.org. 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.
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.
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 rarbgaccess.org 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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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.

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

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 rarbgaccess.org. This includes details about web app manifests.

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 rarbgaccess.org 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: 104.31.16.9
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
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

Name IP Address
MainReg INC. 172.67.143.183
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 4th July, 2021
Valid To: 3rd July, 2022
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 10555011014439248655770784061358746919
Serial Number (Hex): 07F0D238B20BCFCE28396A909AAE2D27
Valid From: 4th July, 2024
Valid To: 3rd July, 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.23.140.1.2.2
CPS: http://www.digicert.com/CPS

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 : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jul 4 15:16:28.294 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A2:9A:4F:8F:B0:10:69:1C:C8:70:D6:
D2:F6:90:A4:02:2C:9E:A2:BB:54:DC:B8:79:2C:9D:55:
5E:10:0D:47:C7:02:21:00:FC:76:DA:CD:28:9B:EB:4F:
EF:31:D5:13:B2:85:DB:01:43:35:A4:BB:DB:96:E2:E6:
47:D4:1E:C2:D1:AA:D6:E0
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 : Jul 4 15:16:28.368 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:5D:D4:79:5C:22:F9:57:C1:97:84:81:52:
0B:00:7A:2E:5E:F5:F3:C4:E1:F5:CE:9C:77:01:E2:B1:
9A:02:B7:97:02:21:00:AC:87:8F:C9:18:C5:08:7B:D6:
C0:56:E0:F7:55:84:33:DD:89:35:E1:1B:BA:BD:20:CA:
0F:97:01:96:DE:08:EA
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Jul 4 15:16:28.386 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:32:30:3D:D9:75:51:CE:4C:B0:98:36:96:
13:A8:2D:4E:12:28:8F:DB:1F:6E:29:C3:42:AD:06:83:
CD:D5:E3:96:02:20:29:14:95:24:DF:E1:86:C2:9E:A6:
3E:BC:C1:CA:6A:04:53:67:D7:17:51:98:DF:D9:7E:F3:
14:36:92:92:A7:43
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.rarbgaccess.org
DNS:rarbgaccess.org
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 503 Service Temporarily Unavailable
Date: 25th January, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: 1st January, 1970
Server: cloudflare
Connection: close
X-Frame-Options: SAMEORIGIN
Permissions-Policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=uOU0FsKHBYoOgkjvJco%2Bso3NH9QbIqOTHZO2W1pRyc6mxW7SSEWk%2FO8pPq5busV0GLdXi%2BON6WB2Mi3jg1%2Fb1WJdPAFTp0SFcd63ebz%2B1FB6ESSbd%2BpSZ3HTrtp9aYwCa%2Fo%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 6d31399faea132fa-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 12th September, 2017
Changed: 7th October, 2021
Expires: 12th September, 2022
Registrar: MainReg INC.
Status: ok
Nameservers: lola.ns.cloudflare.com
tim.ns.cloudflare.com
Owner Name: Not Disclosed Not Disclosed
Owner Organization: RRD INVEST D.D.
Owner Street: Not Disclosed
Owner Post Code: Not Disclosed
Owner City: Not Disclosed
Owner State: Sarajevo
Owner Country: BA
Owner Phone: Not Disclosed
Owner Email: webproxy@whoisprotection.domains
Admin Name: Not Disclosed Not Disclosed
Admin Street: Not Disclosed
Admin Post Code: Not Disclosed
Admin City: Not Disclosed
Admin State: Not Disclosed
Admin Country: Not Disclosed
Admin Phone: Not Disclosed
Admin Email: webproxy@whoisprotection.domains
Tech Name: Not Disclosed Not Disclosed
Tech Street: Not Disclosed
Tech Post Code: Not Disclosed
Tech City: Not Disclosed
Tech State: Not Disclosed
Tech Country: Not Disclosed
Tech Phone: Not Disclosed
Tech Email: webproxy@whoisprotection.domains
Full Whois:
Domain Name: rarbgaccess.org
Registry Domain ID: D402200000004467078-LROR
Registrar WHOIS Server: whois.mainreg.com
Registrar URL: http://www.mainreg.com
Updated Date: 2021-07-10T00:00:00Z
Creation Date: 2017-12-09T00:00:00Z
Registrar Registration Expiration Date: 2022-12-09T00:00:00Z
Registrar: MainReg INC.
Registrar IANA ID: 1917
Registrar Abuse Contact Email: complain@mainreg.com
Registrar Abuse Contact Phone: +359 888 832133
Reseller:
Domain Status: ok https://www.icann.org/epp#ok
Registry Registrant ID: Not Disclosed
Registrant Name: Not Disclosed Not Disclosed
Registrant Organization: RRD INVEST D.D.
Registrant Street: Not Disclosed
Registrant City: Not Disclosed
Registrant State/Province: Sarajevo
Registrant Postal Code: Not Disclosed
Registrant Country: BA
Registrant Phone: Not Disclosed
Registrant Phone Ext: Not Disclosed
Registrant Fax: Not Disclosed
Registrant Fax Ext: Not Disclosed
Registrant Email: webproxy@whoisprotection.domains
Registry Admin ID: Not Disclosed
Admin Name: Not Disclosed Not Disclosed
Admin Organization:
Admin Street: Not Disclosed
Admin City: Not Disclosed
Admin State/Province: Not Disclosed
Admin Postal Code: Not Disclosed
Admin Country: Not Disclosed
Admin Phone: Not Disclosed
Admin Phone Ext: Not Disclosed
Admin Fax: Not Disclosed
Admin Fax Ext: Not Disclosed
Admin Email: webproxy@whoisprotection.domains
Registry Tech ID: Not Disclosed
Tech Name: Not Disclosed Not Disclosed
Tech Organization:
Tech Street: Not Disclosed
Tech City: Not Disclosed
Tech State/Province: Not Disclosed
Tech Postal Code: Not Disclosed
Tech Country: Not Disclosed
Tech Phone: Not Disclosed
Tech Phone Ext: Not Disclosed
Tech Fax: Not Disclosed
Tech Fax Ext: Not Disclosed
Tech Email: webproxy@whoisprotection.domains
Name Server: lola.ns.cloudflare.com
Name Server: tim.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-01-25T00:00:00Z <<<

Nameservers

Name IP Address
lola.ns.cloudflare.com 108.162.192.132
tim.ns.cloudflare.com 108.162.193.145
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$45,068,680 USD 5/5