wafar.com
Free website and domain report on wafar.com
Last Updated: 1st February, 2021 Update Now
Overview
Snoop Summary for wafar.com
This is a free and comprehensive report about wafar.com. Wafar.com is hosted in Austin, Texas in United States on a server with an IP address of 65.75.180.235, where the local currency is USD and English is the local language. Our records indicate that wafar.com is owned/operated by webcom media. If wafar.com was to be sold it would possibly be worth $239 USD (based on the daily revenue potential of the website over a 24 month period). Wafar.com is somewhat popular with an estimated 110 daily unique visitors. This report was last updated 1st February, 2021.
About wafar.com
| Site Preview: |   |
| Title: | |
| Description: | |
| Keywords and Tags: | travel |
| Related Terms: | |
| Fav Icon: | |
| Age: | Over 23 years old |
| Domain Created: | 2nd May, 2000 |
| Domain Updated: | 3rd May, 2020 |
| Domain Expires: | 2nd May, 2021 |
Review
Snoop Score
1/5
Valuation
$239 USD
Note: All valuation figures are estimates.
Popularity
Low
Note: Popularity is estimated.
Rank, Reach and Authority
| Alexa Rank: | 8,030,046 |
| Alexa Reach: | <0.0001% |
| SEMrush Rank (US): | |
| SEMrush Authority Score: | |
| Moz Domain Authority: | 0 |
| Moz Page Authority: | 0 |
Organic vs Paid (Google Ads)
Traffic
Visitors
| Daily Visitors: | 110 |
| Monthly Visitors: | 3,351 |
| Yearly Visitors: | 40,190 |
Note: All visitors figures are estimates.
Visitors By Country
Revenue
Revenue
| Daily Revenue: | $0 USD |
| Monthly Revenue: | $10 USD |
| Yearly Revenue: | $115 USD |
Note: All revenue figures are estimates.
Revenue By Country
SEO
Backlinks Analysis (SEMrush)
Top New Follow Links
Top Ranking Keywords (US)
Domain Analysis
| Value | Length | |
|---|---|---|
| Domain: | wafar.com | 9 |
| Domain Name: | wafar | 5 |
| Extension (TLD): | com | 3 |
| Expiry Check: | |
Page Speed Analysis
| Average Load Time: | 14.24 seconds |
| Load Time Comparison: | Faster than 1% of sites |
PageSpeed Insights
Avg. (All Categories)
Performance
Accessibility
Best Practices
SEO
Progressive Web App
0–49 (Fail) 50–89 (Average) 90–100 (Pass) 
Simulate loading on desktop
Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for wafar.com. This includes details about optimizing page load times which can result in a better user experience.Metrics
First Contentful Paint — 0.3 s The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.3 s The time taken for the primary content of the page to be rendered.
Speed Index — 0.3 s The time taken for the page contents to be visibly populated.
Time to Interactive — 0.3 s The time taken for the page to become fully interactive.
First CPU Idle — 0.3 s The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms Users could experience a delay when interacting with the page.
Other
Estimated Input Latency — 10 ms The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive wafar.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 ms The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests Below is a list of network requests that were made during page load.
| URL | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|
| http://wafar.com/ | 0 | 119.79899997823 | 364 | 111 | 200 | text/html | Document |
| http://wafar.com/cgi-sys/defaultwebpage.cgi | 143.76399992034 | 276.00000007078 | 1780 | 3319 | 200 | text/html | Document |
| http://wafar.com/img-sys/bg.jpg | 290.0030000601 | 370.94100005925 | 884 | 1318 | 404 | text/html | Image |
| http://wafar.com/img-sys/header.jpg | 290.33200000413 | 411.66199999861 | 19299 | 19080 | 200 | image/jpeg | Image |
| http://wafar.com/img-sys/contentbox.jpg | 290.41499993764 | 335.99400008097 | 884 | 1318 | 404 | text/html | Image |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 154.136 | 8.205 |
| 308.962 | 8.165 |
| 323.919 | 16.719 |
Opportunities
Eliminate render-blocking resources Resources, such as JavaScript and style sheets, can block the first paint of the page. Wafar.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images Images can slow down the page's load time. Wafar.com should consider serving more appropriate-sized images.
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Wafar.com should consider lazy-loading offscreen and hidden images.
Minify CSS Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wafar.com should consider minifying CSS files.
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wafar.com should consider minifying JS files.
Remove unused CSS Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wafar.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images — Potential savings of 6 KB Unoptimized images can consume more cellular data than what is necessary.
| URL | Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| http://wafar.com/img-sys/header.jpg | 19080 | 6247 |
Serve images in next-gen formats — Potential savings of 14 KB Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
| URL | Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| http://wafar.com/img-sys/header.jpg | 19080 | 14148 |
Enable text compression Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 120 ms Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects Redirects can cause additional delays before the page can begin loading. Wafar.com should avoid multiple or unnecessary page redirects.
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Wafar.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Diagnostics
Avoids enormous network payloads — Total size was 23 KB Large network payloads can cost users money and are linked to long load times.
| URL | Size (Bytes) |
|---|---|
| http://wafar.com/img-sys/header.jpg | 19299 |
| http://wafar.com/cgi-sys/defaultwebpage.cgi | 1780 |
| http://wafar.com/img-sys/bg.jpg | 884 |
| http://wafar.com/img-sys/contentbox.jpg | 884 |
| http://wafar.com/ | 364 |
Uses efficient cache policy on static assets — 1 resource found Wafar.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
| URL | Cache TTL (Ms) | Size (Bytes) |
|---|---|---|
| http://wafar.com/img-sys/header.jpg | 0 | 19299 |
Avoids an excessive DOM size — 25 elements A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
| Statistic | Element | Value |
|---|---|---|
| Total DOM Elements | 25 | |
| Maximum DOM Depth | 5 | |
| Maximum Child Elements | 7 |
Avoid chaining critical requests Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wafar.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| URL | Total CPU Time (Ms) | Script Evaluation (Ms) | Script Parse (Ms) |
|---|---|---|---|
| Other | 54.464 | 3.54 | 2.273 |
Minimizes main-thread work — 0.1 s Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| Category | Time Spent (Ms) |
|---|---|
| Other | 25.254 |
| Style & Layout | 16.244 |
| Rendering | 5.535 |
| Script Evaluation | 3.54 |
| Script Parsing & Compilation | 2.273 |
| Parse HTML & CSS | 1.618 |
All text remains visible during webfont loads Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 5 requests • 23 KB It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
| Resource Type | Requests | Transfer Size (Bytes) |
|---|---|---|
| Total | 5 | 23211 |
| Image | 3 | 21067 |
| Document | 2 | 2144 |
| Stylesheet | 0 | 0 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Script | 0 | 0 |
| Other | 0 | 0 |
| Third-party | 0 | 0 |
Minimize third-party usage It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Budgets
Performance budget It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wafar.com. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0 Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[role]`s have all required `[aria-*]` attributes Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid All ARIA roles require valid values to perform their intended functions.
`[aria-*]` attributes have valid values ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
Audio and video
`<audio>` elements contain a `<track>` element with `[kind="captions"]` Wafar.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]` Wafar.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]` Wafar.com may provide relevant information that dialogue cannot, by using audio descriptions.
Names and labels
Buttons have an accessible name Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
`<frame>` or `<iframe>` elements have a title Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.
Contrast
Background and foreground colors have a sufficient contrast ratio Many (if not most) users find low-contrast text difficult or impossible to read.
Tables and lists
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements. Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute. It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.
Best practices
`[id]` attributes on the page are unique It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
The document does not use `<meta http-equiv="refresh">` Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5. For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Internationalization and localization
`<html>` element has a valid value for its `[lang]` attribute Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.
Internationalization and localization
`<html>` element does not have a `[lang]` attribute It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
| Failing Elements |
|---|
Manual Checks
The page has a logical tab order The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
Headings don't skip levels Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that wafar.com should incorporate. This includes practices such as protecting pages with HTTPS.Other
Avoids Application Cache Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()` Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Links to cross-origin destinations are safe Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio Ensure that image display dimensions match their natural aspect ratio.
Other
Does not use HTTPS — 5 insecure requests found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://wafar.com/ |
| http://wafar.com/cgi-sys/defaultwebpage.cgi |
| http://wafar.com/img-sys/bg.jpg |
| http://wafar.com/img-sys/header.jpg |
| http://wafar.com/img-sys/contentbox.jpg |
Page lacks the HTML doctype, thus triggering quirks-mode Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Browser errors were logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
| URL | Description |
|---|---|
| http://wafar.com/img-sys/contentbox.jpg | Failed to load resource: the server responded with a status of 404 (Not Found) |
| http://wafar.com/img-sys/bg.jpg | Failed to load resource: the server responded with a status of 404 (Not Found) |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wafar.com. This includes optimizations such as providing meta data.Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang` Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical` Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Crawling and Indexing
Page has successful HTTP status code Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Mobile Friendly
Document uses legible font sizes Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Mobile Friendly
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of wafar.com on mobile screens.
Content Best Practices
Document does not have a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Manual Checks
Structured data is valid Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Progressive Web App
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wafar.com. This includes details about web app manifests.Fast and reliable
Page load is fast enough on mobile networks Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
PWA Optimized
Content is sized correctly for the viewport Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Contains some content when JavaScript is not available Apps should display alternative content for when JavaScript is disabled.
Fast and reliable
Current page does not respond with a 200 when offline In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.
Installable
Does not use HTTPS — 5 insecure requests found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://wafar.com/ |
| http://wafar.com/cgi-sys/defaultwebpage.cgi |
| http://wafar.com/img-sys/bg.jpg |
| http://wafar.com/img-sys/header.jpg |
| http://wafar.com/img-sys/contentbox.jpg |
Does not register a service worker that controls page and `start_url` A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data
PWA Optimized
Does not redirect HTTP traffic to HTTPS It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar. A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of wafar.com on mobile screens.
Does not provide a valid `apple-touch-icon` iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manual Checks
Site works cross-browser Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories)
Performance
Accessibility
Best Practices
SEO
Progressive Web App
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for wafar.com. This includes details about optimizing page load times which can result in a better user experience.Metrics
First Contentful Paint — 0.8 s The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.8 s The time taken for the primary content of the page to be rendered.
Speed Index — 0.8 s The time taken for the page contents to be visibly populated.
Time to Interactive — 0.8 s The time taken for the page to become fully interactive.
First CPU Idle — 0.8 s The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms Users could experience a delay when interacting with the page.
Other
Estimated Input Latency — 10 ms The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive wafar.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 ms The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests Below is a list of network requests that were made during page load.
| URL | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|
| http://wafar.com/ | 0 | 74.217999819666 | 364 | 111 | 200 | text/html | Document |
| http://wafar.com/cgi-sys/defaultwebpage.cgi | 98.421999718994 | 174.3159997277 | 1780 | 3319 | 200 | text/html | Document |
| http://wafar.com/img-sys/bg.jpg | 186.60899996758 | 232.85699961707 | 884 | 1318 | 404 | text/html | Image |
| http://wafar.com/img-sys/header.jpg | 186.93599989638 | 327.55699986592 | 19299 | 19080 | 200 | image/jpeg | Image |
| http://wafar.com/img-sys/contentbox.jpg | 187.05999990925 | 243.71199961752 | 884 | 1318 | 404 | text/html | Image |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 107.966 | 12.558 |
| 205.525 | 7.114 |
| 216.617 | 18.472 |
First Contentful Paint (3G) — 1560 ms The time taken for the first image or text on the page to be rendered while on a 3G network.
Opportunities
Eliminate render-blocking resources Resources, such as JavaScript and style sheets, can block the first paint of the page. Wafar.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images Images can slow down the page's load time. Wafar.com should consider serving more appropriate-sized images.
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Wafar.com should consider lazy-loading offscreen and hidden images.
Minify CSS Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wafar.com should consider minifying CSS files.
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wafar.com should consider minifying JS files.
Remove unused CSS Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wafar.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Enable text compression Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 80 ms Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects Redirects can cause additional delays before the page can begin loading. Wafar.com should avoid multiple or unnecessary page redirects.
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Wafar.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Diagnostics
Avoids enormous network payloads — Total size was 23 KB Large network payloads can cost users money and are linked to long load times.
| URL | Size (Bytes) |
|---|---|
| http://wafar.com/img-sys/header.jpg | 19299 |
| http://wafar.com/cgi-sys/defaultwebpage.cgi | 1780 |
| http://wafar.com/img-sys/bg.jpg | 884 |
| http://wafar.com/img-sys/contentbox.jpg | 884 |
| http://wafar.com/ | 364 |
Uses efficient cache policy on static assets — 1 resource found Wafar.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
| URL | Cache TTL (Ms) | Size (Bytes) |
|---|---|---|
| http://wafar.com/img-sys/header.jpg | 0 | 19299 |
Avoids an excessive DOM size — 25 elements A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
| Statistic | Element | Value |
|---|---|---|
| Total DOM Elements | 25 | |
| Maximum DOM Depth | 5 | |
| Maximum Child Elements | 7 |
Avoid chaining critical requests Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wafar.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| URL | Total CPU Time (Ms) | Script Evaluation (Ms) | Script Parse (Ms) |
|---|---|---|---|
| Other | 225.476 | 12.376 | 7.856 |
Minimizes main-thread work — 0.2 s Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| Category | Time Spent (Ms) |
|---|---|
| Other | 101.568 |
| Style & Layout | 71.032 |
| Rendering | 17.236 |
| Script Evaluation | 12.376 |
| Garbage Collection | 8.74 |
| Script Parsing & Compilation | 7.856 |
| Parse HTML & CSS | 6.668 |
All text remains visible during webfont loads Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 5 requests • 23 KB It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
| Resource Type | Requests | Transfer Size (Bytes) |
|---|---|---|
| Total | 5 | 23211 |
| Image | 3 | 21067 |
| Document | 2 | 2144 |
| Stylesheet | 0 | 0 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Script | 0 | 0 |
| Other | 0 | 0 |
| Third-party | 0 | 0 |
Minimize third-party usage It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Budgets
Performance budget It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Opportunities
Efficiently encode images — Potential savings of 6 KB Unoptimized images can consume more cellular data than what is necessary.
| URL | Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| http://wafar.com/img-sys/header.jpg | 19080 | 6247 |
Serve images in next-gen formats — Potential savings of 14 KB Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
| URL | Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| http://wafar.com/img-sys/header.jpg | 19080 | 14148 |
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wafar.com. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0 Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[role]`s have all required `[aria-*]` attributes Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid All ARIA roles require valid values to perform their intended functions.
`[aria-*]` attributes have valid values ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
Audio and video
`<audio>` elements contain a `<track>` element with `[kind="captions"]` Wafar.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]` Wafar.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]` Wafar.com may provide relevant information that dialogue cannot, by using audio descriptions.
Names and labels
Buttons have an accessible name Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
`<frame>` or `<iframe>` elements have a title Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.
Contrast
Background and foreground colors have a sufficient contrast ratio Many (if not most) users find low-contrast text difficult or impossible to read.
Tables and lists
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements. Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute. It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.
Best practices
`[id]` attributes on the page are unique It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
The document does not use `<meta http-equiv="refresh">` Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5. For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Internationalization and localization
`<html>` element has a valid value for its `[lang]` attribute Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.
Internationalization and localization
`<html>` element does not have a `[lang]` attribute It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
| Failing Elements |
|---|
Manual Checks
The page has a logical tab order The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
Headings don't skip levels Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that wafar.com should incorporate. This includes practices such as protecting pages with HTTPS.Other
Avoids Application Cache Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()` Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Links to cross-origin destinations are safe Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio Ensure that image display dimensions match their natural aspect ratio.
Other
Does not use HTTPS — 5 insecure requests found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://wafar.com/ |
| http://wafar.com/cgi-sys/defaultwebpage.cgi |
| http://wafar.com/img-sys/bg.jpg |
| http://wafar.com/img-sys/header.jpg |
| http://wafar.com/img-sys/contentbox.jpg |
Page lacks the HTML doctype, thus triggering quirks-mode Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Browser errors were logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
| URL | Description |
|---|---|
| http://wafar.com/img-sys/bg.jpg | Failed to load resource: the server responded with a status of 404 (Not Found) |
| http://wafar.com/img-sys/contentbox.jpg | Failed to load resource: the server responded with a status of 404 (Not Found) |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wafar.com. This includes optimizations such as providing meta data.Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang` Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical` Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Crawling and Indexing
Page has successful HTTP status code Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Mobile Friendly
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of wafar.com on mobile screens.
Document doesn't use legible font sizes Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Content Best Practices
Document does not have a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Manual Checks
Structured data is valid Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Progressive Web App
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wafar.com. This includes details about web app manifests.Fast and reliable
Page load is fast enough on mobile networks Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
PWA Optimized
Contains some content when JavaScript is not available Apps should display alternative content for when JavaScript is disabled.
Fast and reliable
Current page does not respond with a 200 when offline In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.
Installable
Does not use HTTPS — 5 insecure requests found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL |
|---|
| http://wafar.com/ |
| http://wafar.com/cgi-sys/defaultwebpage.cgi |
| http://wafar.com/img-sys/bg.jpg |
| http://wafar.com/img-sys/header.jpg |
| http://wafar.com/img-sys/contentbox.jpg |
Does not register a service worker that controls page and `start_url` A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data
PWA Optimized
Does not redirect HTTP traffic to HTTPS It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar. A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of wafar.com on mobile screens.
Does not provide a valid `apple-touch-icon` iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manual Checks
Site works cross-browser Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting
Server Location
| Server IP Address: | 65.75.180.235 |
| Continent: | North America |
| Country: | United States  |
| Region: | Texas |
| City: | Austin |
| Longitude: | -97.6673 |
| Latitude: | 30.3423 |
| Currencies: | USD USN USS |
| Languages: | English |
Web Hosting Provider
| Name | IP Address |
|---|---|
| SoftwareWorks Group, Inc. |
Registration
Domain Registrant
| Private Registration: | No |
| Name: | |
| Organization: | webcom media |
| Country: | EG |
| City: | |
| State: | NA |
| Post Code: | |
| Email: | |
| Phone: |
Note: Registration information is derived from various sources and may be inaccurate.
Domain Registrar
| Name | IP Address |
|---|---|
| GoDaddy.com, LLC | 96.7.27.23 |
Security
Visitor Safety
| Mature Content: | Not Likely |
| McAfee WebAdvisor Rating: | Safe |
| WOT Rating: | |
| WOT Trustworthiness: | |
| WOT Child Safety: |
Note: Safety information is not guaranteed.
SSL/TLS Certificate
Technical
DNS Lookup
A Records
| Host | IP Address | Class | TTL |
|---|---|---|---|
| wafar.com. | 65.75.180.235 | IN | 599 |
NS Records
| Host | Nameserver | Class | TTL |
|---|---|---|---|
| wafar.com. | ns25.domaincontrol.com. | IN | 3599 |
| wafar.com. | ns26.domaincontrol.com. | IN | 3599 |
SOA Records
| Domain Name | Primary NS | Responsible Email | TTL |
|---|---|---|---|
| wafar.com. | ns25.domaincontrol.com. | dns.jomax.net. | 3599 |
HTTP Response Headers
| HTTP-Code: | HTTP/1.1 200 OK |
| Server: | nginx/1.14.2 |
| Date: | 6th May, 2020 |
| Content-Type: | text/html |
| Content-Length: | 111 |
| Connection: | keep-alive |
| Last-Modified: | 20th October, 2016 |
| Accept-Ranges: | bytes |
Whois Lookup
| Created: | 2nd May, 2000 |
| Changed: | 3rd May, 2020 |
| Expires: | 2nd May, 2021 |
| Registrar: | GoDaddy.com, LLC |
| Status: | clientTransferProhibited clientUpdateProhibited clientRenewProhibited clientDeleteProhibited |
| Nameservers: | ns25.domaincontrol.com ns26.domaincontrol.com |
| Owner Organization: | webcom media |
| Owner State: | NA |
| Owner Country: | EG |
| Owner Email: | Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WAFAR.COM |
| Admin Email: | Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WAFAR.COM |
| Tech Email: | Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WAFAR.COM |
| Full Whois: | Domain Name: WAFAR.COM
Registry Domain ID: 26209358_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.godaddy.com Registrar URL: http://www.godaddy.com Updated Date: 2020-05-03T10:42:46Z Creation Date: 2000-05-02T18:53:49Z Registrar Registration Expiration Date: 2021-05-02T18:53:49Z Registrar: GoDaddy.com, LLC Registrar IANA ID: 146 Registrar Abuse Contact Email: abuse@godaddy.com Registrar Abuse Contact Phone: +1.4806242505 Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited Registrant Organization: webcom media Registrant State/Province: NA Registrant Country: EG Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WAFAR.COM Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WAFAR.COM Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=WAFAR.COM Name Server: NS25.DOMAINCONTROL.COM Name Server: NS26.DOMAINCONTROL.COM DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2020-05-06T13:00:00Z <<< For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en Notes: IMPORTANT: Port43 will provide the ICANN-required minimum data set per ICANN Temporary Specification, adopted 17 May 2018. Visit https://whois.godaddy.com to look up contact data for domains not covered by GDPR policy. The data contained in GoDaddy.com, LLC's WhoIs database, while believed by the company to be reliable, is provided "as is" with no guarantee or warranties regarding its accuracy. This information is provided for the sole purpose of assisting you in obtaining information about domain name registration records. Any use of this data for any other purpose is expressly forbidden without the prior written permission of GoDaddy.com, LLC. By submitting an inquiry, you agree to these terms of usage and limitations of warranty. In particular, you agree not to use this data to allow, enable, or otherwise make possible, dissemination or collection of this data, in part or in its entirety, for any purpose, such as the transmission of unsolicited advertising and and solicitations of any kind, including spam. You further agree not to use this data to enable high volume, automated or robotic electronic processes designed to collect or compile this data for any purpose, including mining this data for your own personal or commercial purposes. Please note: the registrant of the domain name is specified in the "registrant" section. In most cases, GoDaddy.com, LLC is not the registrant of domain names listed in this database. |
Nameservers
| Name | IP Address |
|---|---|
| ns25.domaincontrol.com | 97.74.102.13 |
| ns26.domaincontrol.com | 173.201.70.13 |
Love W3 Snoop?
Share This 