shodan.io

shodan.io is SSL secured

Free website and domain report on shodan.io

Last Updated: 10th October, 2023 Update Now
Overview

Snoop Summary for shodan.io

This is a free and comprehensive report about shodan.io. Shodan.io is hosted in United States on a server with an IP address of 104.18.13.238, where the local currency is USD and English is the local language. Shodan.io is expected to earn an estimated $259 USD per day from advertising revenue. The sale of shodan.io would possibly be worth $188,993 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Shodan.io is wildly popular with an estimated 61,217 daily unique visitors. This report was last updated 10th October, 2023.

About shodan.io

Site Preview: shodan.io shodan.io
Title: Shodan Search Engine
Description: Search Engine for the Internet of Things
Keywords and Tags: hardware, industrial control systems, information security, iot search engine, popular, shoda, shodan, shodan api, shodan api key, shodan dork, shodan io, shodan ip, shodan ip camera search, shodan search, shodan search engine, shodanhq, software, what is shodan, www shodan io
Related Terms:
Fav Icon:
Age: Over 11 years old
Domain Created: 22nd August, 2012
Domain Updated: 18th November, 2021
Domain Expires: 22nd August, 2022
Review

Snoop Score

4/5 (Excellent!)

Valuation

$188,993 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 18,700
Alexa Reach:
SEMrush Rank (US): 73,117
SEMrush Authority Score: 62
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 3,184 6
Traffic: 26,513 1,296
Cost: $39,505 USD $1,782 USD
Traffic

Visitors

Daily Visitors: 61,217
Monthly Visitors: 1,863,257
Yearly Visitors: 22,344,262
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $259 USD
Monthly Revenue: $7,880 USD
Yearly Revenue: $94,491 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 3,147,665
Referring Domains: 7,356
Referring IPs: 8,190
Shodan.io has 3,147,665 backlinks according to SEMrush. 99% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve shodan.io's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of shodan.io's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://www.securityartwork.es/category/general/page/41/
Target: https://developer.shodan.io/

2
Source: https://www.securityartwork.es/category/general/page/41/
Target: https://www.shodan.io/report/gffzAK3x

3
Source: https://www.securityartwork.es/category/general/page/41/
Target: https://www.shodan.io/report/SQQ32B3g

4
Source: https://www.favoritei.com.br/
Target: https://www.shodan.io/

5
Source: https://4hou.win/wordpress/?author=31&paged=32
Target: https://malware-hunter.shodan.io/

Top Ranking Keywords (US)

1
Keyword: shodan
Ranked Page: https://www.shodan.io/

2
Keyword: shodan io
Ranked Page: https://www.shodan.io/

3
Keyword: what is shodan
Ranked Page: https://www.shodan.io/

4
Keyword: shodan search engine
Ranked Page: https://www.shodan.io/

5
Keyword: shodan search
Ranked Page: https://www.shodan.io/

Domain Analysis

Value Length
Domain: shodan.io 9
Domain Name: shodan 6
Extension (TLD): io 2
Expiry Check:

Page Speed Analysis

Average Load Time: 1.33 seconds
Load Time Comparison: Faster than 71% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 96
Accessibility 96
Best Practices 92
SEO 91
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.shodan.io/
Updated: 15th February, 2022

1.05 seconds
First Contentful Paint (FCP)
90%
6%
4%

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

