Diapedia.org ranking shows that the page is at position 552,481 over the world, while the bulk of its audience is from United States, where it ranks 336,916.
Diapedia.org hosted on Amsio B.V servers in Netherlands. To reduce page loading time for the majority of diapedia.org users, we recommend migrating the server to United States, as it will speed up diapedia.org page load time for the majority of users. See the list of other webpages hosted on Amsio B.V servers.
In terms of rank-to-traffic ratio, diapedia.org has 1,214 unique users per day, viewing 1,336 pages. The rank based value of diapedia.org is 12,627 USD. Every user makes 1.18 pageviews on average.
Diapedia.org boasts a link base consisting of 223 referring domains and 266 external backlinks, as revealed by the data obtained from web network scanning.
Diapedia.org top-level domain belongs to .ORG domain zone. Check other webpages in .ORG zone.
According the last verification test in June 22, 2019, diapedia.org has an invalid SSL certificate. Click button “Update” SSL Information at the Safety Information section.
Based on data from Google Safe Browsing, Google Safe Search, Symantec and Web of Trust diapedia.org is a fairly safe domain.
According the Mobile-Friendly test by Google diapedia.org is nice optimized for mobile devices and tablets, however the webpage speed could be improved.
WARNING! | Certificate download error. Previous scan results are shown below. |
Domain | www.diapedia.org |
Issuer Organization | Unknown |
Issuer | Let's Encrypt Authority X3 |
Algorithm | RSA-SHA256 |
Valid form | 04/29/2019 |
Expiration | 07/28/2019 |
Signed | Certificate is not self signed |
Additional Domains |
diapedia.net diapedia.nl diapedia.org www.diapedia.net www.diapedia.nl www.diapedia.org |
Alexa Rank shows how popular diapedia.org is in comparison with other sites. The most popular site has Alexa Rank equals 1. If diapedia.org has Alexa Rank equals 100,000, then it is in TOP 100,000 popular sites in the world. The rank is calculated using a combination of average daily visitors to diapedia.org and pageviews on diapedia.org over the past 3 months.
ASN ID: 8315
ASN Title: Amsio B.V.Last Update: 11/08/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)
Domain Name: diapedia.org
Registry Domain ID: e8c3f08f3a614f04a220ebadb78dab87-LROR
Registrar WHOIS Server: http://whois.rrpproxy.net
Registrar URL: http://www.key-systems.net
Updated Date: 2024-06-08T12:33:26Z
Creation Date: 2008-04-24T12:33:08Z
Registry Expiry Date: 2025-04-24T12:33:08Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: abuse@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Driebit
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: NL
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: ns1.driebit.net
Name Server: ns2.driebit.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-12-04T20:07:07Z
Host | A Record | TTL |
---|---|---|
diapedia.org | 83.98.140.24 | 600 |
Host | MX Record | Priority | TTL |
---|---|---|---|
diapedia.org | mail.diapedia.org | 30 | 600 |
Host | NS Record | TTL |
---|---|---|
diapedia.org | ns2.driebit.net | 600 |
diapedia.org | ns1.driebit.net | 600 |
Host | TXT Record | TTL |
---|
ns1.driebit.net
TTL: 600
Email address: hostmaster.driebit.net
Serial: 2017030802
Refresh: 14400
Retry: 3600
Expire: 604800
Minimum: 86400
Last tested: 11/13/2015
Total Resources | 96 |
Number of Hosts | 15 |
Static Resources | 86 |
JavaScript Resources | 27 |
CSS Resources | 9 |
Last tested: 08/26/2019
Total Resources | 88 |
Number of Hosts | 12 |
Static Resources | 73 |
JavaScript Resources | 23 |
CSS Resources | 8 |