Status
Offline
Server IP address resolved: No
Http response code: None
Last Checked: 11/15/2024
Edana.org traffic estimate is about 531 unique visitors and 956 pageviews per day. The approximated value of edana.org is 8,760 USD. Every unique visitor makes about 1.8 pageviews on average.
Alexa Traffic Rank estimates that edana.org is ranked number 29,720 in the world, while most of its traffic comes from United States, where it occupies as high as 498,948 place.
Edana.org is registered under .ORG top-level domain. Check other websites in .ORG zone.
During the last check (May 21, 2021) edana.org has an expired SSL certificate issued by Let's Encrypt (expired on August 03, 2021), please click the “Refresh” button for SSL Information at the Safety Information section. Check other websites using SSL certificates issued by Let's Encrypt.
In accordance with Google Safe Browsing, Google Safe Search and Symantec edana.org is pretty a safe domain.
Relying on Google Mobile-Friendly test edana.org is well optimized for mobile and tablet devices, however website page loading time may be improved.
Where are website visitors coming from?
Country | Visitors |
---|---|
United States US | 16.9% |
India IN | 13.6% |
Other | 69.5% |
Country | Pageviews |
---|---|
United States US | 16.9% |
India IN | 13.6% |
Other | 69.5% |
Country | Rank |
---|---|
India IN | 258424 |
United States US | 498948 |
Where do visitors go on edana.org?
Subdomain | Pageviews |
---|---|
edana.org | 91.16% |
other | 8.83% |
Subdomain | Views per User |
---|---|
edana.org | 1 |
Subdomain | Reach |
---|---|
edana.org | 100% |
How popular is edana.org?
Period | Global Rank | Global Rank Delta |
---|---|---|
past 3 months | 711832 | 193207 |
past month | 638741 | -1002517 |
past week | 1258494 | 823733 |
yesterday | 696851 | 0 |
Days | Pageviews Rank | Pageviews Rank Delta | Pageviews per Million | Pageviews per Million Delta | Pageviews per User | Pageviews per User Delta |
---|---|---|---|---|---|---|
90 | 888797 | 245179 | 3 | -35.38% | 1.8 | -7.216% |
30 | 844405 | -1384816 | 3 | 300% | 2 | 40% |
7 | 1294392 | 789833 | 2 | -73.457% | 2 | 8% |
1 | 790886 | 0 | 3 | 0% | 1 | 0% |
Days | Reach Rank | Reach Rank Delta | Reach per Million | Reach per Million Delta |
---|---|---|---|---|
90 | 674566 | 177154 | 64 | -30.49% |
30 | 590098 | -847904 | 8 | 200% |
7 | 1331756 | 868814 | 3 | -75.439% |
1 | 632653 | 0 | 1 | 0% |
Press rescan to collect fresh statistics for this website...
(Rescan now...)Rankchart Summary
Safe
Updated: 11/15/2024
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Safe
Updated: 02/11/2024
Norton ConnectSafe evaluates websites for any unsafe and inapropriate content. The results are important for families with young children.
Google Safe Search
Safe
Updated: 08/18/2017
SafeSearch works as a parental control tool to filter out any content that might be inappropriate for your children.
Google Safe Browsing
Safe
Malware not found
Phishing not detected
Unwanted software not found
Harmfull applications not found
Updated: 01/09/2019
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
McAfee® WebAdvisor
Safe
Updated: 03/10/2021
McAfee assesses edana.org for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze edana.org for mature or inappropriate content, only security checks are evaluated.
Web of Trust
Not Checked
Updated: 11/15/2024
The WOT calculates reputation of the edana.org. This reputation system receives ratings from users and information from third-party sources, assesses the edana.org for safety features and confirms, whether edana.org is suitable for children.
Domain | edana.org |
Issuer Organization | Let's Encrypt |
Issuer | R3 |
Algorithm | RSA-SHA256 |
Valid form | 05/05/2021 |
Expiration | 08/03/2021 |
Signed | Certificate is not self signed |
Additional Domains | edana.eu edana.org www.edana.eu www.edana.org |
ASN ID: 8315
ASN Title: Amsio B.V.
Updated: 03/19/2024
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to 'AS8192 - AS8523'
as-block: AS8192 - AS8523
descr: RIPE NCC ASN block
remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by: RIPE-NCC-HM-MNT
created: 2010-05-11T11:44:46Z
last-modified: 2014-02-24T13:15:16Z
source: RIPE
% Information related to 'AS8315'
% Abuse contact for 'AS8315' is 'abuse@amsio.com'
aut-num: AS8315
as-name: AMSIO
remarks: Amsio Backbone
remarks: https://www.amsio.com
remarks: ==============================================================
remarks: Please find our peering details at
remarks: http://as8315.peeringdb.com/
remarks: ==============================================================
remarks: We have an open peering policy and would like to peer with
remarks: you. Please send requests to peering@amsio.com.
remarks: ==============================================================
remarks: NOC: noc@amsio.com
remarks: Abuse: abuse@amsio.com
remarks: ==============================================================
remarks: We share the view that for many networks ( including ours:-) )
remarks: only some abstraction of the actual routing policy should/can
remarks: be published in the IRR.
remarks: Right now we are abstracting to a very essential minimum.
remarks: the most important and helpful use of the IRR is
remarks: to publish what a network will announce to peers and upstream
remarks: we are providing that by means of the AS-set AS8315:AS-AMSIO
remarks: which we have been keeping up to date all the time
remarks: we encourage all our neighbors to define and maintain an
remarks: AS-set to describe their announcements, and to register
remarks: all the routes (and have their customers do so as well)
import: from AS-ANY accept ANY # heavy abstraction hits! well, we are ... neither peering promiscuously nor accepting all junk routes offered...
remarks: we maintain a list of what our neighbors have told us
remarks: about their announcements towards AS8315 - in terms of
remarks: AS-set (preferred), AS number, route-set
remarks: (and the IRR database used to publish)
remarks: in fact we apply route filters based on this
remarks: for all neighbors - as far as feasible
remarks: for data published through the RIPE routing registry
remarks: we generate filters automatically
remarks: we consider the integration of RIR and routing registry data
remarks: and the application of RPSS authorization a great feature
remarks: of the RIPE routing registry
remarks: unfortunately this benefit is not available with any
remarks: other IRR database that we know of...
remarks: and some of the IRR databases allow essentially any garbage
remarks: to be registered without any control - making those databases
remarks: quite useless...
export: to AS8315:AS-CUSTOMERS announce ANY # but don't publish that list; in general - if they ask for less, we can do
export: to AS-ANY announce AS8315:AS-AMSIO # for peers and others... for backwards compatibility the older AS-ARGEWEB will be kept around for some more time - defined using just members: AS8315:AS-AMSIO please convert to AS8315:AS-AMSIO if you are still using the old AS-ARGEWEB
remarks: customers are strongly encouraged to define and maintain
remarks: an AS-set that we will include in the definition
remarks: of AS8315:AS-AMSIO (if we are told the name)
remarks: this will be sufficient to have our peers accept the routes
remarks: in any case peers - and any network in the Internet -
remarks: is free to apply some selective policy (e.g. prefix
remarks: length based)
remarks: but we do not think that any such selective policy
remarks: will be based on details of our routing policy omitted
remarks: from this aut-num: object
remarks: unfortunately some customers do not provide usable IRR data;
remarks: we will NOT add to the uncontrolled garbage in the IRR by
remarks: proxy registering in some database that requires no
remarks: authorization
remarks: we advise customers that routes without IRR registration
remarks: and not covered by AS8315:AS-AMSIO may receive less than
remarks: full support by some of our peer networks and other
remarks: parts of the Internet
remarks: ==============================================================
remarks: IPv6 we do/publish essentially the same like for IPv4
mp-import: afi ipv6.unicast from AS-ANY accept ANY # heavy abstraction... neither peering promiscuously nor accepting all junk routes offered...
mp-export: afi ipv6.unicast to AS8315:AS-CUSTOMERS-V6 announce ANY # but don't publish that list; in general - if they ask for less, we can do
mp-export: afi ipv6.unicast to AS-ANY announce AS8315:AS-AMSIO-V6 # for peers and others...
remarks: ==============================================================
org: ORG-AB31-RIPE
admin-c: ABNO3-RIPE
tech-c: ABNO3-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: AMSIO-MNT
created: 2006-01-05T09:59:28Z
last-modified: 2018-02-14T07:31:02Z
source: RIPE
organisation: ORG-AB31-RIPE
org-name: Amsio B.V.
org-type: LIR
address: Postbus 505
address: 3140AM
address: Maassluis
address: NETHERLANDS
phone: +31888007555
fax-no: +31888007501
admin-c: RvdZ8-RIPE
admin-c: OvdL5-RIPE
tech-c: RvdZ8-RIPE
abuse-c: ABRO2-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: AMSIO-MNT
mnt-by: RIPE-NCC-HM-MNT
mnt-by: AMSIO-MNT
created: 2010-05-10T10:59:12Z
last-modified: 2016-06-17T11:27:22Z
source: RIPE # Filtered
role: Amsio BV - Network Operators
address: Noordzee 10C
address: 3144DB Maassluis
address: The Netherlands
nic-hdl: ABNO3-RIPE
tech-c: SK3127-RIPE
tech-c: OvdL5-RIPE
tech-c: RvdZ8-RIPE
admin-c: GvL13-RIPE
admin-c: RvdZ8-RIPE
mnt-by: AMSIO-MNT
created: 2018-02-14T07:02:35Z
last-modified: 2018-02-14T07:03:26Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.91.2 (HEREFORD)
Host | A Record | TTL |
---|
Information about registered users or assignees of an Internet resource
Domain Name: edana.org
Registry Domain ID: 627d837705514bf6bcb913f4fa77747e-LROR
Registrar WHOIS Server: http://whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2023-09-28T04:00:24Z
Creation Date: 1997-08-15T04:00:00Z
Registry Expiry Date: 2024-08-14T04:00:00Z
Registrar: eNom, LLC
Registrar IANA ID: 48
Registrar Abuse Contact Email: abuse@enom.com
Registrar Abuse Contact Phone: +1.4252982646
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: edana
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: BRUXELLES
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: BE
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns.megabyte.be
Name Server: ns2.megabyte.be
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-10-25T08:11:51Z
Website desktop performance and usability tips
Speed
70%
Number and type of the resources loaded from the website:
Total Resources | 67 |
Number of Hosts | 6 |
Static Resources | 48 |
JavaScript Resources | 23 |
CSS Resources | 5 |
CSS | 152.6 KBytes |
Images | 515.1 KBytes |
HTML | 179.6 KBytes |
JavaScript | 3.2 MBytes |
Other | 4.1 KBytes |
Updated: 03/16/2019
Tips on speeding up mobile site performance
Usability
74%
Speed
50%
Number and type of the resources loaded from the website:
Total Resources | 67 |
Number of Hosts | 6 |
Static Resources | 48 |
JavaScript Resources | 23 |
CSS Resources | 5 |
CSS | 152.6 KBytes |
Images | 515.1 KBytes |
HTML | 179.6 KBytes |
JavaScript | 3.2 MBytes |
Other | 4.1 KBytes |
Updated: 03/16/2019