Fangfrisch.At - Info 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 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 This server doesn't support HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Currently Not Available Profile

Last update was 130 days ago
This can take up to 60 seconds. Please wait...

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

How popular is

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
Bounce rate:
*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

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

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

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

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

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

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Hetzner Online GmbH 
Server Location:

Germany, DE

Other sites hosted on

+ How fast does load?

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

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

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

Origin Data

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

Lab Data

Max Potential First Input Delay 40 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.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.0 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.0 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 1.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 350 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.

SizePotential Savings
6 KB110
1 KB150
2 KB230
23 KB310
7 KB190
3 KB150
7 KB190
33 KB270
4 KB110
5 KB110
6 KB110
Efficiently encode images - Potential savings of 539 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
110 KB76 KB
104 KB71 KB
90 KB59 KB
83 KB53 KB
72 KB45 KB
64 KB41 KB
67 KB41 KB
62 KB39 KB
67 KB38 KB
49 KB30 KB
42 KB25 KB
34 KB11 KB
39 KB10 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms208 ms0 KB0 KB301text/html
209 ms698 ms12 KB54 KB200text/htmlDocument
713 ms825 ms6 KB40 KB200text/cssStylesheet
713 ms819 ms1 KB2 KB200text/cssStylesheet
713 ms735 ms2 KB13 KB200text/cssStylesheet
714 ms942 ms23 KB104 KB200text/cssStylesheet
714 ms825 ms7 KB28 KB200text/cssStylesheet
714 ms822 ms3 KB19 KB200text/cssStylesheet
714 ms826 ms7 KB30 KB200text/cssStylesheet
715 ms935 ms33 KB95 KB200application/javascriptScript
715 ms822 ms4 KB10 KB200application/javascriptScript
715 ms821 ms5 KB12 KB200application/javascriptScript
715 ms823 ms6 KB21 KB200application/javascriptScript
716 ms758 ms28 KB73 KB200application/javascriptScript
716 ms824 ms9 KB9 KB200image/pngImage
982 ms1298 ms79 KB80 KB200image/gifImage
982 ms1096 ms11 KB12 KB200image/jpegImage
983 ms1200 ms34 KB36 KB200image/jpegImage
983 ms1207 ms39 KB39 KB200image/jpegImage
983 ms1305 ms64 KB76 KB200image/jpegImage
983 ms1307 ms83 KB83 KB200image/jpegImage
983 ms1305 ms90 KB97 KB200image/jpegImage
983 ms1310 ms42 KB42 KB200image/jpegImage
983 ms1307 ms62 KB68 KB200image/jpegImage
984 ms1300 ms86 KB85 KB200image/pngImage
984 ms1299 ms47 KB48 KB200image/jpegImage
984 ms1205 ms36 KB37 KB200image/jpegImage
984 ms1206 ms28 KB28 KB200image/jpegImage
985 ms1311 ms52 KB52 KB200image/jpegImage
985 ms1310 ms74 KB73 KB200image/jpegImage
985 ms1308 ms81 KB80 KB200image/jpegImage
985 ms1214 ms15 KB15 KB200image/jpegImage
985 ms1095 ms7 KB7 KB200image/jpegImage
985 ms1098 ms9 KB8 KB200image/jpegImage
985 ms1198 ms20 KB20 KB200image/jpegImage
986 ms1208 ms21 KB20 KB200image/jpegImage
986 ms1508 ms21 KB21 KB200image/jpegImage
986 ms1204 ms15 KB15 KB200image/jpegImage
986 ms1504 ms16 KB16 KB200image/jpegImage
986 ms1502 ms19 KB19 KB200image/jpegImage
986 ms1206 ms14 KB14 KB200image/jpegImage
986 ms1207 ms18 KB17 KB200image/jpegImage
986 ms1309 ms67 KB72 KB200image/jpegImage
986 ms1612 ms55 KB57 KB200image/jpegImage
987 ms1406 ms110 KB125 KB200image/jpegImage
987 ms1606 ms67 KB69 KB200image/jpegImage
987 ms1613 ms49 KB69 KB200image/jpegImage
987 ms1260 ms0 KB0 KB301text/html
987 ms1310 ms72 KB88 KB200image/jpegImage
987 ms1404 ms8 KB8 KB200image/pngImage
987 ms1404 ms4 KB4 KB200image/jpegImage
988 ms1107 ms5 KB5 KB200image/jpegImage
988 ms1102 ms3 KB3 KB200image/jpegImage
988 ms1407 ms8 KB8 KB200image/gifImage
759 ms867 ms1 KB2 KB200application/javascriptScript
825 ms932 ms1 KB3 KB200application/javascriptScript
868 ms973 ms1 KB1 KB200application/javascriptScript
933 ms1040 ms4 KB14 KB200application/javascriptScript
981 ms1091 ms16 KB53 KB200application/javascriptScript
981 ms1100 ms6 KB21 KB200application/javascriptScript
982 ms1093 ms2 KB4 KB200application/javascriptScript
982 ms1097 ms1 KB1 KB200application/javascriptScript
982 ms1094 ms1 KB1 KB200application/javascriptScript
988 ms1402 ms5 KB14 KB200application/javascriptScript
1004 ms1008 ms15 KB14 KB200font/woff2Font
1008 ms1623 ms76 KB75 KB200application/octet-streamFont
1009 ms1014 ms19 KB18 KB200font/woff2Font
1012 ms1017 ms15 KB15 KB200font/woff2Font
1105 ms1111 ms18 KB43 KB200text/javascriptScript>m=2ouav9&z=1526084331
1156 ms1161 ms1 KB0 KB200image/gifImage
1195 ms1308 ms1 KB1 KB200image/gifImage
1245 ms1262 ms3 KB3 KB200application/x-javascriptScript
1260 ms1571 ms104 KB120 KB200image/jpegImage
1293 ms1315 ms59 KB194 KB200application/x-javascriptScript
1374 ms1398 ms13 KB37 KB200text/htmlDocument
1692 ms1759 ms17 KB58 KB200text/htmlDocument,cross/R_nNu6ob2q7.css?_nc_x=Ij3Wp8lg5Kz
1775 ms1792 ms8 KB32 KB200text/cssStylesheet
1775 ms1813 ms82 KB313 KB200application/x-javascriptScript
1776 ms1814 ms32 KB113 KB200application/x-javascriptScript
1776 ms1794 ms5 KB14 KB200application/x-javascriptScript
1776 ms1793 ms18 KB18 KB200image/jpegImage
1776 ms1799 ms2 KB2 KB200image/jpegImage
1905 ms1922 ms2 KB1 KB200image/pngImage
1940 ms1956 ms3 KB8 KB200application/x-javascriptScript
2973 ms3010 ms1 KB0 KB200text/htmlXHR
Serve static assets with an efficient cache policy - 52 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms76 KB
1200000 ms3 KB
7200000 ms18 KB
1209600000 ms18 KB
1209600000 ms2 KB
2592000000 ms110 KB
2592000000 ms104 KB
2592000000 ms90 KB
2592000000 ms86 KB
2592000000 ms83 KB
2592000000 ms81 KB
2592000000 ms79 KB
2592000000 ms74 KB
2592000000 ms72 KB
2592000000 ms67 KB
2592000000 ms67 KB
2592000000 ms64 KB
2592000000 ms62 KB
2592000000 ms55 KB
2592000000 ms52 KB
2592000000 ms49 KB
2592000000 ms47 KB
2592000000 ms42 KB
2592000000 ms39 KB
2592000000 ms36 KB
2592000000 ms34 KB
2592000000 ms28 KB
2592000000 ms23 KB
2592000000 ms21 KB
2592000000 ms21 KB
2592000000 ms20 KB
2592000000 ms19 KB
2592000000 ms18 KB
2592000000 ms16 KB
2592000000 ms15 KB
2592000000 ms15 KB
2592000000 ms14 KB
2592000000 ms11 KB
2592000000 ms9 KB
2592000000 ms9 KB
2592000000 ms8 KB
2592000000 ms8 KB
2592000000 ms7 KB
2592000000 ms7 KB
2592000000 ms7 KB
2592000000 ms6 KB
2592000000 ms5 KB
2592000000 ms4 KB
2592000000 ms3 KB
2592000000 ms3 KB
2592000000 ms1 KB
2592000000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
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.

