frontnieuws.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 54 days left6 years oldTranco #456736
90
frontnieuws.com was registered on 10 Apr 2020 via DreamHost, LLC and the registry expiry is 10 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/frontnieuws.com.
frontnieuws.com publishes 2 nameservers. DNSSEC is not signed.
frontnieuws.com has 3 IPv4 addresses (104.26.4.187, 104.26.5.187, 172.67.71.149) and 3 IPv6 addresses (2606:4700:20::681a:4bb, 2606:4700:20::681a:5bb, 2606:4700:20::ac43:4795). The geolocation database places 104.26.4.187 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 54 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, CookieYes, HSTS, MySQL, PHP, Redis, Redis Object Cache, WordPress, Yoast SEO, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for frontnieuws.com in the checks that ran.
Domain · RDAP/WHOIS
frontnieuws.com was registered on 10 Apr 2020 via DreamHost, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/frontnieuws.com.
| Registered | since 10 Apr 2020 |
|---|---|
| Created | 10 April 2020 |
| Updated | 9 February 2026 |
| Expires | 10 April 2027 |
| Registrar | DreamHost, LLC |
| Status | client transfer prohibited |
| Nameservers | chris.ns.cloudflare.com, elsa.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/frontnieuws.com |
frontnieuws.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver chris.ns.cloudflare.com is published for frontnieuws.com in the registration record from https://rdap.verisign.com/com/v1/domain/frontnieuws.com.
Nameserver elsa.ns.cloudflare.com is published for frontnieuws.com in the registration record from https://rdap.verisign.com/com/v1/domain/frontnieuws.com.
DNS
frontnieuws.com has 6 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.4.187, 104.26.5.187, 172.67.71.149 |
|---|---|
| AAAA | 2606:4700:20::681a:4bb, 2606:4700:20::681a:5bb, 2606:4700:20::ac43:4795 |
| NS | chris.ns.cloudflare.com, elsa.ns.cloudflare.com |
| MX | mx1.mailchannels.net (0), mx2.mailchannels.net (0) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at frontnieuws.com is "v=spf1 ip4:64.90.62.0/24 ip4:184.105.182.0/24 ip4:35.190.247.0/24 ip4:209.85.128.0/17 ip4:23.83.208.0/20 ip4:35.85.190.185 ip4:107.180.249.174 mx a include:_spf.mlsend.com ~all".
The DMARC text record at _dmarc.frontnieuws.com is "v=DMARC1; p=quarantine; fo=1;rua=mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected]; pc…".
IPv4 address 104.26.4.187 answers for frontnieuws.com at resolver 1.1.1.1:53.
IPv4 address 104.26.5.187 answers for frontnieuws.com at resolver 1.1.1.1:53.
IPv4 address 172.67.71.149 answers for frontnieuws.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:4bb answers for frontnieuws.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:5bb answers for frontnieuws.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4795 answers for frontnieuws.com at resolver 1.1.1.1:53.
Mail exchanger mx1.mailchannels.net has preference 0.
Mail exchanger mx2.mailchannels.net has preference 0.
Hosting and geo
frontnieuws.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.4.187 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for frontnieuws.com is valid, with 54 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | frontnieuws.com |
| Valid from | 25 September 2026 |
| Valid until | 24 December 2026 |
| Days left | 54 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.frontnieuws.com, frontnieuws.com.
Tech stack
Tech detection checked the fetched homepage and named 11 products. Source: wappalyzergo.
- Cloudflare · CDN
- CookieYes · Cookie compliance
- HSTS · Security
- MySQL · Databases
- PHP · Programming languages
- Redis · Databases
- Redis Object Cache · Caching
- WordPress · CMS, Blogs
- Yoast SEO · SEO, WordPress plugins
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Cloudflare is filed under CDN.
CookieYes is filed under Cookie compliance.
HSTS is filed under Security.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Redis is filed under Databases.
Redis Object Cache is filed under Caching.
WordPress is filed under CMS, Blogs.
Yoast SEO is filed under SEO, WordPress plugins.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 453 ms. The target title is 43 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 453 ms |
| Title length | 43 yes |
| Quoted title | "Frontnieuws - Je maintiendrai - Frontnieuws" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1 |
| Canonical | https://www.frontnieuws.com/ |
| Language | nl-NL |
| Links | 203 |
| Images | 11 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for frontnieuws.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is frontnieuws.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts frontnieuws.com?
frontnieuws.com is placed in Toronto, Canada.
When does frontnieuws.com expire?
frontnieuws.com expires on 10 April 2027 according to https://rdap.verisign.com/com/v1/domain/frontnieuws.com.
Who owns frontnieuws.com?
The registry did not return a person or a company for frontnieuws.com. RDAP often redacts the registrant. The registrar on file is DreamHost, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/frontnieuws.com at 2026-10-30T13:55:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:55:22Z
- TLS source tls:443 at 2026-10-30T13:55:22Z
- HTTP source https://frontnieuws.com/ at 2026-10-30T13:55:22Z
- Tech source wappalyzergo at 2026-10-30T13:55:22Z
- Geo source db-ip at 2026-10-30T13:55:22Z
- Safety source family DNS and local lists at 2026-10-30T13:55:22Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.