xpassd.co

xpassd.co is SSL secured

Free website and domain report on xpassd.co

Last Updated: 1st February, 2025
Overview

Snoop Summary for xpassd.co

This is a free and comprehensive report about xpassd.co. Xpassd.co is hosted in United States on a server with an IP address of 74.63.241.29, where USD is the local currency and the local language is English. Our records indicate that xpassd.co is privately registered by Privacy service provided by Withheld for Privacy ehf. Xpassd.co has the potential to be earning an estimated $1 USD per day from advertising revenue. If xpassd.co was to be sold it would possibly be worth $885 USD (based on the daily revenue potential of the website over a 24 month period). Xpassd.co receives an estimated 420 unique visitors every day - a decent amount of traffic! This report was last updated 1st February, 2025.

About xpassd.co

Site Preview: xpassd.co xpassd.co
Title: Xpassd
Description: Where Free xxx Passwords Updated Daily
Keywords and Tags: blogs, pups, wiki
Related Terms: daily updated, passwords, pornportal passwords, presale passwords, updated, updated daily
Fav Icon:
Age: Over 7 years old
Domain Created: 8th October, 2017
Domain Updated: 17th October, 2024
Domain Expires: 7th October, 2025
Review

Snoop Score

1/5

Valuation

$885 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,492,125
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: 420
Monthly Visitors: 12,796
Yearly Visitors: 153,453
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $36 USD
Yearly Revenue: $437 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: xpassd.co 9
Domain Name: xpassd 6
Extension (TLD): co 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 79
Performance 93
Accessibility 92
Best Practices 83
SEO 92
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://xpassd.net/
Updated: 29th January, 2023

1.41 seconds
First Contentful Paint (FCP)
86%
10%
4%

0.01 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
93

Performance

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

Metrics