Simulate loading on desktop
96

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 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://shodan.io/
http/1.1
0
81.484999507666
389
0
301
text/plain
https://shodan.io/
http/1.1
81.891999579966
759.06899943948
645
0
301
text/html
https://www.shodan.io/
h2
759.44699998945
1002.3139994591
3976
11480
200
text/html
Document
https://wire.shodan.io/v2.4.0/default/css/wire.css
h2
1014.7000001743
1129.0830001235
8374
35845
200
text/css
Stylesheet
https://kit.fontawesome.com/b7e79643d9.js
h2
1014.9889998138
1049.0509998053
4742
11076
200
text/javascript
Script
https://www.shodan.io/static/img/logo.png
h2
1017.5279993564
1142.5470001996
2875
2070
200
image/webp
Image
https://www.shodan.io/static/img/pingmap.png
h2
1017.7899999544
1121.6249996796
27486
26676
200
image/webp
Image
https://www.shodan.io/static/img/dashboard.png
h2
1017.9770002142
1105.8780001476
11306
10494
200
image/webp
Image
https://www.shodan.io/static/default/img/developer.png
h2
1018.3049999177
1147.5139996037
6882
6072
200
image/webp
Image
https://www.shodan.io/static/img/ipinfo.png
h2
1018.5529999435
1165.4509995133
123835
123034
200
image/webp
Image
https://ka-p.fontawesome.com/releases/v5.15.4/js/pro.min.js?token=b7e79643d9
h2
1136.0189998522
1188.5139998049
14883
40783
200
application/javascript
Fetch
data
1137.5789996237
1137.6709993929
0
152
200
image/png
Image
https://wire.shodan.io/v2.4.0/default/img/bg-dark_7cd79f7e.jpg
h2
1138.919999823
1245.868999511
136990
136131
200
image/jpeg
Image
https://wire.shodan.io/v2.4.0/default/img/raleway-regular_de901d73.woff2
h2
1145.0959993526
1258.229999803
54589
53692
200
binary/octet-stream
Font
https://wire.shodan.io/v2.4.0/default/img/raleway-700_611b423f.woff2
h2
1145.6559998915
1248.1359997764
55533
54648
200
binary/octet-stream
Font
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/bars.svg?token=b7e79643d9
h2
1207.6799999923
1260.6999995187
776
558
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/globe.svg?token=b7e79643d9
h2
1208.4739999846
1250.3109993413
1063
955
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/briefcase.svg?token=b7e79643d9
h2
1209.2509996146
1261.225999333
826
485
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/external-link.svg?token=b7e79643d9
h2
1210.1019993424
1260.0170001388
889
641
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/search.svg?token=b7e79643d9
h2
1210.5999998748
1272.4029999226
863
562
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/globe.svg?token=b7e79643d9
h2
1211.2400000915
1253.4929998219
1086
1011
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/sitemap.svg?token=b7e79643d9
h2
1211.9519999251
1252.5689993054
918
918
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/briefcase.svg?token=b7e79643d9
h2
1212.5849993899
1253.752999939
875
596
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/cloud.svg?token=b7e79643d9
h2
1213.1549995393
1271.9399994239
952
692
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/graduation-cap.svg?token=b7e79643d9
h2
1213.7850001454
1253.9559993893
1176
1165
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/chrome.svg?token=b7e79643d9
h2
1214.2359996215
1271.5739998966
960
714
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/firefox.svg?token=b7e79643d9
h2
1214.955999516
1272.7979999036
1540
2315
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/life-ring.svg?token=b7e79643d9
h2
1219.0060000867
1288.5109996423
954
874
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/twitter.svg?token=b7e79643d9
h2
1222.0439994708
1259.2629995197
1091
1008
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/linkedin.svg?token=b7e79643d9
h2
1222.1820000559
1247.2279993817
917
641
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/facebook.svg?token=b7e79643d9
h2
1222.292999737
1254.858000204
842
481
200
image/svg+xml
Fetch
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)
1052.885
8.501
1180.081
14.639
1194.73
39.546
1237.933
8.384
1248.894
17.454
1297.406
5.105
1308.869
11.098
1324.993
51.616
1393.027
45.524
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Shodan.io should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Shodan.io should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Shodan.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Shodan.io should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Shodan.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 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)
https://www.shodan.io/
243.861
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Shodan.io 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 — 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://www.shodan.io/
167
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 457 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wire.shodan.io/v2.4.0/default/img/bg-dark_7cd79f7e.jpg
136990
https://www.shodan.io/static/img/ipinfo.png
123835
https://wire.shodan.io/v2.4.0/default/img/raleway-700_611b423f.woff2
55533
https://wire.shodan.io/v2.4.0/default/img/raleway-regular_de901d73.woff2
54589
https://www.shodan.io/static/img/pingmap.png
27486
https://ka-p.fontawesome.com/releases/v5.15.4/js/pro.min.js?token=b7e79643d9
14883
https://www.shodan.io/static/img/dashboard.png
11306
https://wire.shodan.io/v2.4.0/default/css/wire.css
8374
https://www.shodan.io/static/default/img/developer.png
6882
https://kit.fontawesome.com/b7e79643d9.js
4742
Avoids an excessive DOM size — 206 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
206
Maximum DOM Depth
11
Maximum Child Elements
8
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. Shodan.io 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)
https://www.shodan.io/
187.313
16.548
1.196
Minimizes main-thread work — 0.3 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
94.483
Style & Layout
55.653
Script Evaluation
47.127
Other
46.621
Parse HTML & CSS
7.708
Script Parsing & Compilation
5.215
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 — 30 requests • 457 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
30
468233
Image
6
309374
Font
2
110122
Other
19
31645
Stylesheet
1
8374
Script
1
4742
Document
1
3976
Media
0
0
Third-party
18
35353
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)
35353
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
9.6975422321054E-5
8.7547256262063E-5
3.6290956655641E-5
1.0475740065546E-5
8.6948642544032E-6
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.shodan.io/
192
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 shodan.io on mobile screens.

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

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

