wochenanzeiger.de Wochenanzeiger.de

   
Aktuelle Nachrichten, Events & Kleinanzeigen in deiner Region | Wochenanzeiger

Domain Summary

What is the traffic rank for Wochenanzeiger.de?

• Wochenanzeiger.de ranks #2,782,092 globally on HypeStat.

What percent of global Internet users visit Wochenanzeiger.de?

• 6.16E-5% of global Internet users visit Wochenanzeiger.de

How many people visit Wochenanzeiger.de each day?

• Wochenanzeiger.de receives approximately 3K visitors and 4,860 page impressions per day.

Which countries does Wochenanzeiger.de receive most of its visitors from?

• Wochenanzeiger.de is mostly visited by people located in Germany,Switzerland,United States.

How much Wochenanzeiger.de can earn?

• Wochenanzeiger.de should earn about $7.48/day from advertising revenue.

What is Wochenanzeiger.de estimated value?

• Estimated value of Wochenanzeiger.de is $6,833.17.

What IP addresses does Wochenanzeiger.de resolve to?

• Wochenanzeiger.de resolves to the IP addresses 212.18.23.204.

Where are Wochenanzeiger.de servers located in?

• Wochenanzeiger.de has servers located in Munich, Bavaria, 81477, Germany.

wochenanzeiger.de Profile

Title:Aktuelle Nachrichten, Events & Kleinanzeigen in deiner Region | Wochenanzeiger Description:Hallo München - Der Münchner Wochenanzeiger: Ihre Wochenzeitung für aktuelle Nachrichten, lokale Ereignisse, Angebote und Events in München.
Tags:
Category:News and Media / News and Media
About: Wochenanzeiger.de is a comprehensive online platform that serves as a local news and information hub primarily for German-speaking communities. Its primary purpose is to provide users with access to news articles, event listings, and advertisements tailored to regional interests. Key features include a user-friendly interface that facilitates easy navigation through various categories such as local news, culture, sports, and classifieds. The site emphasizes accessibility, offering responsive design elements that cater to both desktop and mobile users. Additionally, Wochenanzeiger.de fosters community engagement by allowing users to submit events and share local happenings, thus enhancing its role as a vital resource for community connection.
Edit Site Info

What technologies does wochenanzeiger.de use?

These are the technologies used at wochenanzeiger.de. wochenanzeiger.de has a total of 6 technologies installed in 7 different categories.

wochenanzeiger.de Traffic Analysis

Wochenanzeiger.de is ranked #2,782,092 in the world. This website is viewed by an estimated 3K visitors daily, generating a total of 4.9K pageviews. This equates to about 91.9K monthly visitors. Wochenanzeiger.de traffic has increased by 20.09% compared to last month.
Daily Visitors3K
12.22%
Monthly Visits91.9K
20.09%
Pages per Visit1.60
0.2%
Visit duration00:47
619.18%
Bounce Rate72.04%
2.15%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
3,034
Monthly Visits:
91,930
Pages per Visit:
1.60
Daily Pageviews:
4,860
Avg. visit duration:
00:47
Bounce rate:
72.04%
Global Reach:
6.16E-5%
Monthly Visits (SEMrush):
59,460
Monthly Unique Visitors (SEMrush):
48,128
Monthly Visits (SimilarWeb):
90,131
HypeRank:
2,782,092
SEMrush Rank:
6,929,904
SimilarWeb Rank:
485,726
*All traffic values are estimates only.

Traffic sources

Direct:
41.69%
Referral:
11.95%
Search:
45.66%
Social:
0.70%
Paid:
0%

Desktop vs Mobile

Desktop:
50.58%
Mobile:
49.42%

Total Visits Last 3 Months

82.1K
MAY
76.6K
JUN
91.9K
JUL

Visitors by country

Country
Users%
 
Germany 95.76%
 
Switzerland 1.90%
 
United States 1.62%
 
Austria 0.65%
 
Pakistan 0.04%

  ▼

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:
  wochenanzeiger.de
Rank:
(Rank based on keywords, cost and organic traffic)
  6,929,904
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  106
Organic Traffic:
(Number of visitors coming from top 20 search results)
  17
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $6.00

Which sites are competitors to wochenanzeiger.de?

Websites similar to wochenanzeiger.de 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.
Last update was 24 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with wochenanzeiger.de 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:
169,000
Bing Index:
2,340

Revenue report ▼

wochenanzeiger.de would generate approximately $7.5 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $224.4 and annual gross revenue of approximately $2.7K. Based on these figures, the site's net worth is estimated at around $6.8K.

How much would wochenanzeiger.de make?

Daily Revenue:
$7.48
Monthly Revenue:
$224.40
Yearly Revenue:
$2,730.20
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Germany 4,654$6.52
 
Switzerland 92$0.51
 
United States 79$0.38
 
Austria 31$0.06
 
Pakistan 2$0.00

Loss of money due to Adblock?

Daily Revenue Loss:
$2.07
Monthly Revenue Loss:
$62.00
Yearly Revenue Loss:
$754.36
Daily Pageviews Blocked:
1,389
Monthly Pageviews Blocked:
41,675
Yearly Pageviews Blocked:
507,046

Daily revenue loss by country

 
CountryBlockedLost Money
 
Germany 1,350$1.89
 
Switzerland 17$0.09
 
United States 14$0.07
 
Austria 8$0.02
 
