myaudi.de Myaudi.de

   
Welcome to myAudi

Domain Summary

What percent of global Internet users visit Myaudi.de?

• 5.0E-7% of global Internet users visit Myaudi.de

How many people visit Myaudi.de each day?

• Myaudi.de receives approximately 25 visitors and 25 page impressions per day.

How much Myaudi.de can earn?

• Myaudi.de should earn about $0.10/day from advertising revenue.

What is Myaudi.de estimated value?

• Estimated value of Myaudi.de is $84.55.

What IP addresses does Myaudi.de resolve to?

• Myaudi.de resolves to the IP addresses 54.74.124.230.

Where are Myaudi.de servers located in?

• Myaudi.de has servers located in Dublin, Leinster, D02, Ireland.

myaudi.de Profile

Title:Welcome to myAudi Description:myAudi gives you access to all the digital services from Audi
Edit Site Info

What technologies does myaudi.de use?

These are the technologies used at myaudi.de. myaudi.de has a total of 4 technologies installed in 4 different categories.
CDN
Amazon Cloudfront Amazon Cloudfront
UI frameworks
Bootstrap Bootstrap
Miscellaneous
Open Graph Open Graph
PaaS
Amazon Web Services Amazon Web Services

myaudi.de Traffic Analysis

This website is viewed by an estimated 25 visitors daily, generating a total of 25 pageviews. This equates to about 757.5 monthly visitors.
Daily Visitors25
Monthly Visits757.5
Pages per Visit1.00
Visit duration n/a
Bounce Rate100.00%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
25
Monthly Visits:
758
Pages per Visit:
1.00
Daily Pageviews:
25
Avg. visit duration:
n/a
Bounce rate:
100.00%
Global Reach:
5.0E-7%
Monthly Visits (SEMrush):
722
Monthly Unique Visitors (SEMrush):
361
HypeRank:
n/a
*All traffic values are estimates only.

Traffic sources

Direct:
100.00%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%
Last update was 197 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with myaudi.de in any way. Only publicly available statistics data are displayed.

  ▼

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:
  myaudi.de
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
Full SEMrush Report >>

Revenue report ▼

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

How much would myaudi.de make?

Daily Revenue:
$0.10
Monthly Revenue:
$3.00
Yearly Revenue:
$36.50
*All earnings values are estimates only.

How much is myaudi.de worth?

Website Value:
$84.6

Ad Experience Report ▼

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

Mobile summary

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

Myaudi.de may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
54.74.124.230
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Dublin
Leinster, L
D02
Ireland, IE
 

Other sites hosted on 54.74.124.230

There are no other sites hosted on this IP

How fast does myaudi.de load? ▼

The average loading time of myaudi.de is 344 ms. The Desktop speed index is 82 and mobile speed index is 49.
Average Load Time:
344 ms

Page Speed (Google PageSpeed Insights) - Desktop

82
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)0ms 100% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 100% 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)405ms 86% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 86% 10% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 10% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)943ms 91% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 91% 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)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)21ms 100% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 100% 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)954ms 97% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 97% 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%

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 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 95% 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)484ms 85% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 85% 12% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 12% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)719ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
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)32ms 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.8s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Lab Data

Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Time to Interactive 2.4 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
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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
Total Blocking Time 160 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
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Modern HTTP  
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 360 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
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Page Speed (Google PageSpeed Insights) - Mobile

49
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)0ms 100% 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)719ms 86% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 77% 14% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 14% 7% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)1.5s 91% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 80% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
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)80ms 100% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 97% 2% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 2% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.5s 97% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 89% 7% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 7% 3% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 3%

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)2ms 86% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 86% 4% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 4% 9% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 9%
Time To First Byte (TTFB)850ms 73% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 73% 22% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 22% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)924ms 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 90% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
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)91ms 95% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 95% 3% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 3% 0% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.4s 78% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 78% 16% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 16% 4% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 4%

