Website profiles · Technology insights · Alternatives

wiewaswie.nl

Ontdek je voorouders en je familiegeschiedenis in meer dan 230 miljoen historische, genealogische bronnen.

No paid content found
Visit website
Profile views 13 Outbound visits 3 Normal
WieWasWie Full homepage screenshot

At a glance

Category
History & Archives
Language
English
Paid-content signal
No paid content foundObserved
Registered
2009
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Related questions

More questions →
What Is WieWasWie and How Can You Use It to Research Dutch Ancestors?

WieWasWie is a Dutch genealogy platform that lets you search historical records and view original documents to trace your ancestors. It is most useful if your family history leads back to the Netherlands, since its database draws on Dutch archives and participating institutions rather than being a general global genealogy site. The site states it holds more than 252 million persons in its database, and it points you toward both a basic search and an "Uitgebreid zoeken" (advanced search) option.

What WieWasWie actually is

WieWasWie ("Who Was Who") is built around searching old documents and then viewing the original. Its content comes from a long list of participating institutions, including:

  • Nationaal Archief
  • Stadsarchief Amsterdam
  • Haags Gemeentearchief
  • Het Utrechts Archief
  • Brabants Historisch Informatie Centrum
  • Drents Archief
  • Groninger Archieven
  • Zeeuws Archief
  • CBG|Centrum voor familiegeschiedenis

That institutional backing matters: records are tied to real archive collections, so when you find a match you are usually working with a source that has a provenance, not an unsourced user submission.

How to search the database

The site presents two main paths: a standard search and "Uitgebreid zoeken" (advanced search). The page does not spell out every field, so the practical approach is:

  1. Start with a name and a rough place or period.
  2. If results are too broad, switch to advanced search to narrow by record type, location, or date.
  3. Open a result to see the underlying document and, where available, view the original.

The stated goal of the platform is exactly this sequence: search old documents and view the original. Treat the index entry as a pointer, and the original scan as the evidence you actually evaluate.

What kinds of records you can expect

The site describes its holdings as historical and genealogical sources. In Dutch genealogy these typically cover birth, marriage, and death records, plus other historical documents held by the participating archives. The page itself does not enumerate every record category, so check what a specific institution has contributed before assuming a type of record is included.

Premium access: what it adds

WieWasWie describes a Premiumtoegang (Premium access) with two concrete features:

Feature What it does
Search two people at once Lets you look for two individuals simultaneously
Wildcards * and ? Searches spelling variants of one name, e.g. "Graaf" and "Graeff"

The wildcard function is the more important one for Dutch research, because surname spelling was not standardized historically. If your ancestor appears as "Graeff" in one record and "Graaf" in another, wildcards help you catch both. The page mentions Premium and links to a subscription, but it does not state a price here, so check the subscription page for current terms rather than assuming cost or free access.

The privacy wall and the NRO workaround

A key limitation: because of privacy legislation, you probably will not find recently deceased ancestors in WieWasWie. The site addresses this directly through the Nationaal Register van Overledenen (NRO), which it describes as offering researchers a flying start for people who died recently. The suggested route is to request an uittreksel (extract) from the NRO.

So the practical split is:

  • Older records → search WieWasWie directly.
  • Recent deaths → expect a gap in WieWasWie and use the NRO instead.

A realistic research sequence

For example, if you are looking for a grandfather who died in the 1970s in Rotterdam:

  1. Search WieWasWie first, but expect the recent record may be blocked by privacy rules.
  2. If it is blocked, request an NRO extract.
  3. For earlier generations, search WieWasWie with wildcards enabled if you have Premium, since name spellings will vary.
  4. Open the original document for each match to confirm the identity before adding it to your tree.

Practical takeaways

  • WieWasWie is strongest for Dutch ancestors and archive-backed sources.
  • Use advanced search when a simple name search returns too much.
  • Premium's wildcards are genuinely useful for Dutch name variants; the two-person search is a convenience feature.
  • Do not expect recent deaths in the database — the NRO is the stated alternative.
  • Always verify against the original document rather than trusting the index alone.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 2009, this domain has about 17 years of history. That suggests continuity, although ownership and purpose may have changed. The domain uses the common .nl extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Google Workspace email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies jQuery, Bootstrap, Google Tag Manager, Google Analytics, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 55 characters, within a common display range. A meta description is present, with 106 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.26.14.166

Registration details

RDAP / WHOIS

RegistrarRealtime Register
Registered2009-03-19
ExpiresUnknown
Domain statusactive
Nameservershank.ns.cloudflare.com、mimi.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Awiewaswie.nl104.26.14.166197—
Awiewaswie.nl104.26.15.166197—
Awiewaswie.nl172.67.72.33197—
AAAAwiewaswie.nl2606:4700:20::681a:ea6300—
AAAAwiewaswie.nl2606:4700:20::681a:fa6300—
AAAAwiewaswie.nl2606:4700:20::ac43:4821300—
MXwiewaswie.nlaspmx.l.google.com3001
MXwiewaswie.nlalt1.aspmx.l.google.com3003
MXwiewaswie.nlalt2.aspmx.l.google.com3003
MXwiewaswie.nlaspmx.l.google.com3005
MXwiewaswie.nlaspmx2.googlemail.com3005
MXwiewaswie.nlaspmx3.googlemail.com3005
MXwiewaswie.nlaspmx4.googlemail.com3005
MXwiewaswie.nlaspmx5.googlemail.com3005
NSwiewaswie.nlhank.ns.cloudflare.com86400—
NSwiewaswie.nlmimi.ns.cloudflare.com86400—
TXTwiewaswie.nlh1fga6ms63d2b25rug1s3d1ekf300—
TXTwiewaswie.nlh5nln0mvmpi2aeejq3lidc05dq300—
TXTwiewaswie.nlicue7ca0s5l66ifu0p8pum3lmm300—
TXTwiewaswie.nlv=spf1 include:sendgrid.net include:_spf.google.com ~all300—
DMARC_dmarc.wiewaswie.nlv=DMARC1; p=reject; rua=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwiewaswie.nl
IssuerGoogle Trust Services
Valid until2027-01-10T22:44 · Remaining when checked: 86 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlprivate
servercloudflare

Identified technologies

jQueryBootstrapGoogle Tag ManagerGoogle AnalyticsCloudflare

Pages, Search and Sharing

Meta descriptionOntdek je voorouders en je familiegeschiedenis in meer dan 230 miljoen historische, genealogische bronnen.
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

No robots.txt found

No sitemaps found

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information
  • HTTP Response Information
  • TLS and certificates
  • DNS Information
  • Domain Registration
  • Website profile
  • Website Description
  • Website Name
  • Website profile
  • Website Description
  • Website Name

User reviews (0)

  • No reviews yet.