Other

Eliminate render-blocking resources — Potential savings of 210 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Shodan.io 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://wire.shodan.io/v2.4.0/default/css/wire.css
8374
230
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Shodan.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://shodan.io/
190
https://shodan.io/
150
https://www.shodan.io/
0
Serve static assets with an efficient cache policy — 9 resources found
Shodan.io 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://wire.shodan.io/v2.4.0/default/img/bg-dark_7cd79f7e.jpg
432000000
136990
https://www.shodan.io/static/img/ipinfo.png
432000000
123835
https://wire.shodan.io/v2.4.0/default/img/raleway-700_611b423f.woff2
432000000
55533
https://wire.shodan.io/v2.4.0/default/img/raleway-regular_de901d73.woff2
432000000
54589
https://www.shodan.io/static/img/pingmap.png
432000000
27486
https://www.shodan.io/static/img/dashboard.png
432000000
11306
https://wire.shodan.io/v2.4.0/default/css/wire.css
432000000
8374
https://www.shodan.io/static/default/img/developer.png
432000000
6882
https://www.shodan.io/static/img/logo.png
432000000
2875

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://www.shodan.io/static/img/ipinfo.png
https://www.shodan.io/static/img/pingmap.png
https://www.shodan.io/static/default/img/developer.png
https://www.shodan.io/static/img/dashboard.png
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of shodan.io. 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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that shodan.io 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

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.
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for shodan.io. 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 shodan.io 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Content Best Practices

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

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 shodan.io. 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 shodan.io 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) 74
Performance 69
Accessibility 96
Best Practices 85
SEO 90
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.shodan.io/
Updated: 15th February, 2022

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

0.02 seconds
First Input Delay (FID)
86%
14%
0%

Simulate loading on mobile
69

Performance

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

Metrics

