dw.com
dw.com is a live website, registered in 1994, served from Troisdorf, Germany. It has a valid HTTPS certificate, 2 of 6 common security headers.
Does dw.com publish the usual trust pages?
None of about, contact, privacy or terms could be found at their usual addresses. That is common for small or single-purpose sites, and it is also what a disposable site looks like, so it is worth noting rather than concluding from. These were checked at conventional paths only, so a site using different URLs may publish them elsewhere.
How does dw.com compare with other domains analysed here?
Measured against the 79 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 78% of them (median 657ms) |
|---|---|
| Security headers | More than 89% of them |
| Domain age | Older than 97% of them |
Related domains in this index
Other analysed domains served from the same country:
When was dw.com registered?
dw.com was registered on 7 December 1994, which makes it about 31 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is HTTP.NET INTERNET GMBH.
Registration runs until 6 December 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 7 December 1994 |
|---|---|
| Expires | 6 December 2027 |
| Registrar | HTTP.NET INTERNET GMBH |
| Registry status | client transfer prohibited |
Where is dw.com hosted?
The first address resolves to infrastructure in Troisdorf, Germany.
The network is operated by Deutsche Welle Anstalt des Oeffentlichen Rechts (AS200777 Deutsche Welle Anstalt des Oeffentlichen Rechts).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is dw.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of dw.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 166ms to first byte this response is fast for a homepage measured from a single European location.
At 12KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 12,072 bytes |
| Declared language | not declared |
| Mobile viewport | declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is dw.com served over a valid certificate?
The HTTPS certificate is issued by DigiCert Inc and is valid until 2027-03-20, which is 167 days from the date of this check. It covers 2 hostnames.
- *.dw.com
- dw.com
The certificate has 167 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
2 of 6 are set (HSTS, Content Security Policy). Absent: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000 |
| Content Security Policy | yes | frame-ancestors 'none' |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for dw.com?
| IP addresses | 194.55.30.46, 194.55.26.46 |
|---|---|
| Reverse DNS | hoelderlin.dwelle.de, hoelderlin.dwelle.de |
| Name servers | voltaire.dwelle.de, dns3.netcologne.de, dns4.netcologne.de, dns5.netcologne.de |
| Mail (MX) | dw-com.mail.protection.outlook.com (pri 10) |
| SPF | v=spf1 ip4:194.55.30.155 ip4:194.55.30.156 ip4:194.55.26.155 ip4:194.55.26.156 ip4:81.209.250.80 ip4:81.209.250.76 ip4:81.209.250.78 ip4:83.133.243.211 ip4:185.17.245.132 ip4:185.17.245.28 include:spf.umantis.com include:spf.de.umantis.com include:spf.protection.outlook.com include:spf1.checkinserver.com include:spf.vizito.be include:spf.send.business-beat.eu -all |
| TXT records | 10 |
dw.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to hoelderlin.dwelle.de, hoelderlin.dwelle.de, which usually names the hosting provider.
Who runs DNS and mail for dw.com?
Mail is handled by Microsoft 365.
No AAAA records are published, so the site is reachable over IPv4 only.
Can dw.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What else does dw.com publish?
An ads.txt file is published with 182 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.
What does robots.txt allow?
robots.txt is 2,843 bytes and names 54 user-agent groups. It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.dw.com/sitemap.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | blocked |
| claudebot | blocked |
| perplexitybot | blocked |
| google-extended | blocked |
| ccbot | blocked |
| applebot-extended | blocked |
| bytespider | blocked |
| anthropic-ai | blocked |
1 sitemap is declared in robots.txt, which gives crawlers a direct list of URLs.
Every named AI crawler is blocked (gptbot, claudebot, perplexitybot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai). This domain has opted out of AI training and AI answer surfaces wholesale.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does dw.com load from third parties?
The homepage loads no resources from third-party hosts at all, which is rare and means visiting it tells no other company that you did.
No cookies are set on first load.
Does dw.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both dw.com and www.dw.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can dw.com be crawled?
A sitemap index is served at https://www.dw.com/sitemap.xml listing 217 entries.
The most recent lastmod date is 2026-10-04.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does dw.com run?
No analytics or advertising trackers were detected on the homepage of dw.com, which is unusual for a commercial site.
How does dw.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
How are images, fonts and scripts handled?
The page pulls 1 external stylesheet and 1 external script, with 0 carrying defer or async.
Responses carry Akamai edge headers, so content is served from a CDN rather than straight from the origin.
Is dw.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index dw.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
Visible text is only 0.4% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is dw.com delivered?
The HTML is served with Cache-Control: public, max-age=120, s-maxage=300.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
Frequently asked questions
Does dw.com set the usual HTTP security headers?
It sets 2 of 6. The ones not present are: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Does dw.com allow AI crawlers?
No — robots.txt blocks gptbot, claudebot, perplexitybot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own dw.com and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →