trench.bot Trench.bot

   
TrenchRadar Bundle Viewer

Domain Summary

What percent of global Internet users visit Trench.bot?

• 0.0005342% of global Internet users visit Trench.bot

How many people visit Trench.bot each day?

• Trench.bot receives approximately 26.3K visitors and 84,264 page impressions per day.

How much Trench.bot can earn?

• Trench.bot should earn about $343.80/day from advertising revenue.

What is Trench.bot estimated value?

• Estimated value of Trench.bot is $334,644.08.

What IP addresses does Trench.bot resolve to?

• Trench.bot resolves to the IP addresses 170.205.24.80.

Where are Trench.bot servers located in?

• Trench.bot has servers located in United States.

trench.bot Profile

Title:TrenchRadar Bundle Viewer
Description:TrenchRadar Bundle Viewer: Interactive bubble maps for Solana token bundles.
Tags:
token visualization
solana
bundle view
trenchradar
crypto tools
blockchain analysis
pumpfun
bubble map
Edit Site Info

What technologies does trench.bot use?

These are the technologies used at trench.bot. trench.bot has a total of 5 technologies installed in 6 different categories.
Web Frameworks
Express Express
Web Servers
Express Express
Nginx Nginx
Reverse proxies
Nginx Nginx
Miscellaneous
Open Graph Open Graph
Operating Systems
Ubuntu Ubuntu
Programming Languages
Node.js Node.js

trench.bot Traffic Analysis

This website is viewed by an estimated 26.3K visitors daily, generating a total of 84.3K pageviews. This equates to about 797.9K monthly visitors. Trench.bot traffic has increased by 64.48% compared to last month.
Daily Visitors26.3K
20.54%
Monthly Visits797.9K
64.48%
Pages per Visit3.20
9.17%
Visit duration16:14
10.89%
Bounce Rate42.08%
13.34%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
26,334
Monthly Visits:
797,920
Pages per Visit:
3.20
Daily Pageviews:
84,264
Avg. visit duration:
16:14
Bounce rate:
42.08%
Global Reach:
0.0005342%
Monthly Visits (SEMrush):
782,198
Monthly Unique Visitors (SEMrush):
133,031
HypeRank:
n/a
SEMrush Rank:
1,204,644
*All traffic values are estimates only.

Traffic sources

Direct:
87.73%
Referral:
1.64%
Search:
6.54%
Social:
4.05%
Paid:
0.04%

Desktop vs Mobile

Desktop:
86.31%
Mobile:
13.69%
Last update was 5 hours ago
     
This can take up to 60 seconds. Please wait...

Update will be available in 19 hours
*HypeStat.com is not promoting or affiliated with trench.bot in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
923

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  trench.bot
Rank:
(Rank based on keywords, cost and organic traffic)
  1,204,644
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  43
Organic Traffic:
(Number of visitors coming from top 20 search results)
  846
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $28.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $343.8 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $10.3K and annual gross revenue of approximately $125.5K. Based on these figures, the site's net worth is estimated at around $334.6K.

How much would trench.bot make?

Daily Revenue:
$343.80
Monthly Revenue:
$10,314.00
Yearly Revenue:
$125,487.00
*All earnings values are estimates only.

How much is trench.bot worth?

Website Value:
$334.6K

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
trench.bot
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
trench.bot
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
trench.bot
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is trench.bot hosted? ▼

Trench.bot may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
170.205.24.80
ASN:
AS399244 
ISP:
BLOOM-HOST  
Server Location:

United States, US
 

Other sites hosted on 170.205.24.80

There are no other sites hosted on this IP

How fast does trench.bot load? ▼

The average loading time of trench.bot is 68 ms. The Desktop speed index is 80 and mobile speed index is 67.
Average Load Time:
68 ms

Page Speed (Google PageSpeed Insights) - Desktop

80
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST 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.

Cumulative Layout Shift (CLS)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)657ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 15% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 15% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.7s 76% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 76% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)83ms 93% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 93% 4% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 4% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.7s 87% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 87% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Origin Data

All pages served from this origin have an FAST 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.

Cumulative Layout Shift (CLS)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)485ms 87% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 87% 10% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 10% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.5s 82% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 82% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)83ms 93% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 93% 4% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 4% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.4s 90% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 90% 6% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 6% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Lab Data

Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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. Learn more about optimal lazy loading
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Total Blocking Time 250 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 Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Time to Interactive 2.0 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
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Largest Contentful Paint 1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 280 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

Page Speed (Google PageSpeed Insights) - Mobile

67
0-49 50-89 90-100 i

Field Data

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.

Cumulative Layout Shift (CLS)6ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 85% 14% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 14% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.1s 82% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 58% 34% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 34% 6% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)2.6s 76% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 57% 21% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 21% 21% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 21%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)197ms 93% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 76% 19% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 19% 3% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 3%
Largest Contentful Paint (LCP)2.6s 87% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 73% 13% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 13% 12% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 12%

Origin Data

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.

Cumulative Layout Shift (CLS)5ms 92% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 92% 7% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 7% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)991ms 64% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 64% 29% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 29% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)2.3s 63% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 63% 20% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 20% 16% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 16%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)221ms 70% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 70% 22% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 22% 6% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 6%
Largest Contentful Paint (LCP)3.0s 67% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 67% 14% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 14% 17% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 17%

Lab Data

Largest Contentful Paint 8.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 8.1 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
Total Blocking Time 270 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
Max Potential First Input Delay 290 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
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
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. Learn more about optimal lazy loading
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Speed Index 4.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does trench.bot 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 trench.bot are reduced by 61%.
trench.bot use gzip compression.
Original size: 1.34 KB
Compressed size: 532 B
File reduced by: 839 B (61%)

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

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:
  UNKNOWN

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 web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. trench.bot supports HTTPS.
 trench.bot supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: trench.bot
Organization:
Location:
Issuer: E5
Valid from: Jan 19 02:39:28 2025 GMT
Valid until: Apr 19 02:39:27 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: E5
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize:

Verify HTTP/2 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.
 trench.bot does not support HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

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. 
Server: nginx/1.24.0 (Ubuntu)
Date: Fri, 28 Feb 2025 04:05:01 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: Express
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: *
Access-Control-Allow-Headers: *
Accept-Ranges: bytes
ETag: W/"55b-g9tg/Qc5fVs9Aos2uQx/6/OiCuM"
Vary: Accept-Encoding
Content-Encoding: gzip
Permissions-Policy: geolocation=(), microphone=(), camera=()

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.
Type Ip Target/Txt TTL
A 170.205.24.80 1617
NS dns2.registrar-servers.com 172618
NS dns1.registrar-servers.com 172618
HINFO 3600