Time to Interactive — 1.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.009
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
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://xpassd.co/
http/1.1
0
68.48099999479
717
0
301
text/plain
https://xpassd.co/
http/1.1
68.838000006508
333.09000000008
747
0
301
text/html
https://xpassd.net/
h2
333.44200000283
968.2830000238
12338
76219
200
text/html
Document
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
h2
979.87700000522
1019.3030000082
34296
187631
200
text/css
Stylesheet
https://xpassd.net/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1
h2
980.89800000889
1067.5610000035
13325
94889
200
text/css
Stylesheet
https://xpassd.net/wp-content/themes/veen/assets/dist/plugins.min.css?ver=2.2.0
h2
981.02900001686
1007.6390000177
6395
28498
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Josefin+Sans%3A400%2C600%2C700%7CNunito%3A400%2C400i%2C600%2C700%2C700i&subset=latin%2Clatin-ext&display=swap
h2
981.16300001857
999.05800001579
1470
11825
200
text/css
Stylesheet
https://estudiopatagon.com/themes/wordpress/veenv2/wp-content/themes/veen/assets/images/transparent.gif
h2
989.91600002046
1082.2050000133
383
42
200
image/gif
Image
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
h2
989.57400000654
1115.947000013
32715
89684
200
application/javascript
Script
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
h2
990.17299999832
1107.565000013
55044
190847
200
application/javascript
Script
data
988.58900001505
988.78000001423
0
452
200
text/javascript
Script
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
h2
1041.2270000088
1115.1670000108
128823
128058
200
image/gif
Image
https://xpassd.net/wp-content/themes/veen/assets/images/urban-sprite-op.png
h2
1042.574000021
1075.3740000073
32469
31666
200
image/png
Image
https://xpassd.net/wp-content/litespeed/avatar/afcaf7e3bb2f8b22b8ecb875ce77aea3.jpg?ver=1674539657
h2
1043.0360000173
1528.7390000012
2272
1528
200
image/jpeg
Image
https://fonts.gstatic.com/s/nunito/v25/XRXV3I6Li01BKofINeaBTMnFcQ.woff2
h2
1055.0820000062
1060.4910000111
36660
35848
200
font/woff2
Font
https://fonts.gstatic.com/s/josefinsans/v25/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
h2
1055.434000009
1060.942000011
27424
26612
200
font/woff2
Font
https://xpassd.net/wp-content/themes/veen/assets/fonts/fontawesome-webfont.woff2
h2
1055.6440000073
1142.8510000114
77916
77160
200
font/woff2
Font
https://xpassd.net/wp-json/wp-statistics/v2/hit?wp_statistics_hit_rest=yes&exclusion_match=no&exclusion_reason&track_all=1&current_page_type=home&current_page_id=0&search_query&page_uri=Lw=&referred=&_=1674954585443
h2
1302.1890000091
2007.5250000227
1091
62
200
application/json
XHR
https://xpassd.net/wp-includes/js/wp-emoji-release.min.js?ver=6.1.1
h2
1334.9760000128
1388.5970000119
5617
18617
200
application/javascript
Script
data
1621.5150000062
1621.6840000125
0
43
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
h2
1628.904000012
1683.7330000126
577741
576984
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2023/01/free-porn-passwords-2023-2.gif
h2
1629.0910000098
1708.0150000111
158462
157707
200
image/gif
Image
https://xpassd.co/wp-content/uploads/2021/01/giphy.gif
h2
1629.5550000214
1720.4970000021
14040
13278
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2021/12/puba-password-main-120x120.jpg
h2
1629.963000014
1659.6770000178
3847
3097
200
image/jpeg
Image
https://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
h2
1630.1420000091
1738.7330000056
957852
957097
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2021/12/12-december-xxx-accounts-2021-120x120.jpg
h2
1632.12200001
1668.0409999972
5440
4686
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)
972.958
14.798
1021.361
7.913
1029.394
96.302
1137.58
57.786
1199.116
8.402
1208.488
19.061
1227.936
67.497
1301.769
72.691
1380.234
14.475
1395.923
8.15
1405.929
6.339
1419.35
5.388
1465.442
17.836
1483.323
19.085
1515.808
25.431
1541.269
91.345
1632.659
12.373
1645.652
105.916
1763.584
9.019
1772.65
5.484
1778.193
5.073
1801.85
8.162
1811.763
11.77
1846.78
7.456
1878.679
6.323
1916.807
22.077
1956.938
16.06
1987.013
18.227
2019.473
17.99
2050.945
19.794
2083.327
17.237
2114.708
21.299
2136.044
13.185
2149.581
16.509
2180.869
14.977
2215.19
16.014
2246.737
15.962
2281.83
15.814
2311.603
5.908
2345.822
7.544
2382.113
5.169
2413.488
5.648
2448.733
13.579
2481.475
15.867
2545.475
6.701
2564.331
6.438
2716.552
5.756
2844.599
38.42
3059.114
6.699
3082.171
6.325
3117.044
5.936
3146.318
6.411
3212.042
6.243
3245.822
6.935
3311.905
7.579
3411.834
5.342
3511.771
5.275
3595.37
5.07
3906.403
5.305
4047.905
5.599
4083.147
5.642
4118.507
5.715
4156.187
7.443
4179.103
7.822
4212.808
5.27
4247.469
10.475
4282.025
7.267
4312.596
5.804
4345.977
5.276
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 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Xpassd.co 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://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
34296
120
Properly size images — Potential savings of 7 KiB
Images can slow down the page's load time. Xpassd.co should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xpassd.co/wp-content/uploads/2021/01/giphy.gif
13278
7631
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Xpassd.co should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xpassd.co should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xpassd.co should consider minifying JS files.
Reduce unused CSS — Potential savings of 41 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xpassd.co should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
34296
29054
https://xpassd.net/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1
13325
13307
Reduce unused JavaScript — Potential savings of 37 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://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
55044
38111
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xpassd.co should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
63
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
0
Avoids enormous network payloads — Total size was 2,136 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
957852
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
577741
https://xpassd.net/wp-content/uploads/2023/01/free-porn-passwords-2023-2.gif
158462
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
128823
https://xpassd.net/wp-content/themes/veen/assets/fonts/fontawesome-webfont.woff2
77916
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
55044
https://fonts.gstatic.com/s/nunito/v25/XRXV3I6Li01BKofINeaBTMnFcQ.woff2
36660
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
34296
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
32715
https://xpassd.net/wp-content/themes/veen/assets/images/urban-sprite-op.png
32469
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. Xpassd.co 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.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://xpassd.net/
798.62
6.787
1.782
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
459.573
62.95
4.009
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
160.465
86.632
2.396
Minimizes main-thread work — 1.5 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)
Rendering
702.26299999999
Style & Layout
377.711
Other
205.141
Script Evaluation
165.836
Parse HTML & CSS
22.689
Script Parsing & Compilation
8.798
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 — 24 requests • 2,136 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
24
2187084
Image
10
1881329
Font
3
142000
Script
3
93376
Stylesheet
4
55486
Document
1
12338
Other
3
2555
Media
0
0
Third-party
7
81441
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
65554
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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.0046959927114202
0.0012378012841276
0.00068734970763988
0.00068393005735311
0.00068393005735311
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://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
1373
106
1250
73
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xpassd.co on mobile screens.
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.

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 — 1.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.6 s
The time taken for the page contents to be visibly populated.

