naughtyblog.st

Naughtyblog.st

#10,285 Global
NABLOG | Newest Posts
Last Updated 33 mins ago
     
This can take up to 60 seconds. Please wait...
Update will be available in 24 hours

Domain Summary

What is the traffic rank for Naughtyblog.st?

Naughtyblog.st ranks #10,285 globally on HypeStat.

What percent of global Internet users visit Naughtyblog.st?

0.002642% of global Internet users visit Naughtyblog.st

How many people visit Naughtyblog.st each day?

Naughtyblog.st receives approximately 158.5K visitors and 1,272,205 page impressions per day.

Which countries does Naughtyblog.st receive most of its visitors from?

Naughtyblog.st is mostly visited by people located in United States,Germany,France.

How much Naughtyblog.st can earn?

Naughtyblog.st should earn about $2,394.01/day from advertising revenue.

What is Naughtyblog.st estimated value?

Estimated value of Naughtyblog.st is $2,263,697.70.

What IP addresses does Naughtyblog.st resolve to?

Naughtyblog.st resolves to the IP addresses 2606:4700:20::681a:668, 104.26.7.104.

naughtyblog.st Profile

Title
NABLOG | Newest Posts
Category
Adult / Adult

naughtyblog.st Traffic Analysis

Naughtyblog.st is ranked #10,285 in the world. This website is viewed by an estimated 158.5K visitors daily, generating a total of 1.3M pageviews. This equates to about 4.8M monthly visitors. Naughtyblog.st traffic has increased by 6.82% compared to last month.

Daily Visitors
158.5K
158,494 unique
▲ 4.95%
Monthly Visits
4.8M
▲ 6.82%
Pages per Visit
8.03
▲ 4.88%
Visit Duration
06:23
▲ 14.58%
Bounce Rate
30.64%
▼ 9.4%
Is this your site?Verify your site's metrics.
Daily Unique Visitors
158,494
Monthly Visits
4,802,368
Pages per Visit
8.03
Daily Pageviews
1,272,205
Avg. Visit Duration
06:23
Bounce Rate
30.64%
Global Reach
0.002642%
Monthly Visits (SEMrush)
4,744,251
Monthly Unique Visitors (SEMrush)
864,100
Monthly Visits (SimilarWeb)
4,851,847
HypeRank
10,285
SEMrush Rank
16,473,718
SimilarWeb Rank
9,183

*All traffic values are estimates only.

Traffic Sources

Direct
80.81%
Referral
15.38%
Search
3.55%
Social
0.26%
Paid
0%

Desktop vs Mobile

Desktop
72.70%
Mobile
27.30%

Total Visits Last 3 Months

1.2M
JUL
4.5M
AUG
4.8M
SEP

Visitors by Country

CountryUsers %
United States 36.15%
Germany 8.87%
France 4.85%
Italy 4.60%
United Kingdom 3.91%
SEO

naughtyblog.st SEMrush Overview

SEMrush is a complete online advertising and marketing platform that gives a wide variety of tools and features to help businesses and marketers improve their online visibility and optimize their digital marketing strategies.

SemRushSemRush
Domain
naughtyblog.st
RankBased on keywords, cost and organic traffic
16,473,718
Organic KeywordsKeywords in top 20 Google SERP
16
Organic TrafficVisitors coming from top 20 search results
0
Organic CostEquivalent Google Ads spend for the same traffic
$0.00
Full SEMrush Report →

Which sites are competitors to naughtyblog.st?

Websites similar to naughtyblog.st are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.

DomainDaily Visitors
***hub.com hidden Compare →
***.com 38.3M Compare →
***.com 29.3M Compare →
***.com hidden Compare →
***.com 7.6M Compare →
you***.com 3.7M Compare →
you***.com 1.8M Compare →
***.com 1.5M Compare →
***friendfinder.com 322.8K Compare →
tube8.com 316.2K Compare →
***.com 305.7K Compare →
streamate.com 120.3K Compare →
phun.org 80.7K Compare →
***rabbit.com 65.1K Compare →
realitykings.com 54.5K Compare →
modelmayhem.com 39.8K Compare →
***titan.com 2.2K Compare →
spankwire.com 1.1K Compare →
fantasti.cc 844 Compare →
4gifs.com 22 Compare →
Monetization

Revenue Report

naughtyblog.st would generate approximately $2.4K per day if the source of income were advertisements, which equates to an estimated monthly revenue of $71.8K and annual gross revenue of approximately $873.8K. Based on these figures, the site's net worth is estimated at around $2.3M.

