reallifecam.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 105 days left15 years oldTranco #28087
65
reallifecam.com was registered on 7 Apr 2011 via Name.com, Inc. and the registry expiry is 7 Apr 2030. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/reallifecam.com.
reallifecam.com publishes 4 nameservers. DNSSEC is not signed.
reallifecam.com has 10 IPv4 addresses (178.162.194.102, 208.74.148.102, 208.74.148.103, 208.74.148.110, 208.74.148.111, 208.74.148.112, 212.32.228.194, 212.32.228.217, 212.32.228.218, 51.75.130.187). The geolocation database places 178.162.194.102 in Frankfurt am Main (Innenstadt I), Germany.
The TLS certificate from Sectigo Public Server Authentication CA DV R36 is valid and has 105 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named jQuery. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
reallifecam.com was registered on 7 Apr 2011 via Name.com, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/reallifecam.com.
| Registered | since 7 Apr 2011 |
|---|---|
| Created | 7 April 2011 |
| Updated | 8 March 2025 |
| Expires | 7 April 2030 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1dns.name.com, ns2dqx.name.com, ns3jwx.name.com, ns4cpw.name.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/reallifecam.com |
reallifecam.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 ns1dns.name.com is published for reallifecam.com in the registration record from https://rdap.verisign.com/com/v1/domain/reallifecam.com.
Nameserver ns2dqx.name.com is published for reallifecam.com in the registration record from https://rdap.verisign.com/com/v1/domain/reallifecam.com.
Nameserver ns3jwx.name.com is published for reallifecam.com in the registration record from https://rdap.verisign.com/com/v1/domain/reallifecam.com.
Nameserver ns4cpw.name.com is published for reallifecam.com in the registration record from https://rdap.verisign.com/com/v1/domain/reallifecam.com.
DNS
reallifecam.com has 10 address records, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 178.162.194.102, 208.74.148.102, 208.74.148.103, 208.74.148.110, 208.74.148.111, 208.74.148.112, 212.32.228.194, 212.32.228.217, 212.32.228.218, 51.75.130.187 |
|---|---|
| AAAA | — |
| NS | ns1dns.name.com, ns2dqx.name.com, ns3jwx.name.com, ns4cpw.name.com |
| MX | mx1.startmail.com (10), mx2.startmail.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at reallifecam.com is "v=spf1 include:_spf.smtp.com include:mailgun.org include:spf.startmail.com include:_spf.reallifecam.com -all".
The DMARC text record at _dmarc.reallifecam.com is "v=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1;".
IPv4 address 178.162.194.102 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 208.74.148.102 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 208.74.148.103 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 208.74.148.110 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 208.74.148.111 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 208.74.148.112 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 212.32.228.194 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 212.32.228.217 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 212.32.228.218 answers for reallifecam.com at resolver 1.1.1.1:53.
IPv4 address 51.75.130.187 answers for reallifecam.com at resolver 1.1.1.1:53.
Mail exchanger mx1.startmail.com has preference 10.
Mail exchanger mx2.startmail.com has preference 10.
A random label under reallifecam.com also resolved, which means wildcard DNS is on.
Hosting and geo
reallifecam.com is placed in Frankfurt am Main (Innenstadt I), Germany by the local geolocation database (db-ip).
| Address | 178.162.194.102 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main (Innenstadt I) |
| Source | db-ip |
SSL/TLS
The certificate for reallifecam.com is valid, with 105 days left and 3 subject alternative names. Source: tls:443.
| Issuer | Sectigo Public Server Authentication CA DV R36 |
|---|---|
| Subject | reallifecam.com |
| Valid from | 22 September 2026 |
| Valid until | 13 February 2027 |
| Days left | 105 |
| SAN count | 3 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.reallifecam.com, *.static.reallifecam.com, reallifecam.com.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- jQuery · JavaScript libraries
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 211 ms. The target title is 34 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 211 ms |
| Title length | 34 yes |
| Quoted title | "RealLifeCam (RLC) - Real Life 24/7" |
| Meta description | "Unique project since 2011. The private life of other people live 24/7" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index, follow |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| 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 reallifecam.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for reallifecam.com. That resolver covers adult and malware names.
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 5 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 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
- October 2026: geo city changed from empty to Frankfurt am Main (Innenstadt I).
- October 2026: geo country changed from empty to Germany.
Questions
Is reallifecam.com safe?
Cloudflare family DNS returned a block for reallifecam.com. That resolver covers adult and malware names.
Who hosts reallifecam.com?
reallifecam.com is placed in Frankfurt am Main (Innenstadt I), Germany.
When does reallifecam.com expire?
reallifecam.com expires on 7 April 2030 according to https://rdap.verisign.com/com/v1/domain/reallifecam.com.
Who owns reallifecam.com?
The registry did not return a person or a company for reallifecam.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/reallifecam.com at 2026-10-30T14:11:30Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:11:30Z
- TLS source tls:443 at 2026-10-30T14:11:30Z
- HTTP source https://reallifecam.com/ at 2026-10-30T14:11:30Z
- Tech source wappalyzergo at 2026-10-30T14:11:30Z
- Geo source db-ip at 2026-10-30T14:11:30Z
- Safety source family DNS and local lists at 2026-10-30T14:11:30Z
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.