Audits

First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Other

Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Xpassd.co should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://xpassd.co/
190
https://xpassd.co/
150
https://xpassd.net/
0
Avoid an excessive DOM size — 847 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
847
Maximum DOM Depth
15
Maximum Child Elements
45

Other

Reduce initial server response time — Root document took 640 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://xpassd.net/
635.826
Use video formats for animated content — Potential savings of 1,198 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
957097
698681
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
576984
386579
https://xpassd.net/wp-content/uploads/2023/01/free-porn-passwords-2023-2.gif
157707
80431
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
128058
61468
Serve static assets with an efficient cache policy — 15 resources found
Xpassd.co 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://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
604800000
957852
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
604800000
577741
https://xpassd.net/wp-content/uploads/2023/01/free-porn-passwords-2023-2.gif
604800000
158462
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
604800000
128823
https://xpassd.net/wp-content/themes/veen/assets/fonts/fontawesome-webfont.woff2
604800000
77916
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
604800000
55044
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
604800000
34296
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
604800000
32715
https://xpassd.co/wp-content/uploads/2021/01/giphy.gif
604800000
14040
https://xpassd.net/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1
604800000
13325
https://xpassd.net/wp-content/themes/veen/assets/dist/plugins.min.css?ver=2.2.0
604800000
6395
https://xpassd.net/wp-includes/js/wp-emoji-release.min.js?ver=6.1.1
604800000
5617
https://xpassd.net/wp-content/uploads/2021/12/12-december-xxx-accounts-2021-120x120.jpg
604800000
5440
https://xpassd.net/wp-content/uploads/2021/12/puba-password-main-120x120.jpg
604800000
3847
https://xpassd.net/wp-content/litespeed/avatar/afcaf7e3bb2f8b22b8ecb875ce77aea3.jpg?ver=1674539657
604800000
2272
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://xpassd.co/wp-content/uploads/2021/01/giphy.gif
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of xpassd.co. 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.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate 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"]`
Xpassd.co may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

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

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that xpassd.co 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.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
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

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.1
WordPress
6.1.1
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.

Audits

Does not use HTTPS — 2 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://xpassd.co/
Allowed
http://estudiopatagon.com/themes/wordpress/veenv2/wp-content/themes/veen/assets/images/transparent.gif
Automatically upgraded to HTTPS

Audits

Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
92

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xpassd.co on mobile screens.
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.

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

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

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 xpassd.co. 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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xpassd.co on 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
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) 73
Performance 60
Accessibility 92
Best Practices 83
SEO 92
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://xpassd.net/
Updated: 29th January, 2023

1.66 seconds
First Contentful Paint (FCP)
83%
13%
4%

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

Simulate loading on mobile
60

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Xpassd.co should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 13 KiB
Time to Interactive can be slowed down by resources on the page. Xpassd.co should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xpassd.co/wp-content/uploads/2021/01/giphy.gif
13278
13278
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xpassd.co should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xpassd.co should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://xpassd.net/
146.414
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xpassd.co should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
63
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
0
Avoids enormous network payloads — Total size was 1,947 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
957847
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
577775
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
128811
https://xpassd.net/wp-content/themes/veen/assets/fonts/fontawesome-webfont.woff2
77914
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
55042
https://fonts.gstatic.com/s/nunito/v25/XRXV3I6Li01BKofINeaBTMnFcQ.woff2
36659
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
34294
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
32717
https://fonts.gstatic.com/s/josefinsans/v25/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
27423
https://xpassd.co/wp-content/uploads/2021/01/giphy.gif
14124
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. Xpassd.co 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.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://xpassd.net/
2736.184
24.232
5.748
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
1001.028
345.62
16.724
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
519.76
278.756
25.96
Unattributable
268.184
7.464
0
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 • 1,947 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
1993937
Image
7
1688223
Font
3
141996
Script
3
93378
Stylesheet
4
55490
Document
1
12334
Other
3
2516
Media
0
0
Third-party
7
81480
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
65552
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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 — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00022054036458333
0.00014702690972222
0.00014702690972222
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 — 20 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)
5490
395
https://xpassd.net/
1960
232
https://xpassd.net/
2282
114
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
5040
97
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
6592
97
https://xpassd.net/
2192
90
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
5945
73
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
6185
71
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
6115
70
https://xpassd.net/
2851
70
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
6455
69
https://xpassd.net/
2512
69
https://xpassd.net/
2649
69
https://xpassd.net/
2782
69
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
6047
68
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
6387
68
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
6524
68
https://xpassd.net/
694
68
https://xpassd.net/
2581
68
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
5137
66
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xpassd.co on mobile screens.
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.

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.

