Meff.nl Startpagina meff


Online Status
Offline

Server IP address resolved: No
Http response code: None
Last Checked: 03/29/2024

Meff.nl traffic volume is 83 unique daily visitors and their 83 pageviews. The web value rate of meff.nl is 0 USD. Each visitor makes around 1.07 page views on average.

By Alexa's traffic estimates meff.nl placed at 48,057 position over the world.

Meff.nl registered under .NL top-level domain. Check other websites in .NL zone.

The last verification results, performed on (May 01, 2021) meff.nl show that meff.nl has an expired SSL certificate issued by Let's Encrypt (expired on June 19, 2021). Click “Refresh” button for SSL Information at the Safety Information section. Check the list of websites using SSL certificates issued by Let's Encrypt.

In accordance with Google Safe Browsing, Google Safe Search and Symantec meff.nl is pretty a safe domain.

Relying Google MobileFriendly test meff.nl is well optimized for mobile and tablet devices.


Global Rank
8,791,787
Average Load Time
5.48sec
Links In Count
37
Website Value
$0

Overview
Last Updated: 03/29/2024
Overall result - meff.nl is safe.
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
Last Updated: 03/20/2024
meff.nl is safe.
Norton ConnectSafe evaluates meff.nl for any unsafe and insecure content. The results are critical for families with young children.
Google Safe Search
Last Updated: 06/11/2017
meff.nl is safe.
SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.
Google Safe Browsing
Last Updated: 01/09/2019
meff.nl is safe.
Malware: not found.
Phishing: not detected.
Unwanted software: not found.
Harmfull applications: not found.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 02/18/2021
meff.nl is safe.
McAfee assesses meff.nl 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 meff.nl for mature or inappropriate content, only security checks are evaluated.
Web of Trust
Last Updated: 03/29/2024
meff.nl child safety is unknown.
The WOT calculates reputation of the meff.nl. This reputation system receives ratings from users and information from third-party sources, assesses the meff.nl for safety features and confirms, whether meff.nl is suitable for children.

SSL Information
Domainarg-pldacl09.amsiohosting.net
Issuer OrganizationLet's Encrypt
IssuerR3
AlgorithmRSA-SHA256
Valid form03/21/2021
Expiration06/19/2021
SignedCertificate is not self signed
Additional Domains arg-pldacl09.amsiohosting.net
Server Location

ASN Information

ASN ID: 8315
ASN Title: Amsio B.V.

Last Update: 03/17/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)

WHOIS

Domain name: meff.nl
Status: active

Registrar:
ZXCS
Krommewijk 5
7911TK Nieuweroord
Netherlands

Abuse Contact:

Creation Date: 2007-11-15

Updated Date: 2019-10-31

DNSSEC: yes

Domain nameservers:
ns1.zxcs.nl
ns2.zxcs.nl
ns3.zxcs.nl

Record maintained by: SIDN BV

Copyright notice
No part of this publication may be reproduced, published, stored in a
retrieval system, or transmitted, in any form or by any means,
electronic, mechanical, recording, or otherwise, without prior
permission of SIDN.
These restrictions apply equally to registrars, except in that
reproductions and publications are permitted insofar as they are
reasonable, necessary and solely in the context of the registration
activities referred to in the General Terms and Conditions for .nl
Registrars.
Any use of this material for advertising, targeting commercial offers or
similar activities is explicitly forbidden and liable to result in legal
action. Anyone who is aware or suspects that such activities are taking
place is asked to inform SIDN.
(c) SIDN BV, Dutch Copyright Act, protection of authors' rights
(Section 10, subsection 1, clause 1).


DNS Records
HostA RecordTTL
HostMX RecordPriorityTTL
HostNS RecordTTL
HostTXT RecordTTL

Errors
Warnings

Last tested: 12/01/2017

Desktop
Desktop Speed
85%

Desktop Resource Breakdown
Total Resources41
Number of Hosts12
Static Resources24
JavaScript Resources13
CSS Resources4

Last tested: 11/30/2017

Mobile
Mobile Usability
61%
Mobile Speed
72%

Mobile Resource Breakdown
Total Resources41
Number of Hosts12
Static Resources24
JavaScript Resources13
CSS Resources4
www.meff.com
www.meff.net
www.meff.org
www.meff.info
www.meff.biz
www.meff.us
www.meff.mobi
www.eff.nl
www.meff.nl
www.neff.nl
www.mneff.nl
www.nmeff.nl
www.jeff.nl
www.mjeff.nl
www.jmeff.nl
www.keff.nl
www.mkeff.nl
www.kmeff.nl
www.mff.nl
www.mwff.nl
www.mewff.nl
www.mweff.nl
www.msff.nl
www.mesff.nl
www.mseff.nl
www.mdff.nl
www.medff.nl
www.mdeff.nl
www.mrff.nl
www.merff.nl
www.mreff.nl
www.mef.nl
www.mecf.nl
www.mefcf.nl
www.mecff.nl
www.medf.nl
www.mefdf.nl
www.merf.nl
www.mefrf.nl
www.metf.nl
www.meftf.nl
www.metff.nl
www.megf.nl
www.mefgf.nl
www.megff.nl
www.mevf.nl
www.mefvf.nl
www.mevff.nl
www.mefc.nl
www.meffc.nl
www.mefd.nl
www.meffd.nl
www.mefr.nl
www.meffr.nl
www.meft.nl
www.mefft.nl
www.mefg.nl
www.meffg.nl
www.mefv.nl
www.meffv.nl