spicer.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 59 days left8 years oldTranco #995534
75
spicer.app was registered on 8 May 2018 via Name.com, Inc. and the registry expiry is 8 May 2027. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/spicer.app.
spicer.app publishes 4 nameservers. DNSSEC is not signed.
spicer.app has 1 IPv4 address (65.108.142.126). The geolocation database places 65.108.142.126 in Helsinki, Finland.
The TLS certificate from YR1 is valid and has 59 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Bootstrap, Google Analytics, Nginx, jQuery and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for spicer.app in the checks that ran.
Domain · RDAP/WHOIS
spicer.app was registered on 8 May 2018 via Name.com, Inc.. The registry returned 2 status values and 4 nameservers from https://pubapi.registry.google/rdap/domain/spicer.app.
| Registered | since 8 May 2018 |
|---|---|
| Created | 8 May 2018 |
| Updated | 21 February 2026 |
| Expires | 8 May 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | ns1lmy.name.com, ns2dky.name.com, ns3qty.name.com, ns4lqx.name.com |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/spicer.app |
spicer.app 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.
spicer.app carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns1lmy.name.com is published for spicer.app in the registration record from https://pubapi.registry.google/rdap/domain/spicer.app.
Nameserver ns2dky.name.com is published for spicer.app in the registration record from https://pubapi.registry.google/rdap/domain/spicer.app.
Nameserver ns3qty.name.com is published for spicer.app in the registration record from https://pubapi.registry.google/rdap/domain/spicer.app.
Nameserver ns4lqx.name.com is published for spicer.app in the registration record from https://pubapi.registry.google/rdap/domain/spicer.app.
DNS
spicer.app has 1 address record, 6 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 65.108.142.126 |
|---|---|
| AAAA | — |
| NS | ns1lmy.name.com, ns2dky.name.com, ns3qty.name.com, ns4lqx.name.com |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (30) Google, aspmx2.googlemail.com (40) Google, aspmx3.googlemail.com (50) Google, steepway.com (100) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at spicer.app is "v=spf1 ip4:65.108.142.126 include:_spf.google.com ~all".
The DMARC text record at _dmarc.spicer.app is "v=DMARC1; p=none; aspf=r; rua=mailto:[email protected]".
IPv4 address 65.108.142.126 answers for spicer.app at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 40. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 50. The host is recognised as Google.
Mail exchanger steepway.com has preference 100.
Hosting and geo
spicer.app is placed in Helsinki, Finland by the local geolocation database (db-ip).
| Address | 65.108.142.126 |
|---|---|
| Country | Finland |
| City | Helsinki |
| Source | db-ip |
SSL/TLS
The certificate for spicer.app is valid, with 59 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | spicer.app |
| Valid from | 1 October 2026 |
| Valid until | 30 December 2026 |
| Days left | 59 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: spicer.app, www.spicer.app.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Google Analytics · Analytics
- Nginx · Web servers, Reverse proxies
- jQuery · JavaScript libraries
- reCAPTCHA · Security
Bootstrap is filed under UI frameworks.
Google Analytics is filed under Analytics.
Nginx is filed under Web servers, Reverse proxies.
jQuery is filed under JavaScript libraries.
reCAPTCHA is filed under Security.
On-page checks
The homepage returned HTTP 200 in 28 ms. The target title is 28 characters and the page has 10 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 28 ms |
| Title length | 28 yes |
| Quoted title | "Spicer - Sex App For Couples" |
| Meta description | "Spicer is the Sex App for couples. Spicer allows couples to discover new sex ideas and improve communication, intimacy and sex life. Install on iOS or Android and discover new sex ideas you BOTH like." yes |
| H1 count | 10 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://spicer.app/ |
| Language | en |
| Links | 24 |
| Images | 17 |
| 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 spicer.app 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 | no |
| CSP | no |
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 0 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
- October 2026: geo city changed from empty to Helsinki.
- October 2026: geo country changed from empty to Finland.
Questions
Is spicer.app 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 spicer.app?
spicer.app is placed in Helsinki, Finland.
When does spicer.app expire?
spicer.app expires on 8 May 2027 according to https://pubapi.registry.google/rdap/domain/spicer.app.
Who owns spicer.app?
The registry did not return a person or a company for spicer.app. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://pubapi.registry.google/rdap/domain/spicer.app at 2026-10-30T13:31:52Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:31:52Z
- TLS source tls:443 at 2026-10-30T13:31:52Z
- HTTP source https://spicer.app/ at 2026-10-30T13:31:52Z
- Tech source wappalyzergo at 2026-10-30T13:31:52Z
- Geo source db-ip at 2026-10-30T13:31:52Z
- Safety source family DNS and local lists at 2026-10-30T13:31:52Z
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.