Time to Interactive — 2.7 s
The time taken for the page to become fully interactive.
Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 20 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 — 70 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://shodan.io/
http/1.1
0
97.943999920972
388
0
301
text/plain
https://shodan.io/
http/1.1
98.371999920346
215.78399999999
643
0
301
text/html
https://www.shodan.io/
h2
216.12499991897
413.63899991848
3976
11480
200
text/html
Document
https://wire.shodan.io/v2.4.0/default/css/wire.css
h2
428.08999994304
751.80299999192
8374
35845
200
text/css
Stylesheet
https://kit.fontawesome.com/b7e79643d9.js
h2
428.45699994359
454.54599999357
4742
11076
200
text/javascript
Script
https://www.shodan.io/static/img/logo.png
h2
431.37699994259
496.53799994849
2876
2070
200
image/webp
Image
https://www.shodan.io/static/img/pingmap.png
h2
431.58799991943
503.36199998856
27487
26676
200
image/webp
Image
https://www.shodan.io/static/img/dashboard.png
h2
431.84600002132
483.08599996381
11307
10494
200
image/webp
Image
https://www.shodan.io/static/default/img/developer.png
h2
432.06499994267
495.8420000039
6882
6072
200
image/webp
Image
https://www.shodan.io/static/img/ipinfo.png
h2
432.44200001936
502.5879999157
123845
123034
200
image/webp
Image
https://ka-p.fontawesome.com/releases/v5.15.4/js/pro.min.js?token=b7e79643d9
h2
759.94699995499
794.54299993813
14852
40783
200
application/javascript
Fetch
data
762.42699997965
762.54699996207
0
152
200
image/png
Image
https://wire.shodan.io/v2.4.0/default/img/bg-dark_7cd79f7e.jpg
h2
763.88799992856
786.37699992396
136991
136131
200
image/jpeg
Image
https://wire.shodan.io/v2.4.0/default/img/raleway-regular_de901d73.woff2
h2
770.2130000107
888.04599992
54578
53692
200
binary/octet-stream
Font
https://wire.shodan.io/v2.4.0/default/img/raleway-700_611b423f.woff2
770.4949999461
2814.5609999774
0
0
-1
Font
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/bars.svg?token=b7e79643d9
h2
838.50800001528
863.49599994719
777
558
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/globe.svg?token=b7e79643d9
h2
839.43799999543
958.02999997977
1059
955
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/briefcase.svg?token=b7e79643d9
h2
840.33399994951
932.13299999479
825
485
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/external-link.svg?token=b7e79643d9
h2
841.34499996435
873.83799999952
889
641
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/solid/search.svg?token=b7e79643d9
h2
842.16499992181
889.62000003085
864
562
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/globe.svg?token=b7e79643d9
h2
842.83300000243
862.14500002097
1086
1011
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/sitemap.svg?token=b7e79643d9
h2
843.70600001421
865.72300002445
918
918
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/briefcase.svg?token=b7e79643d9
h2
844.46799999569
871.46199995186
874
596
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/cloud.svg?token=b7e79643d9
h2
844.94699991774
873.21300001349
952
692
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/graduation-cap.svg?token=b7e79643d9
h2
845.49700003117
869.43399999291
1176
1165
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/chrome.svg?token=b7e79643d9
h2
846.24899993651
884.97599994298
960
714
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/firefox.svg?token=b7e79643d9
h2
846.8410000205
866.27999995835
1540
2315
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/regular/life-ring.svg?token=b7e79643d9
h2
847.49700000975
868.892999948
955
874
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/twitter.svg?token=b7e79643d9
h2
848.11799996532
879.88999998197
1090
1008
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/linkedin.svg?token=b7e79643d9
h2
848.80999999586
916.45999997854
917
641
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v5.15.4/svgs/brands/facebook.svg?token=b7e79643d9
h2
849.64099992067
895.72399994358
842
481
200
image/svg+xml
Fetch
https://wire.shodan.io/v2.4.0/default/img/raleway-700_ff26f36.woff
h2
2814.7739999695
3162.6039999537
70408
69524
200
application/font-woff
Font
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)
458.11
9.787
797.207
17.205
814.425
40.833
862.93
7.937
872.303
20.298
892.619
33.571
933.958
6.168
948.331
11.799
1016.387
17.237
3205.304
8.251
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Shodan.io should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Shodan.io should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Shodan.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Shodan.io should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Shodan.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 200 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.shodan.io/
198.504
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Shodan.io 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 — 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://www.shodan.io/
167
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 472 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wire.shodan.io/v2.4.0/default/img/bg-dark_7cd79f7e.jpg
136991
https://www.shodan.io/static/img/ipinfo.png
123845
https://wire.shodan.io/v2.4.0/default/img/raleway-700_ff26f36.woff
70408
https://wire.shodan.io/v2.4.0/default/img/raleway-regular_de901d73.woff2
54578
https://www.shodan.io/static/img/pingmap.png
27487
https://ka-p.fontawesome.com/releases/v5.15.4/js/pro.min.js?token=b7e79643d9
14852
https://www.shodan.io/static/img/dashboard.png
11307
https://wire.shodan.io/v2.4.0/default/css/wire.css
8374
https://www.shodan.io/static/default/img/developer.png
6882
https://kit.fontawesome.com/b7e79643d9.js
4742
Avoids an excessive DOM size — 206 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
206
Maximum DOM Depth
11
Maximum Child Elements
8
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Shodan.io 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://www.shodan.io/
681.68
85.508
5.784
Unattributable
202.396
38.944
0.988
https://kit.fontawesome.com/b7e79643d9.js
121.928
94.668
14.484
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
268.268
Other
238.36
Rendering
226.472
Script Evaluation
219.12
Parse HTML & CSS
40.744
Script Parsing & Compilation
21.256
Garbage Collection
5.224
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 — 31 requests • 472 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
31
483073
Image
6
309388
Font
3
124986
Other
19
31607
Stylesheet
1
8374
Script
1
4742
Document
1
3976
Media
0
0
Third-party
18
35318
Minimize third-party usage — Third-party code blocked the main thread for 10 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)
35318
11.096
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 — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.44427995980965
0.0093456949474521
0.0044032601194726
0.0032709932316083
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 — 3 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://www.shodan.io/
638
134
https://www.shodan.io/
1890
82
https://kit.fontawesome.com/b7e79643d9.js
2670
69
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 shodan.io on mobile screens.

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.7 s
The time taken for the first image or text on the page to be rendered.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 700 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Shodan.io 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://wire.shodan.io/v2.4.0/default/css/wire.css
8374
780
Serve static assets with an efficient cache policy — 9 resources found
Shodan.io 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://wire.shodan.io/v2.4.0/default/img/bg-dark_7cd79f7e.jpg
432000000
136991
https://www.shodan.io/static/img/ipinfo.png
432000000
123845
https://wire.shodan.io/v2.4.0/default/img/raleway-700_ff26f36.woff
432000000
70408
https://wire.shodan.io/v2.4.0/default/img/raleway-regular_de901d73.woff2
432000000
54578
https://www.shodan.io/static/img/pingmap.png
432000000
27487
https://www.shodan.io/static/img/dashboard.png
432000000
11307
https://wire.shodan.io/v2.4.0/default/css/wire.css
432000000
8374
https://www.shodan.io/static/default/img/developer.png
432000000
6882
https://www.shodan.io/static/img/logo.png
432000000
2876