How much would naughtyblog.st make?

Daily Revenue
$2,394.01
Monthly Revenue
$71,820.30
Yearly Revenue
$873,813.65

How much is naughtyblog.st worth?

Website Value
$2.3M

*All earnings values are estimates only.

Daily Earning by Country

CountryPageviewsEarning
United States 459,909 $1,821.52
Germany 112,851 $112.17
United Kingdom 49,781 $112.07
France 61,672 $31.84
Italy 58,496 $11.65

Daily Revenue Loss by Country

CountryBlockedLost
United States 82,784 $399.84
Germany 32,727 $45.82
United Kingdom 7,965 $21.35
France 6,784 $3.93
Italy 9,944 $2.39

Impact of Ad Blockers

Daily Revenue Loss
$473.33
Monthly Revenue Loss
$14,199.90
Yearly Revenue Loss
$172,765.41
Daily Pageviews Blocked
140,204
Monthly Pageviews Blocked
4,206,108
Yearly Pageviews Blocked
51,174,319

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to naughtyblog.st, per platform.

Mobile Summary

Root Domain
naughtyblog.st
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Desktop Summary

Root Domain
naughtyblog.st
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Abusive Experience

Root Domain
naughtyblog.st
EnforcementChrome is not preventing your site from opening new windows or tabs.
Off
StatusReviewed for abusive experiences
Not reviewed
Technical

Where is naughtyblog.st hosted?

Naughtyblog.st may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

ASN
AS13335
ISP
Cloudflare, Inc.
Server Location


Other sites hosted on 104.26.7.104

There are no other sites hosted on this IP.

How fast does naughtyblog.st load?

The average loading time of naughtyblog.st is 68 ms. The Desktop speed index is 68 and mobile speed index is 39.

68
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
68 ms

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report. We are showing the 90th percentile of FCP and the 95th percentile of FID.

CLSCumulative Layout Shift
1ms
94% fast3% avg2% slow
TTFBTime To First Byte
1.3s
52% fast32% avg15% slow
FCPFirst Contentful Paint
1.6s
79% fast12% avg8% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
16ms
98% fast0% avg0% slow
LCPLargest Contentful Paint
2.0s
83% fast9% avg6% slow

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report over the last 30 days. To view suggestions tailored to each page, analyze individual page URLs.

CLSCumulative Layout Shift
0ms
95% fast2% avg1% slow
TTFBTime To First Byte
1.1s
60% fast28% avg10% slow
FCPFirst Contentful Paint
1.4s
83% fast10% avg5% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
42ms
96% fast1% avg1% slow
LCPLargest Contentful Paint
1.6s
88% fast7% avg4% slow
Speed Index1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive2.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Largest Contentful Paint1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
INP breakdown
Start investigating by looking at the longest subpart. how to improve INP
Max Potential First Input Delay240 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
39
Poor
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
68 ms

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report. We are showing the 90th percentile of FCP and the 95th percentile of FID.

CLSCumulative Layout Shift
0ms
89% fast5% avg4% slow
TTFBTime To First Byte
1.6s
44% fast35% avg19% slow
FCPFirst Contentful Paint
1.8s
75% fast14% avg10% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
86ms
96% fast2% avg0% slow
LCPLargest Contentful Paint
2.0s
82% fast10% avg7% slow

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report over the last 30 days. To view suggestions tailored to each page, analyze individual page URLs.

CLSCumulative Layout Shift
0ms
93% fast4% avg2% slow
TTFBTime To First Byte
1.3s
56% fast29% avg13% slow
FCPFirst Contentful Paint
1.5s
81% fast11% avg7% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
112ms
90% fast7% avg2% slow
LCPLargest Contentful Paint
1.7s
87% fast7% avg4% slow
Total Blocking Time140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
First Contentful Paint5.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Speed Index6.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Time to Interactive10.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Largest Contentful Paint9.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
INP breakdown
Start investigating by looking at the longest subpart. how to improve INP

Does naughtyblog.st use compression?

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on naughtyblog.st are reduced by 44%.

44%
Reduced
Original
5.41 KB
Compressed
3.03 KB

Saved 2.39 KB off the original size

naughtyblog.st use br compression.

Google Safe Browsing

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.

This site is not currently listed as suspicious

WOT MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.

Status
SAFE

SSL Checker SSL Certificate Verify

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. naughtyblog.st supports HTTPS.