Audits

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://xpassd.co/
http/1.1
0
98.136000015074
700
0
301
text/plain
https://xpassd.co/
http/1.1
98.501000000397
179.8359999957
721
0
301
text/html
https://xpassd.net/
h2
180.20699999761
325.63400000799
12334
76219
200
text/html
Document
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
h2
338.35600002203
379.38700002269
34294
187631
200
text/css
Stylesheet
https://xpassd.net/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1
h2
338.55300000869
371.63300000248
13323
94889
200
text/css
Stylesheet
https://xpassd.net/wp-content/themes/veen/assets/dist/plugins.min.css?ver=2.2.0
h2
338.90100001008
367.37900000298
6403
28498
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Josefin+Sans%3A400%2C600%2C700%7CNunito%3A400%2C400i%2C600%2C700%2C700i&subset=latin%2Clatin-ext&display=swap
h2
339.17200000724
357.40500001702
1470
11825
200
text/css
Stylesheet
https://estudiopatagon.com/themes/wordpress/veenv2/wp-content/themes/veen/assets/images/transparent.gif
h2
346.34700001334
439.6720000077
383
42
200
image/gif
Image
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
h2
346.07400000095
374.21199999517
32717
89684
200
application/javascript
Script
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
h2
346.43200002029
408.30999999889
55042
190847
200
application/javascript
Script
data
345.00200001639
345.16500000609
0
452
200
text/javascript
Script
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
h2
407.78100001626
435.12500001816
128811
128058
200
image/gif
Image
https://fonts.gstatic.com/s/josefinsans/v25/Qw3aZQNVED7rKGKxtqIqX5EUDXx4Vn8sig.woff2
h2
420.31499999575
424.12000001059
27423
26612
200
font/woff2
Font
https://xpassd.net/wp-content/themes/veen/assets/fonts/fontawesome-webfont.woff2
h2
420.49000001862
479.20500001055
77914
77160
200
font/woff2
Font
https://fonts.gstatic.com/s/nunito/v25/XRXV3I6Li01BKofINeaBTMnFcQ.woff2
h2
420.91000001528
424.78200001642
36659
35848
200
font/woff2
Font
https://xpassd.net/wp-json/wp-statistics/v2/hit?wp_statistics_hit_rest=yes&exclusion_match=no&exclusion_reason&track_all=1&current_page_type=home&current_page_id=0&search_query&page_uri=Lw=&referred=&_=1674954613090
h2
604.14500001934
1292.5859999959
1095
62
200
application/json
XHR
https://xpassd.net/wp-includes/js/wp-emoji-release.min.js?ver=6.1.1
h2
653.61599999596
681.48200001451
5619
18617
200
application/javascript
Script
data
840.80299999914
841.0000000149
0
43
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
h2
849.65600000578
949.67299999553
577775
576984
200
image/gif
Image
https://xpassd.co/wp-content/uploads/2021/01/giphy.gif
h2
849.83500000089
937.20400001621
14124
13278
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2021/12/puba-password-main-120x120.jpg
h2
850.79500000575
884.15100000566
3857
3097
200
image/jpeg
Image
https://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
h2
851.11700001289
899.31900001829
957847
957097
200
image/gif
Image
https://xpassd.net/wp-content/uploads/2021/12/12-december-xxx-accounts-2021-120x120.jpg
h2
851.25400000834
1321.3070000056
5426
4686
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)
330.686
13.662
381.396
8.593
390.919
116.026
506.966
24.307
541.6
7.935
549.562
44.985
597.274
5.429
602.714
98.69
701.488
7.945
713.453
14.892
733.361
28.535
761.925
15.972
778.023
14.59
793.575
8.806
802.459
9.607
816.172
36.47
886.914
6.51
949.206
16.55
970.295
5.259
986.205
14.424
1000.666
14.596
1065.077
16.982
1098.263
17.426
1166.112
17.817
1199.385
16.179
1282.033
16.394
1314.879
17.077
1348.141
17.274
1381.425
16.933
1398.419
17.204
1465.188
24.152
1498.037
17.12
1565.203
17.106
1597.93
34.501
1632.48
15.948
1664.964
17.262
1698.04
17.435
2598.159
8.706
2764.909
5.804
3564.635
6.684
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.