Metrics

Largest Contentful Paint — 4.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.461
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Shodan.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://shodan.io/
630
https://shodan.io/
480
https://www.shodan.io/
0
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://www.shodan.io/static/img/ipinfo.png
https://www.shodan.io/static/img/pingmap.png
https://www.shodan.io/static/default/img/developer.png
https://www.shodan.io/static/img/dashboard.png
First Contentful Paint (3G) — 5220 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of shodan.io. 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.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that shodan.io 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

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to font at 'https://wire.shodan.io/v2.4.0/default/img/raleway-700_611b423f.woff2' from origin 'https://www.shodan.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for shodan.io. 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 shodan.io on mobile screens.
Document uses legible font sizes — 98.27% 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
.button, button, input[type=button], input[type=reset], input[type=submit]
1.24%
11px
.quickbar
0.49%
11px
98.27%
≥ 12px

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 84% 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.
Tap Target Size Overlapping Target
33x13
15x21
15x21

Content Best Practices

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

Manual Checks

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

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

PWA Optimized

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 shodan.io 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
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.
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.18.13.238
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
Gandi SAS 146.75.77.103
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 16th June, 2021
Valid To: 15th June, 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: 1671595663992479133038571627252002725
Serial Number (Hex): 0141F0077FA248AEB8D88587C917AFA5
Valid From: 16th June, 2024
Valid To: 15th June, 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 : Jun 16 16:21:11.747 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0C:44:CB:97:98:55:87:9F:1B:3F:14:4C:
FB:D0:7A:8E:66:1C:56:EF:46:6A:91:3E:E0:BA:FA:29:
D3:89:74:6E:02:21:00:86:CA:9D:CC:44:AE:A5:82:72:
3C:43:53:32:54:67:77:72:FC:28:7C:C2:A7:D2:E3:67:
A5:4B:3A:39:29:85:DF
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Jun 16 16:21:11.829 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:CD:76:91:AE:3F:DC:AA:12:E3:3C:A6:
66:88:14:A0:66:C8:32:6F:49:62:3F:0F:C9:51:74:8F:
D0:29:AC:59:96:02:20:6E:D9:A5:EC:DD:45:81:38:1F:
C2:8C:0A:14:52:1F:9A:FA:36:BD:7C:09:38:CB:CC:9C:
8A:2D:0E:7B:83:5A:13
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 : Jun 16 16:21:11.726 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:55:2E:48:73:29:35:B5:0C:6B:CE:FC:CC:
A2:DD:BE:C6:7D:A0:2B:11:B0:BC:84:0C:19:C8:63:00:
0A:6B:75:26:02:21:00:B9:E9:98:C6:92:46:D3:3B:72:
FA:B1:2E:18:02:0A:AD:82:99:8B:35:5F:61:EB:28:F7:
B1:04:2C:62:80:7D:FB
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.shodan.io
DNS:sni.cloudflaressl.com
DNS:shodan.io
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 15th February, 2022
Content-Type: text/html; charset=UTF-8
Server: cloudflare
Connection: keep-alive
Vary: Accept-Encoding
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=63072000; includeSubDomains
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
permissions-policy: interest-cohort=()
CF-RAY: 6de119679caf8c1d-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 22nd August, 2012
Changed: 18th November, 2021
Expires: 22nd August, 2022
Registrar: Gandi SAS
Status: ok
Nameservers: ed.ns.cloudflare.com
lady.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: John Matherly
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: .
Owner Country: FR
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
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
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: shodan.io
Registry Domain ID: 164a65d6714b47228bdedff858cac71b-DONUTS
Registrar WHOIS Server: whois.gandi.net
Registrar URL: https://www.gandi.net
Updated Date: 2021-11-18T22:58:47Z
Creation Date: 2012-08-22T03:02:54Z
Registry Expiry Date: 2022-08-22T03:02:54Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: John Matherly
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: .
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: FR
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 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 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: lady.ns.cloudflare.com
Name Server: ed.ns.cloudflare.com
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-02-15T19:56:25Z <<<

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

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
ed.ns.cloudflare.com 108.162.193.111
lady.ns.cloudflare.com 108.162.192.127
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$10 USD

Sites hosted on the same IP address