f49i.Ir - Info f49i.ir

f49i.ir receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank f49i.ir is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Germany and links to network IP address 138.201.202.183. This server doesn't support HTTPS and doesn't support HTTP/2.

About - f49i.ir


Technologies used on Website

Web Servers
Apache
Programming Languages
PHP

f49i.ir Profile

Title: سایت همسریابی ازدواج دائم و موقت نازیار
Description: همسریابی نازیار با بیش از پانصد هزار عضو از سرتاسر ایران آماده ازدواج دائم و همچنین ازدواج موقت (صیغه یابی) است و سامانه نازیار فعالیتی در زمینه دوستیابی نداردو فعالیت نازیار فقط به همسریابی موقت ودائم محدود میگردد
Keywords: ‌سایت همسریابی,همسريابي,همسر يابي آنلاين,بزرگترین سایت همسریابی,همسریابی ناز یار,نازیار,سایت نازیار,همسريابي آنلاين,صیغه یابی,ilsvdhfd,shdj ilsvdhfd,سايت همسريابي تهران,ثبتنام در همسریابی,ازدواج آنلاین,ازدواج,ازدواج دائم,همسریابی موقت,ازدواج موقت,سایت همسریابی موقت,سایت ازدواج,همسریابی رایگان,شوهریابی,ازدواج دائم,همسان گزينی,بهترين سايت همسر يابي آنلاين,همسريابي,سايت همسريابي رايگان,ازدواج ساعتی,همسریابی اینترنتی,شوهریابی اینترنتی,آدرس جدید سایت ناز یار
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with f49i.ir in any way. Only publicly available statistics data are displayed.

How popular is f49i.ir?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  f49i.ir
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is f49i.ir?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

Root domain:
f49i.ir
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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

Root domain:
f49i.ir
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

+ How much f49i.ir can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do f49i.ir lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is f49i.ir worth?

Website Value:
n/a

+ Where is f49i.ir hosted?

Server IP:
138.201.202.183
ASN:
AS24940 
ISP:
Hetzner Online GmbH 
Server Location:

Germany, DE
 

Other sites hosted on 138.201.202.183

There are no other sites hosted on this IP

+ How fast does f49i.ir load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

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

First Contentful Paint (FCP)1.7s 46% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 46% 44% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 44% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)6ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.

First Contentful Paint (FCP)1.7s 46% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 46% 44% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 44% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)6ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

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 more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
933 ms
9 ms
1056 ms
10 ms
1066 ms
19 ms
1379 ms
8 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
60 ms3 ms1 ms
Avoids enormous network payloads - Total size was 152 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://58e.ir/themes/nazyar/imgs/outside.png
126 KB
http://58e.ir/themes/nazyar/font/Yekan.ttf
20 KB
http://58e.ir/
3 KB
http://58e.ir/themes/nazyar/css/outside.css
3 KB
http://f49i.ir/
1 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
30 ms
Other
19 ms
Rendering
5 ms
Script Evaluation
4 ms
Parse HTML & CSS
3 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 77 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://58e.ir/themes/nazyar/imgs/outside.png
126 KB77 KB
Avoids an excessive DOM size - 80 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
80
Maximum DOM Depth
12
Maximum Child Elements
7
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://f49i.ir/)
0
http://58e.ir/
190
Keep request counts low and transfer sizes small - 5 requests • 152 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
5152 KB
Image
1126 KB
Font
120 KB
Document
13 KB
Stylesheet
13 KB
Other
11 KB
Media
00 KB
Script
00 KB
Third-party
11 KB
Eliminate render-blocking resources - Potential savings of 60 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://58e.ir/themes/nazyar/css/outside.css
3 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://f49i.ir/
0 ms449 ms1 KB0 KB301text/html
http://58e.ir/
449 ms909 ms3 KB6 KB200text/htmlDocument
http://58e.ir/themes/nazyar/css/outside.css
923 ms1032 ms3 KB10 KB200text/cssStylesheet
http://58e.ir/themes/nazyar/imgs/outside.png
1037 ms1555 ms126 KB126 KB200image/pngImage
http://58e.ir/themes/nazyar/font/Yekan.ttf
1042 ms1355 ms20 KB37 KB200application/x-font-ttfFont
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://58e.ir/themes/nazyar/css/outside.css
604800000 ms3 KB
http://58e.ir/themes/nazyar/imgs/outside.png
4838400000 ms126 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 460 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

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