Lab Data

Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
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
Speed Index 6.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Max Potential First Input Delay 350 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
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
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
Total Blocking Time 510 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
Time to Interactive 10.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
Largest Contentful Paint 6.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Modern HTTP  
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
First Contentful Paint 6.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Does myaudi.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 myaudi.de are reduced by 88%.
myaudi.de use gzip compression.
Original size: 174.51 KB
Compressed size: 20.86 KB
File reduced by: 153.64 KB (88%)

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. myaudi.de has 89 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  89
Safety Confidence:
  15

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. myaudi.de supports HTTPS.
 myaudi.de supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: my.audi.com
Organization: Audi AG
Location: Ingolstadt, DE
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from: Jul 18 00:00:00 2024 GMT
Valid until: Jul 17 23:59:59 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: my.audi.com
Organization: Audi AG
Location: Ingolstadt, DE
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from: Jul 18 00:00:00 2024 GMT
Valid until: Jul 17 23:59:59 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root G2
Valid from: Mar 30 00:00:00 2021 GMT
Valid until: Mar 29 23:59:59 2031 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: DigiCert Global Root G2
Organization: DigiCert Inc, OU = www.digicert.com
Location: US
Issuer: DigiCert Global Root G2
Valid from: Aug 1 12:00:00 2013 GMT
Valid until: Jan 15 12:00:00 2038 GMT
Authority: CA:TRUE
Keysize: 2048 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.
 myaudi.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.26.2
Date: Thu, 01 May 2025 22:33:02 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive
Location: https://my.audi.com
X-Frame-Options: SAMEORIGIN

HTTP/2 302 
server: CloudFront
date: Thu, 01 May 2025 22:33:02 GMT
content-length: 0
location: https://my.audi.com/region-selector/
x-cache: FunctionGeneratedResponse from cloudfront
via: 1.1 48ae30b385d6a5d01d175d0518196f70.cloudfront.net (CloudFront)
x-amz-cf-pop: ORD58-P12
x-amz-cf-id: atD0oxe9Pz-azgjEeAdNDMveZryQGwoL6YwKgg7qg4HipilrHCijOA==

HTTP/2 200 
content-type: text/html
x-amz-cf-pop: ORD58-P9
server: CloudFront
date: Thu, 01 May 2025 22:13:55 GMT
content-encoding: gzip
cache-control: public, max-age=10800, s-maxage=300, stale-while-revalidate=31536000, stale-if-error=31536000
etag: "2ba07-srE3erh9rdNqrTEf0D8B3IrczFk"
x-amzn-trace-id: Root=1-6813f222-01d684065c90a2d4235a6db8;Parent=5e9d4e156fd72339;Sampled=0;Lineage=1:34a40f7e:0
via: 1.1 3e7e3901bf50d3bb955abab1f1f4010e.cloudfront.net (CloudFront), 1.1 48ae30b385d6a5d01d175d0518196f70.cloudfront.net (CloudFront)
x-age: 1070
x-amzn-requestid: 1a3d1a97-f4f1-49f3-919a-5edb0df821d9
vary: Accept-Encoding
x-cache: Hit from cloudfront
x-amz-cf-pop: ORD58-P12
x-amz-cf-id: cVaAX_t0wDGSqbCPwEf6_ue6ev5lyA0t_CO5nLdUMVuElgj7hXRHRA==
age: 1147

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
SOA 3600
Mname ns.audi.de
Rname domainservice.audi.de
Serial Number 2024082001
Refresh 10000
Retry 1800
Expire 604800
Minimum TTL 600
TXT QuoVadis=2bcaa596-b868-42aa-9e43-8200508c073d 3600
TXT _91viwlgw2fwvietff4zmru2nushrvyr 3600
TXT 5gxwzr3ls14ff79w2r5ywvyt2w6870zb 3600
TXT mjdmg88ptl77g0fh0q72276mbvvzfcz8 3600
TXT w9nv9b7ly1jb7z73973y0n0m2qvm41xk 3600
TXT QuoVadis=cbb09816-5d53-43c0-a8cb-c878cfde8a86 3600
MX mailin3.audi.de 3600
MX mailin4.audi.de 3600
A 54.74.124.230 3512
NS ns2.audi.de 3600
NS ns5.xc-ns.de 3600

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:
2011-10-13
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: myaudi.de
Nserver: ns2.audi.de
Nserver: ns5.xc-ns.de
Status: connect
Changed: 2011-10-13T15:08:45+02:00