naughtyblog.st supports HTTPS
Verifying SSL Support. Please wait...
Common Name: naughtyblog.st
Organization:
Location:
Issuer: WE1
Valid from: Sep 19 17:31:16 2026 GMT
Valid until: Dec 18 18:31:01 2026 GMT
Authority: CA:FALSE
Keysize:
Common Name: WE1
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Common Name: GTS Root R4
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize:

Email Security

SPF, DKIM and DMARC are DNS records that prove which servers may send email for a domain and tell receivers what to do with forged messages. naughtyblog.st has SPF and an enforced DMARC policy, which protects it against email spoofing.

Email provider
Cloudflare Email Routing
SPF
present
DMARC
reject
DKIM
found
DNSSEC
not signed
v=spf1 include:_spf.mx.cloudflare.net ~all

AI Crawlers

Websites use robots.txt to allow or block AI crawlers that collect content for training and AI search. naughtyblog.st blocks 13 of 26 known AI crawlers.

OpenAI
blocked GPTBot
Anthropic
blocked ClaudeBot, anthropic-ai, Claude-Web
Google
blocked Google-Extended
Apple
blocked Applebot-Extended
Common Crawl
blocked CCBot
ByteDance
blocked Bytespider
Amazon
blocked Amazonbot
Meta
blocked meta-externalagent
Cohere
blocked cohere-ai
Diffbot
blocked Diffbot
Webz.io
blocked omgili
llms.txt
not found

Verify HTTP/2 & HTTP/3 Support

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.

naughtyblog.st supports HTTP/2
naughtyblog.st supports HTTP/3
Verifying HTTP/2 and HTTP/3 Support. Please wait...
Details

Http Header

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.

HTTP/1.1
date: Tue, 20 Oct 2026 07:44:33 GMT
content-type: text/html; charset=UTF-8
accept-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
cf-mitigated: challenge
content-security-policy: default-src 'none'; script-src 'nonce-hysBruffS401nr1wzRz2YE' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'
server: cloudflare
critical-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
cross-origin-embedder-policy: require-corp
cross-origin-opener-policy: same-origin
cross-origin-resource-policy: same-origin
origin-agent-cluster: ?1
permissions-policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
referrer-policy: same-origin
server-timing: chlray;desc="a4d665e27fff742f"
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
speculation-rules: "/cdn-cgi/speculation"
vary: accept-encoding
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=uHQMKi5xHk%2FBOsH%2BkaCHdYHQMYvRITdzkD%2BrGtBiUe0bLnrW%2BcGk6jzDjvNq244YYD0eWqPaNtmMyUBcYlI%2B1RgcW6YWMP6Oo0L%2Fe3iWOhOZudTjQeisSGtsz%2Ftd0renvFJf98FQc9z9JOea"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
content-encoding: br
cf-ray: a4d665e27fff742f-TXL
alt-svc: h3=":443"; ma=86400

DNS Lookup

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.

TypeIPTarget / TXTTTL
AAAA 2606:4700:20::ac43:4a88 286
AAAA 2606:4700:20::681a:768 286
AAAA 2606:4700:20::681a:668 286
NS fred.ns.cloudflare.com 86386
NS kara.ns.cloudflare.com 86386
More on HypeStat
Activity

Recently Analyzed Sites

si-academy.it
HTTP/3 supportedHTTPS supported 9 secs
nastiinkaaa.de
HTTP/2 supportedHTTPS supported 18 secs
***moix.com
HTTP/3 supportedHTTPS supported 57 secs
hilinecrm.it
HTTP/3 supportedHTTPS supported 1 min
***hub-x.com
HTTP/3 supportedHTTPS supported 1 min
mulahubafrica.com
HTTP/3 supportedHTTPS supported 1 min
***chatters.com
HTTP/3 supportedHTTPS supported 2 mins
hlbc.net
HTTP/3 supportedHTTPS supported 2 mins
league-one-dtc.com
HTTP/2 supportedHTTPS supported 3 mins
easywatt24.de
HTTP/2 not supportedHTTPS supported 3 mins
fashionscloud.net
HTTP/2 supportedHTTPS supported 4 mins
cloverpay2027.com
HTTP/2 supportedHTTPS supported 4 mins
chinaq.net
HTTP/3 supportedHTTPS supported 5 mins
akihatecnologia.pt
HTTP/3 supportedHTTPS supported 5 mins
aa123tra.com
HTTP/3 supportedHTTPS supported 5 mins
Resources

Custom Widget

naughtyblog.st
Daily Visitors 158.5K
Monthly Visits 4.8M
Pages / Visit 8.03
HypeRank #10,285
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.