Metrics

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

First Meaningful Paint — 3.9 s
The time taken for the primary content of the page to be rendered.

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. Xpassd.co 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://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
34294
450
Reduce unused CSS — Potential savings of 41 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xpassd.co should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
34294
28901
https://xpassd.net/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1
13323
13308
Reduce unused JavaScript — Potential savings of 40 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://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
55042
40853
Avoid an excessive DOM size — 846 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
846
Maximum DOM Depth
14
Maximum Child Elements
45

Metrics

First Contentful Paint — 3.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 5.7 s
The timing of the largest text or image that is painted.

Audits

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

Other

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Xpassd.co should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://xpassd.co/
630
https://xpassd.co/
480
https://xpassd.net/
0
Use video formats for animated content — Potential savings of 1,120 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
957097
698681
https://xpassd.net/wp-content/uploads/2021/11/huge-mix-fe.gif
576984
386579
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
128058
61468
Serve static assets with an efficient cache policy — 11 resources found
Xpassd.co 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://xpassd.net/wp-content/uploads/2021/10/pp-2.gif
604800000
957847
https://xpassd.net/wp-content/uploads/2023/01/free-xxx-accounts.gif
604800000
128811
https://xpassd.net/wp-content/themes/veen/assets/fonts/fontawesome-webfont.woff2
604800000
77914
https://xpassd.net/wp-content/litespeed/js/b2763c55be0369425d4adf38b8486f80.js?ver=5894a
604800000
55042
https://xpassd.net/wp-content/litespeed/css/64fe01730f09e8b9d29fc720c5ed78d0.css?ver=5894a
604800000
34294
https://xpassd.net/wp-includes/js/jquery/jquery.min.js?ver=3.6.1
604800000
32717
https://xpassd.net/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1
604800000
13323
https://xpassd.net/wp-content/themes/veen/assets/dist/plugins.min.css?ver=2.2.0
604800000
6403
https://xpassd.net/wp-includes/js/wp-emoji-release.min.js?ver=6.1.1
604800000
5619
https://xpassd.net/wp-content/uploads/2021/12/12-december-xxx-accounts-2021-120x120.jpg
604800000
5426
https://xpassd.net/wp-content/uploads/2021/12/puba-password-main-120x120.jpg
604800000
3857
Minimize main-thread work — 4.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)
Rendering
1905.784
Style & Layout
1125.828
Other
735.628
Script Evaluation
698.108
Parse HTML & CSS
85.196
Script Parsing & Compilation
51.86
Garbage Collection
9.984
First Contentful Paint (3G) — 7650 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of xpassd.co. 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.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate 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"]`
Xpassd.co may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

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

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that xpassd.co 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.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
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

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.1
WordPress
6.1.1
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.

Audits

Does not use HTTPS — 2 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://xpassd.co/
Allowed
http://estudiopatagon.com/themes/wordpress/veenv2/wp-content/themes/veen/assets/images/transparent.gif
Automatically upgraded to HTTPS

