digitalrisks.fi
Details
Source: Finnish Transport and Communications Agency (Traficom) and Internet Assigned Numbers Authority (IANA)| State | Validity expired |
| Holder | Digital Risks (Company), 9265254 180 Borough High St, United Kingdom +44.7538164347 |
| Grant Date | 2019-07-09 |
| Last Validity Date | 2020-07-09 |
| Registrar | Gandi SAS SE1 1LB London |
| Name Servers Please see DNS section for details | ns-1203.awsdns-22.org ns-1711.awsdns-21.co.uk ns-547.awsdns-04.net ns-8.awsdns-01.com |
| Is The DNSSec in Use | No |
| IANA details for suffix | Top Level Domain (TLD): FI TLD manager: Finnish Transport and Communications Agency Traficom Domain type: Country-code |
Server IP location
Source: Actual web page - Timestamp: 2020-05-22 09:04WARNING: Please notice that the location may be totally wrong if server uses e.g. reverse proxy like Cloudflare
Server IP not valid or missing details in database. Map not shown
Word cloud for digitalrisks.fi
Sorry, not enough data to parse a word cloud for this site at this time
Web page details for digitalrisks.fi
Source: Actual web page - Timestamp: | Header data & Meta tags | |
| Open Graph (OG) meta tags | Using Open Graph tags is highly recommended for Search Engine Optimization (SEO) |
| Twitter cards | Using Twitter tags is highly recommended for Search Engine Optimization (SEO) |
| Cascading Style Sheets (CSS) (CSS) | |
| Social Media (SOME) links | Having Social Media content is highly recommended for Search Engine Optimization (SEO) |
| JavaScript libraries |
Screenshot for digitalrisks.fi
DNS records for digitalrisks.fi
Source: DNS reponse - Timestamp: 2020-05-22 09:04| NS | ns-1203.awsdns-22.org
|
| SOA | digitalrisks.fi ns-1711.awsdns-21.co.uk (Time to Live: 899) awsdns-hostmaster.amazon.com |
Whois record history for digitalrisks.fi
Source: Finnish Transport and Communications Agency (Traficom)Showing latest max 5 detected changes in the records. Changes are highlighted
| Date | 2019-07-10 | 2020-07-10 |
|---|---|---|
| Name | digitalrisks.fi | digitalrisks.fi |
| State | Registered | Validity expired |
| Holder | Digital Risks | Digital Risks |
| Address | 180 Borough High St | 180 Borough High St |
| Country | United Kingdom (GB) | United Kingdom (GB) |
| GrantDate | 2019-07-09T11:33:35.343 | 2019-07-09T11:33:35.343 |
| Registrar | Gandi SAS | Gandi SAS |
| PostalArea | London | London |
| PostalCode | SE1 1LB | SE1 1LB |
| NameServer1 | ns-1203.awsdns-22.org | ns-1203.awsdns-22.org |
| NameServer2 | ns-1711.awsdns-21.co.uk | ns-1711.awsdns-21.co.uk |
| NameServer3 | ns-547.awsdns-04.net | ns-547.awsdns-04.net |
| NameServer4 | ns-8.awsdns-01.com | ns-8.awsdns-01.com |
| PhoneNumber | +44.7538164347 | +44.7538164347 |
| IsDNSSecInUse | no | no |
| OrganizationId | 9265254 | 9265254 |
| AssociationType | Company | Company |
| LastValidityDate | 2020-07-09T11:33:35.343 | 2020-07-09T11:33:35.343 |
| DepartmentOrContactPerson |
Server response for digitalrisks.fi
Source: Web server reponse - Timestamp: 2020-05-22 09:04| Final URL | |
| HTTP Return Code | |
| IP Address | |
| Server Header | Server: Via: |
| Certificate | Not available Using certificate is highly recommended for Search Engine Optimization (SEO) If your website has an certificate and you are still seing this warning it means that your web server is not configured properly to redirect traffic to an https address |
Used technologies on digitalrisks.fi
Source: Web page analysis - Timestamp: 2020-05-22 09:04| Latest review | 2020-05-22 09:04 |
| Page language (from header) | en-US (This is often false!) |
| Technologies |  Google Font API (Font Scripts) (100% propable) Sentry (Issue Trackers) (100% propable) Squarespace (CMS) (100% propable) Typekit 1.19.2 (Font Scripts) (100% propable) YUI 3.17.2 (JavaScript Libraries) (100% propable) webpack (Miscellaneous) (100% propable) |
Known subdomains for digitalrisks.fi
Source: Search engines and DNS records (NOTICE: Most may not be reachable (internal/DMZ/obsolete)). Showing max rows 700No subdomains found
Web hosting providers
Source: All valid company websites with content (see below table)Not enough data to present a graph