SizeMain-Thread Blocking Time
245 KB0 ms
28 KB0 ms
19 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
727 ms
8 ms
739 ms
41 ms
973 ms
19 ms
1000 ms
17 ms
1018 ms
54 ms
1072 ms
5 ms
1087 ms
36 ms
1123 ms
9 ms
1139 ms
6 ms
1152 ms
32 ms
1183 ms
6 ms
1196 ms
81 ms
1277 ms
8 ms
1297 ms
12 ms
1345 ms
5 ms
1365 ms
19 ms
1386 ms
15 ms
1427 ms
7 ms
1439 ms
7 ms
1447 ms
9 ms
1456 ms
5 ms
1519 ms
10 ms
1529 ms
8 ms
1541 ms
13 ms
1650 ms
69 ms
1720 ms
10 ms
1733 ms
9 ms
1788 ms
7 ms
1800 ms
6 ms
1863 ms
25 ms
1895 ms
8 ms
1903 ms
26 ms
1929 ms
13 ms
1943 ms
25 ms
1970 ms
7 ms
1987 ms
6 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
4 ms
615 ms
5 ms
5 ms
JavaScript execution time - 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.

Total CPU TimeScript EvaluationScript Parse
437 ms14 ms3 ms
155 ms109 ms2 ms
79 ms54 ms8 ms
Minify CSS - Potential savings of 5 KB
Minifying CSS files can reduce network payload sizes. Learn more.