Pakistan 1$0.00

How much is wochenanzeiger.de worth?

Website Value:
$6.8K

Ad Experience Report ▼

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

Mobile summary

Root domain:
wochenanzeiger.de
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:
wochenanzeiger.de
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:
wochenanzeiger.de
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 wochenanzeiger.de hosted? ▼

Wochenanzeiger.de may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
212.18.23.204
ASN:
AS8767 
ISP:
M-net Telekommunikations GmbH 
Server Location:
Munich
Bavaria, BY
81477
Germany, DE
 

Other sites hosted on 212.18.23.204

How fast does wochenanzeiger.de load? ▼

The average loading time of wochenanzeiger.de is 1027 ms. The Desktop speed index is 91 and mobile speed index is 77.
Average Load Time:
1027 ms

Page Speed (Google PageSpeed Insights) - Desktop

91
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)10ms 72% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 72% 23% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 23% 4% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 4%
Time To First Byte (TTFB)1.3s 9% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 9% 79% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 79% 11% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 11%
First Contentful Paint (FCP)1.4s 84% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 84% 10% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 10% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)2ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)30ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.5s 91% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 91% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

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% 5% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 5% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)961ms 71% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 71% 23% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 23% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.1s 92% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 92% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)2ms 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%
Interaction To Next Paint (INP)32ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.1s 96% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 96% 2% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 2% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Largest Contentful Paint 1.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
Total Blocking Time 0 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
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
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
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
Time to Interactive 0.8 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

Page Speed (Google PageSpeed Insights) - Mobile

77
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)0ms 72% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 98% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.4s 9% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 12% 76% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 76% 10% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 10%
First Contentful Paint (FCP)1.7s 84% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 80% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)13ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 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%
Interactive To Next Paint (INP)77ms 99% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 98% 0% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 0% 1% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.7s 91% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 92% 5% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 5% 2% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 2%

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)0ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 94% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)757ms 76% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 76% 19% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 19% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.1s 92% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 92% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)12ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)69ms 97% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 97% 1% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 1% 0% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.1s 96% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 96% 2% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 2% 0% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 0%

Lab Data

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
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 0 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
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 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
Largest Contentful Paint 3.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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
First Contentful Paint 2.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 Index 7.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 3.2 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
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

Does wochenanzeiger.de 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 wochenanzeiger.de are reduced by 82%.
wochenanzeiger.de use br compression.
Original size: 378.59 KB
Compressed size: 68.01 KB
File reduced by: 310.58 KB (82%)

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. wochenanzeiger.de has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  9

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. wochenanzeiger.de supports HTTPS.
 wochenanzeiger.de supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.wochenanzeiger.de
Organization:
Location:
Issuer: YR2
Valid from: Jul 24 00:17:39 2026 GMT
Valid until: Oct 22 00:17:38 2026 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: YR2
Organization: Let's Encrypt
Location: US
Issuer: Root YR
Valid from: Sep 3 00:00:00 2025 GMT
Valid until: Sep 2 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Root YR
Organization: ISRG
Location: US
Issuer: ISRG Root X1
Valid from: May 13 00:00:00 2026 GMT
Valid until: Sep 2 23:59:59 2032 GMT
Authority: CA:TRUE
Keysize: 4096 Bits

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.
 wochenanzeiger.de supports 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.18.0
date: Tue, 01 Sep 2026 10:29:35 GMT
content-type: text/html
content-length: 169
location: https://www.wochenanzeiger.de/

HTTP/2 200 
server: nginx/1.18.0
date: Tue, 01 Sep 2026 10:29:36 GMT
content-type: text/html; charset=utf-8
x-powered-by: Express
access-control-allow-origin: *
etag: W/"5ea5e-DCr+UAl0BIjaSy4Oj8eDs8eoymk"
vary: Accept-Encoding
content-encoding: br
set-cookie: connect.sid=s%3AG2rM_bKjLXXPpPX1KdGGo8bnBmru7dY4.M3xXhC7I2zsxLF4E2kR3pjVnkLWlMslRSkOjYl2Scvk; Path=/; Expires=Tue, 15 Sep 2026 10:29:36 GMT; HttpOnly

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
TXT v=spf1 mx ip4:82.135.8.73 include:spf.turbo-smtp.com include:turbo-smtp.com ~all 300
TXT MS=ms53311438 300
NS ns.link-m.de 300
NS ns.ipn.de 300
A 212.18.23.204 300
MX proxmox.haiberg.net 300
SOA 300
Mname ns.link-m.de
Rname hostmaster.link-m.de
Serial Number 2026030401
Refresh 28800
Retry 3600
Expire 864000
Minimum TTL 86400

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information.
Domain Updated:
2007-07-31
WhoIs:
 

% Restricted rights.
% 
% Terms and Conditions of Use
% 
% The above data may only be used within the scope of technical or
% administrative necessities of Internet operation or to remedy legal
% problems.
% The use for other purposes, in particular for advertising, is not permitted.
% 
% The DENIC whois service on port 43 doesn't disclose any information concerning
% the domain holder, general request and abuse contact.
% This information can be obtained through use of our web-based whois service
% available at the DENIC website:
% http://www.denic.de/en/domains/whois-service/web-whois.html
% 
% 

Domain: wochenanzeiger.de
Nserver: ns.ipn.de
Nserver: ns.link-m.de
Status: connect
Changed: 2007-07-31T15:08:23+02:00