aupair.com — domain analysis
aupair.com describes itself as "Find the right Au Pair or Host Family safely and directly. Discover thousands of active, verified profiles worldwide and register for free.". It was registered in 1999, served from Cologne, Germany. It has a valid HTTPS certificate, 4 of 6 common security headers, 1 tracking script.
What is aupair.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- pair ×71
- host ×22
- family ×22
- aupair ×20
- experience ×19
- find ×15
- destinations ×14
- pairs ×13
- germany ×12
- language ×10
Does aupair.com publish the usual trust pages?
None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does aupair.com compare with other domains analysed here?
Measured against the 11 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 91% of them (median 814ms) |
|---|---|
| Security headers | More than 50% of them |
| Domain age | Older than 70% of them |
Related domains in this index
Analysed domains built on a similar stack:
When was aupair.com registered?
aupair.com was registered on 26 March 1999, which makes it about 27 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is Mesh Digital Limited.
Registration runs until 26 March 2027.
| Registered | 26 March 1999 |
|---|---|
| Expires | 26 March 2027 |
| Registrar | Mesh Digital Limited |
| Registry status | active |
Where is aupair.com hosted?
The first address resolves to infrastructure in Cologne, Germany.
The network is operated by Hosteurope GmbH (AS34011 Host Europe GmbH).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is aupair.com running on?
aupair.com exposes 1 identifiable technology: Google Tag Manager.
Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.
- Google Tag Manager
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 322ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 76KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | Apache |
|---|---|
| Compression | gzip |
| Page size | 77,706 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 58 characters, inside the range that displays without truncation.
A meta description of 139 characters is present.
1 of 48 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.
| Title | AuPair.com – Find your Au Pair today or discover the world (58 chars) |
|---|---|
| Meta description | Find the right Au Pair or Host Family safely and directly. Discover thousands of active, verified profiles worldwide and register for free. (139 chars) |
| H1 | Find your Au Pair or your Host Family safely and easily! (1 on the page) |
| Canonical | not set |
| Open Graph title | AuPair.com – Find your Au Pair today or discover the world |
| Headings / images | 10 H2s, 48 images (1 without alt text) |
Is aupair.com served over a valid certificate?
The HTTPS certificate is issued by Starfield Technologies, Inc. and is
valid until 2026-12-06, which is 62 days from the date of this check. It covers
2 hostnames.
- www.aupair.com
- aupair.com
The certificate has 62 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
4 of 6 are set (HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy). Absent: Content Security Policy, Permissions-Policy.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=63072000; includeSubDomains; preload |
| Content Security Policy | no | — |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | yes | same-origin |
| Permissions-Policy | no | — |
How is DNS configured for aupair.com?
| IP addresses | 87.230.62.153, 2a01:488:42:1000:57e6:3e99:ee:6884 |
|---|---|
| Reverse DNS | vwp0658.webpack.hosteurope.de, 2a01:488:42:1000:57e6:3e99:ee:6884 |
| Name servers | ns36.domaincontrol.com, ns35.domaincontrol.com |
| Mail (MX) | mx0.aupair.com (pri 50) |
| SPF | v=spf1 mx a include:spf.server-he.de -all |
| TXT records | 3 |
aupair.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to vwp0658.webpack.hosteurope.de, 2a01:488:42:1000:57e6:3e99:ee:6884, which usually names the hosting provider.
Who runs DNS and mail for aupair.com?
DNS is operated by GoDaddy rather than self-hosted name servers.
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
The domain publishes AAAA records and accepts connections over IPv6.
Can aupair.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 3,984 bytes and names
34 user-agent groups.
It does not blanket-disallow general crawlers.
No sitemap is declared in robots.txt.
AI crawler policy
| Crawler | Policy |
|---|---|
| perplexitybot | blocked |
| bytespider | blocked |
No sitemap is declared in robots.txt, so crawlers must discover pages by following links.
Every named AI crawler is blocked (perplexitybot, bytespider). This domain has opted out of AI training and AI answer surfaces wholesale.
What structured data does the homepage publish?
- Organization
- ContactPoint
- Place
- PostalAddress
- LocalBusiness
- WebSite
The homepage publishes 6 structured data types: Organization, ContactPoint, Place, PostalAddress, LocalBusiness, WebSite.
What does aupair.com load from third parties?
The homepage loads no resources from third-party hosts at all, which is rare and means visiting it tells no other company that you did.
1 cookie is set before any interaction (PHPSESSID). 1 lacks the Secure flag.
The page links or refers to X/Twitter, LinkedIn, Facebook, Instagram, YouTube.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| PHPSESSID | no | no | none/unset |
Does aupair.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both aupair.com and www.aupair.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can aupair.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does aupair.com run?
1 tracking script detected: Google Tag Manager.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does aupair.com look when shared?
4 of 5 social preview tags are set. Missing: twitter:card.
The page declares 10 hreflang alternates (en, de, pl, es, pt, it, ru, zh, fr, x-default), so it targets more than one language or region.
How are images, fonts and scripts handled?
49 images on the homepage, 43 of them lazy-loaded (88%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 1 external stylesheet and 0 external scripts, with 0 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Is aupair.com accessible and current?
The page uses 12 landmark elements and 0 ARIA attributes.
There are 8 form inputs but only 3 label elements, so some fields may be unlabelled for screen readers.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index aupair.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 154 internal and 8 external links across 8 outside hosts.
Visible text makes up 18% of the HTML.
How is aupair.com delivered?
The HTML is served with Cache-Control: no-cache, must-revalidate, post-check=7200, pre-check=7200.
The TLS certificate also covers 1 subdomain: www.aupair.com.
- www.aupair.com
Frequently asked questions
Does aupair.com set the usual HTTP security headers?
It sets 4 of 6. The ones not present are: Content Security Policy, Permissions-Policy.
Does aupair.com allow AI crawlers?
No — robots.txt blocks perplexitybot, bytespider.
What is aupair.com built with?
The homepage exposes these fingerprints: Google Tag Manager. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own aupair.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026.
Analyse another domain →