SizePotential Savings
23 KB5 KB
Properly size images - Potential savings of 46 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
67 KB26 KB
21 KB3 KB
20 KB3 KB
20 KB3 KB
19 KB3 KB
5 KB2 KB
17 KB2 KB
16 KB2 KB
15 KB2 KB
Remove unused CSS - Potential savings of 19 KB
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.

SizePotential Savings
23 KB19 KB
Avoids enormous network payloads - Total size was 2,208 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

110 KB
104 KB
90 KB
86 KB
83 KB
82 KB
81 KB
79 KB
76 KB
74 KB
Minimizes main-thread work - 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
346 ms
Style & Layout
178 ms
166 ms
97 ms
Script Parsing & Compilation
55 ms
Parse HTML & CSS
41 ms
Serve images in next-gen formats - Potential savings of 776 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.

SizePotential Savings
110 KB89 KB
104 KB81 KB
85 KB72 KB
90 KB71 KB
83 KB63 KB
72 KB57 KB
67 KB52 KB
67 KB51 KB
64 KB50 KB
62 KB49 KB
49 KB39 KB
42 KB33 KB
55 KB25 KB
34 KB22 KB
39 KB20 KB
Avoids an excessive DOM size - 513 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Minify JavaScript - Potential savings of 4 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

SizePotential Savings
16 KB4 KB
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 85 requests • 2,208 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
852208 KB
451666 KB
22318 KB
4124 KB
856 KB
342 KB
32 KB
00 KB
21342 KB
Server response times are low (TTFB) - Root document took 490 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.

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.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. 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.

Avoid chaining critical requests - 24 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.

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.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 890.1KiB (49% reduction).