First Contentful Paint (FCP)2.9s 46% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 24% 51% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 51% 24% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 24%
First Input Delay (FID)28ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 2% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 2% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.

First Contentful Paint (FCP)2.0s 39% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 39% 47% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 47% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
First Input Delay (FID)26ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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 more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 2790 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 80 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
80
Maximum DOM Depth
12
Maximum Child Elements
7
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://f49i.ir/)
0
http://58e.ir/
630
Keep request counts low and transfer sizes small - 5 requests • 152 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
5152 KB
Image
1126 KB
Font
120 KB
Document
13 KB
Stylesheet
13 KB
Other
11 KB
Media
00 KB
Script
00 KB
Third-party
11 KB
Eliminate render-blocking resources - Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://58e.ir/themes/nazyar/css/outside.css
3 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://f49i.ir/
0 ms453 ms1 KB0 KB301text/html
http://58e.ir/
453 ms917 ms3 KB6 KB200text/htmlDocument
http://58e.ir/themes/nazyar/css/outside.css
931 ms1368 ms3 KB10 KB200text/cssStylesheet
http://58e.ir/themes/nazyar/imgs/outside.png
1373 ms1892 ms126 KB126 KB200image/pngImage
http://58e.ir/themes/nazyar/font/Yekan.ttf
1378 ms1691 ms20 KB37 KB200application/x-font-ttfFont
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://58e.ir/themes/nazyar/css/outside.css
604800000 ms3 KB
http://58e.ir/themes/nazyar/imgs/outside.png
4838400000 ms126 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
946 ms
9 ms
1396 ms
9 ms
1405 ms
18 ms
1719 ms
9 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
235 ms9 ms5 ms
Avoids enormous network payloads - Total size was 152 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://58e.ir/themes/nazyar/imgs/outside.png
126 KB
http://58e.ir/themes/nazyar/font/Yekan.ttf
20 KB
http://58e.ir/
3 KB
http://58e.ir/themes/nazyar/css/outside.css
3 KB
http://f49i.ir/
1 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
113 ms
Other
77 ms
Rendering
21 ms
Script Evaluation
12 ms
Parse HTML & CSS
10 ms
Script Parsing & Compilation
5 ms
Serve images in next-gen formats - Potential savings of 77 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://58e.ir/themes/nazyar/imgs/outside.png
126 KB77 KB
Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 460 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does f49i.ir use compression?

f49i.ir use gzip compression.
Original size: 6.09 KB
Compressed size: 2.55 KB
File reduced by: 3.54 KB (58%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

f49i.ir does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

f49i.ir does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 22 May 2020 23:52:03 GMT
Server: Apache/2
Set-Cookie: 56503f49iir=ok6pnnnucutfl62tlglkg46pl3; path=/; domain=.f49i.ir; HttpOnly
Location: http://58e.ir/
Content-Encoding: gzip
Vary: Accept-Encoding,User-Agent
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Expires: 0
Content-Length: 20
Content-Type: text/html; charset=utf-8

HTTP/1.1 200 OK
Date: Fri, 22 May 2020 23:52:04 GMT
Server: Apache/2
X-Powered-By: PHP/5.6.36
Set-Cookie: 5650358eir=fvauie9doer7liievi39baohu5; path=/; domain=.58e.ir; HttpOnly
Expires: 0
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Last-Modified: Fri, 22 May 2020 23:52:04 GMT
Content-Encoding: gzip
Vary: Accept-Encoding,User-Agent
Content-Length: 2611
Content-Type: text/html; charset=utf-8

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname ns1.wend.ir
Rname hostmaster.f49i.ir
Serial Number 2020051200
Refresh 14400
Retry 3600
Expire 1209600
Minimum TTL 0
TXT 3600
MX mail.f49i.ir 3600
A 138.201.202.183 3508
NS ns1.wend.ir 1348
NS ns2.wend.ir 1348

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with f49i.ir in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

socialpros.co
14 secs
premium.iearn01.com
17 secs
thegourmetrd.com
42 secs
socialpress.ir
1 min
ratanak.org
1 min
socialdiscourse.ir
2 mins
fitafter50.com
2 mins
socgu.blogfa.com
3 mins
socialapk.com
3 mins
geardiary.com
3 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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.
Make custom Widget for your website
Get the code now!
f49i.ir widget