Status
Online
Server IP address resolved: Yes
Http response code: 200
Response time: 1.95 sec.
Last Checked: 11/14/2024
Frankwatching.com traffic estimate is about 2,315 unique visitors and 3,473 pageviews per day. The approximated value of frankwatching.com is 65,700 USD. Every unique visitor makes about 1.5 pageviews on average.
Alexa Traffic Rank estimates that frankwatching.com is ranked number 14,067 in the world, while most of its traffic comes from Netherlands, where it occupies as high as 2,354 place.
It’s good for frankwatching.com that their hosting company Amsio B.V is located in Netherlands, as that provides the majority of their visitors to benefit from the faster page load time. See the list of other websites hosted by Amsio B.V.
Frankwatching.com is registered under .COM top-level domain. Check other websites in .COM zone.
During the last check (August 15, 2024) frankwatching.com has a valid and up-to-date SSL certificate issued by Sectigo Limited that expires on March 17, 2025, please click the “Refresh” button for SSL Information at the Safety Information section. Check other websites using SSL certificates issued by Sectigo Limited.
In accordance with Google Safe Browsing, Google Safe Search, Symantec and Web of Trust frankwatching.com is pretty a safe domain.
Relying on Google Mobile-Friendly test frankwatching.com is well optimized for mobile and tablet devices, however website page loading time may be improved.
Where are website visitors coming from?
Country | Visitors |
---|---|
Netherlands NL | 74.1% |
Belgium BE | 14.1% |
United States US | 3.1% |
Canada CA | 2.3% |
India IN | 1.4% |
Other | 4.9% |
Country | Pageviews |
---|---|
Netherlands NL | 74.1% |
Belgium BE | 14.1% |
United States US | 3.1% |
Canada CA | 2.3% |
India IN | 1.4% |
Other | 4.9% |
Country | Rank |
---|---|
Netherlands NL | 2354 |
Belgium BE | 8391 |
Canada CA | 78998 |
India IN | 325603 |
United States US | 558415 |
Where do visitors go on frankwatching.com?
Subdomain | Pageviews |
---|---|
frankwatching.com | 97.93% |
cdn.frankwatching.com | 2.07% |
Subdomain | Views per User |
---|---|
frankwatching.com | 1.4 |
cdn.frankwatching.com | 1 |
Subdomain | Reach |
---|---|
frankwatching.com | 99.26% |
cdn.frankwatching.com | 2.92% |
How popular is frankwatching.com?
Period | Global Rank | Global Rank Delta |
---|---|---|
past 3 months | 197558 | 63769 |
past month | 156439 | -59545 |
past week | 131515 | -17840 |
yesterday | 122020 | 8137 |
Days | Pageviews Rank | Pageviews Rank Delta | Pageviews per Million | Pageviews per Million Delta | Pageviews per User | Pageviews per User Delta |
---|---|---|---|---|---|---|
90 | 292861 | 103906 | 14 | -42.25% | 1.5 | -8.176% |
30 | 240028 | -69261 | 18 | 40% | 1.4 | -11.32% |
7 | 203055 | -40771 | 23 | 30% | 1.5 | 10% |
1 | 171189 | 23275 | 32 | -17.38% | 2 | -15.05% |
Days | Reach Rank | Reach Rank Delta | Reach per Million | Reach per Million Delta |
---|---|---|---|---|
90 | 172896 | 53566 | 35 | -36.9% |
30 | 135285 | -59406 | 47 | 57% |
7 | 115279 | -11166 | 58 | 10% |
1 | 131686 | 14279 | 7 | -2.6% |
Press rescan to collect fresh statistics for this website...
(Rescan now...)Rankchart Summary
Safe
Updated: 11/14/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: 03/22/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: 10/17/2016
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: 02/22/2021
McAfee assesses frankwatching.com 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 frankwatching.com for mature or inappropriate content, only security checks are evaluated.
Web of Trust
Child safety is good
Updated: 01/09/2019
The WOT calculates reputation of the frankwatching.com. This reputation system receives ratings from users and information from third-party sources, assesses the frankwatching.com for safety features and confirms, whether frankwatching.com is suitable for children.
Domain | www.frankwatching.com |
Issuer Organization | Sectigo Limited |
Issuer | Sectigo RSA Extended Validation Secure Server CA |
Algorithm | RSA-SHA256 |
Valid form | 03/11/2024 |
Expiration | 03/17/2025 |
Signed | Certificate is not self signed |
Additional Domains | www.frankwatching.com frankwatching.com |
ASN ID: 8315
ASN Title: Amsio B.V.
Updated: 07/16/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 |
---|---|---|
frankwatching.com | 213.214.123.41 | 3600 |
Host | MX Record | Priority | TTL |
---|---|---|---|
frankwatching.com | ASPMX3.GOOGLEMAIL.com | 10 | 3600 |
frankwatching.com | ASPMX4.GOOGLEMAIL.com | 10 | 3600 |
frankwatching.com | ALT2.ASPMX.L.GOOGLE.com | 5 | 3600 |
frankwatching.com | ALT1.ASPMX.L.GOOGLE.com | 5 | 3600 |
frankwatching.com | ASPMX5.GOOGLEMAIL.com | 10 | 3600 |
frankwatching.com | ASPMX2.GOOGLEMAIL.com | 10 | 3600 |
frankwatching.com | ASPMX.L.GOOGLE.com | 1 | 3600 |
Host | NS Record | TTL |
---|---|---|
frankwatching.com | ns1.nines.nl | 3600 |
frankwatching.com | ns2.nines.nl | 3600 |
frankwatching.com | ns3.9-9-9-9-9.net | 3600 |
Host | TXT Record | TTL |
---|---|---|
frankwatching.com | v=spf1 a mx ip4:213.214.120.32/27 include:_spf.nines.nl include:_spf.sc.nines.nl include:_spf.google.com include:_spf.moneybird.nl include:sparkpostmail.com ~all | 3600 |
frankwatching.com | google-site-verification=u7N4kvP8S4LrCD7Uga4nyjVHfkf22yHTj3R_5HY40z4 | 3600 |
frankwatching.com | google-site-verification=MfhjyVnye9r-zzeBdszjiSEfXKxxcZ3giiYLl6qOhkc | 3600 |
frankwatching.com | google-site-verification=jZThw_GqPYT7LPovWoPiYbi1ZuC9lyhjRsGAaTAb2dI | 3600 |
ns1.nines.nl
TTL: 86400
Email address: registry.nines.nl
Serial: 2019011814
Refresh: 86400
Retry: 7200
Expire: 3024000
Minimum: 300
Information about registered users or assignees of an Internet resource
Domain Name: FRANKWATCHING.COM
Registry Domain ID: 133930802_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.eu
Registrar URL: http://www.openprovider.com
Updated Date: 2024-01-26T09:45:02Z
Creation Date: 2004-10-29T15:11:12Z
Registry Expiry Date: 2024-10-29T15:11:12Z
Registrar: Hosting Concepts B.V. d/b/a Registrar.eu
Registrar IANA ID: 1647
Registrar Abuse Contact Email: abuse@registrar.eu
Registrar Abuse Contact Phone: +31.104482297
Domain Status: ok https://icann.org/epp#ok
Name Server: EVELYN.NS.CLOUDFLARE.COM
Name Server: FONZIE.NS.CLOUDFLARE.COM
DNSSEC: signedDelegation
DNSSEC DS Data: 2371 13 2 6C906282FDDB15D4BF1A663678D5A3E533EBBC53FC3591FB4CB3E72021F333BE
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-10T22:55:27Z
Website desktop performance and usability tips
Speed
32%
Number and type of the resources loaded from the website:
Total Resources | 235 |
Number of Hosts | 20 |
Static Resources | 182 |
JavaScript Resources | 80 |
CSS Resources | 3 |
CSS | 496.0 KBytes |
Images | 3.9 MBytes |
HTML | 237.5 KBytes |
JavaScript | 471.9 KBytes |
Other | 139.7 KBytes |
Updated: 08/09/2016
Tips on speeding up mobile site performance
Usability
99%
Speed
36%
Number and type of the resources loaded from the website:
Total Resources | 163 |
Number of Hosts | 23 |
Static Resources | 138 |
JavaScript Resources | 39 |
CSS Resources | 5 |
Text | 326.0 Bytes |
CSS | 732.0 KBytes |
Images | 941.5 KBytes |
HTML | 198.8 KBytes |
JavaScript | 5.5 MBytes |
Other | 80.5 KBytes |
Updated: 12/07/2019