Audits

Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
92

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xpassd.co on mobile screens.
Document uses legible font sizes — 99.55% legible text
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.
Source Selector % of Page Text Font Size
.widget_rss .rss-date, a, abbr, acronym, address, applet, article, aside, audio, b, big, blockquote, body, button, canvas, caption, center, cite, code, dd, del, details, dfn, div, dl, dt, em, embed, fieldset, figcaption, figure, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, html, i, iframe, img, ins, kbd, label, legend, li, mark, menu, nav, object, ol, output, p, pre, q, ruby, s, samp, section, small, span, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, time, tr, tt, u, ul, var, video
0.41%
0px
.widget_epcl_tag_cloud, .widget_tag_cloud, div.tags
0.03%
0px
#single #comments.hosted nav.pagination a i.fa, .button i.fa, .epcl-button:not(.epcl-shortcode) i.fa
0.01%
11.05px
99.55%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
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 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.
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.
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.

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

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 xpassd.co. 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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xpassd.co on 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
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: 74.63.241.29
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: Yes
Name: REDACTED FOR PRIVACY
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: REDACTED FOR PRIVACY
State: Capital Region
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
.CO Internet, S.A.S. 104.16.99.56
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: xpassd.co
Issued By: R10
Valid From: 6th December, 2024
Valid To: 6th March, 2025
Subject: CN = xpassd.co
Hash: d52c2c7e
Issuer: CN = R10
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0332B669C13139EAC7EFDDED45BDF5A374A1
Serial Number (Hex): 0332B669C13139EAC7EFDDED45BDF5A374A1
Valid From: 6th December, 2025
Valid To: 6th March, 2025
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
Timestamp : Dec 6 02:22:27.852 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:78:82:14:C8:1C:63:76:E2:FA:D8:BD:35:
7B:4E:39:DA:B0:10:7E:9E:1E:CA:38:A3:CF:20:77:1B:
0C:3B:4A:DD:02:21:00:DE:A2:7C:A0:78:93:32:D6:BF:
55:EF:5F:CF:47:3C:0C:D8:F1:59:3B:C1:5E:7D:96:5C:
E0:B7:F0:27:20:E4:F7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
Timestamp : Dec 6 02:22:27.892 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:6E:13:01:8C:A2:4E:7F:B1:7E:77:50:91:
B9:ED:91:37:78:87:C6:73:A4:C1:EB:66:B9:61:08:E7:
9A:0B:B6:C5:02:21:00:9C:80:9E:18:4D:92:B5:DC:5D:
76:37:8B:52:B3:46:C0:12:FB:D1:6F:E1:D0:05:F9:91:
B3:80:00:76:52:5B:06
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:xpassd.co
DNS:*.xpassd.co
Technical

DNS Lookup

A Records

Host IP Address Class TTL
xpassd.co. 162.210.199.85 IN 600

NS Records

Host Nameserver Class TTL
xpassd.co. ns2.koaladns.com. IN 600
xpassd.co. ns1.koaladns.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
xpassd.co. ns1.koaladns.com. admin.xpassd.co. 600

HTTP Response Headers

HTTP-Code: HTTP/1.1 302 Found
cache-control: max-age=0, private, must-revalidate
date: 1st February, 2025
server: nginx
connection: close
content-length: 11
location: http://survey-smiles.com
set-cookie: *

Whois Lookup

Created: 8th October, 2017
Changed: 17th October, 2024
Expires: 7th October, 2025
Registrar: NameCheap, Inc.
Status: clientTransferProhibited
Nameservers: ns1.brainydns.com
ns2.brainydns.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Capital Region
Owner Country: IS
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: xpassd.co
Registry Domain ID: REDACTED FOR PRIVACY
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2024-10-17T19:59:15Z
Creation Date: 2017-10-08T11:02:25Z
Registry Expiry Date: 2025-10-07T23:59:59Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Capital Region
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: IS
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.brainydns.com
Name Server: ns2.brainydns.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2025-02-01T05:10:07Z <<<

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

The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.co.

.CO Internet, S.A.S., the Administrator for .CO, has collected this information for the WHOIS database through Accredited Registrars. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the .CO Internet registry database. .CO Internet makes this information available to you "as is" and does not guarantee its accuracy.

By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection laws; or (3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without .CO Internet's prior written permission. .CO Internet reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. In some limited cases, domains that might appear as available in whois might not actually be available as they could be already registered and the whois not yet updated and/or they could be part of the Restricted list. In this cases, performing a check through your Registrar's (EPP check) will give you the actual status of the domain. Additionally, domains currently or previously used as extensions in 3rd level domains will not be available for registration in the 2nd level. For example, org.co, mil.co, edu.co, com.co, net.co, nom.co, arts.co, firm.co, info.co, int.co, web.co, rec.co, co.co.

NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.cointernet.co <http://www.cointernet.co>.

Nameservers

Name IP Address
ns1.brainydns.com 207.244.67.194
ns2.brainydns.com 5.79.65.16
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
0/5
0/5
0/5