Compressing could save 100.7KiB (80% reduction).
Compressing could save 95.6KiB (79% reduction).
Compressing could save 74.8KiB (77% reduction).
Compressing could save 67.6KiB (76% reduction).
Compressing could save 61.8KiB (74% reduction).
Compressing could save 59.7KiB (78% reduction).
Compressing could save 53.9KiB (78% reduction).
Compressing could save 51KiB (75% reduction).
Compressing could save 50.9KiB (70% reduction).
Compressing could save 49.5KiB (71% reduction).
Compressing could save 29.5KiB (70% reduction).
Compressing could save 18.8KiB (52% reduction).
Compressing could save 17.5KiB (46% reduction).
Compressing could save 16.5KiB (18% reduction).
Compressing could save 16.3KiB (24% reduction).
Compressing could save 14.8KiB (16% reduction).
Compressing could save 14.6KiB (26% reduction).
Compressing could save 13.3KiB (22% reduction).
Compressing could save 13.3KiB (17% reduction).
Compressing could save 13.1KiB (16% reduction).
Compressing could save 12KiB (17% reduction).
Compressing could save 10.9KiB (19% reduction).
Compressing could save 8.1KiB (16% reduction).
Compressing could save 6.6KiB (19% reduction).
Compressing could save 5.2KiB (20% reduction).
Compressing could save 4.5KiB (39% reduction).
Compressing could save 3.2KiB (19% reduction).
Compressing could save 2.7KiB (18% reduction).
Compressing could save 1.5KiB (17% reduction).
Compressing could save 1.2KiB (16% reduction).
Compressing https://static.*** could save 518B (37% reduction).
Compressing https://scontent-atl3-1.******&oh=d4daf209be9fb88d64a3a353ec1e3a3e&oe=5E4633E8 could save 467B (25% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://www.fa…im-mittelmeer/" class="post-title">Schleppfischen…im Mittelmeer</a> and 5 others are close to other tap targets .
The tap target <a href="https://www.fa…edens/#respond">0</a> and 7 others are close to other tap targets.
The tap target <a href="https://www.fa…edens/#respond">0</a> and 7 others are close to other tap targets.
The tap target <a href="https://www.fa…lmeer/#respond">0</a> and 2 others are close to other tap targets.
The tap target <a href="https://www.fa…lmeer/#respond">0</a> and 2 others are close to other tap targets.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (15 minutes) (20 minutes)******ytics.js (2 hours)

Reduce server response time

In our test, your server responded in 0.34 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 7.2KiB (26% reduction).

Minifying could save 5.6KiB (26% reduction) after compression.
Minifying could save 1.6KiB (26% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 5.9KiB (24% reduction).

Minifying could save 3.6KiB (23% reduction) after compression.
Minifying could save 671B (39% reduction) after compression.
Minifying could save 653B (17% reduction) after compression.
Minifying could save 552B (49% reduction) after compression.
Minifying could save 328B (61% reduction) after compression.
Minifying could save 174B (13% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? does not use compression.
Original size: n/a
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify does not support HTTPS
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Currently Not Available

+ DNS Lookup

Type Ip Target TTL
MX 3600
A 3600
SOA 3600
Serial Number 2019100301
Refresh 14400
Retry 1800
Expire 604800
Minimum TTL 0
NS 3562
NS 3562
NS 3562

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
% Copyright (c)2019 by NIC.AT (1)
% Restricted rights.
% Except for agreed Internet operational purposes, no part of this
% information may be reproduced, stored in a retrieval system, or
% transmitted, in any form or by any means, electronic, mechanical,
% recording, or otherwise, without prior permission of NIC.AT on behalf
% of itself and/or the copyright holders. Any use of this material to
% target advertising or similar activities is explicitly forbidden and
% can be prosecuted.
% It is furthermore strictly forbidden to use the Whois-Database in such
% a way that jeopardizes or could jeopardize the stability of the
% technical systems of NIC.AT under any cir***stances. In particular,
% this includes any misuse of the Whois-Database and any use of the
% Whois-Database which disturbs its operation.
% Should the user violate these points, NIC.AT reserves the right to
% deactivate the Whois-Database entirely or partly for the user.
% Moreover, the user shall be held liable for any and all damage
% arising from a violation of these points.

registrar: Key-Systems GmbH ( )
registrant: OA9130565-NICAT
tech-c: KG12093025-NICAT
changed: 20191030 15:13:44
source: AT-DOM

personname: Marcus Stark
organization: Oesterreichischer Agrarverlag
street address: Sturzgasse 1a
postal code: A-1140
city: Wien
country: Austria
phone: +4319823344465
fax-no: +439823344259
e-mail: email
nic-hdl: OA9130565-NICAT
changed: 20140429 14:30:22
source: AT-DOM

personname: Domain Admin
organization: Key-Systems GmbH
street address: Im Oberen Werk 1
postal code: 66386
city: St. Ingbert
country: Germany
phone: +4968949396850
fax-no: +4968949396851
e-mail: email
nic-hdl: KG12093025-NICAT
changed: 20181121 10:53:17
source: AT-DOM
Last update was 130 days ago
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites
9 secs
48 secs
1 min
1 min
1 min
1 min
2 mins
2 mins
2 mins
2 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


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) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget