ipaspot.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 85 days left2 years old
70
ipaspot.app was registered on 8 Jun 2024 via Sav.com, LLC - 10 and the registry expiry is 8 Jun 2027. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/ipaspot.app.
ipaspot.app publishes 2 nameservers. DNSSEC is not signed.
ipaspot.app has 2 IPv4 addresses (157.90.33.73, 157.90.33.74). The geolocation database places 157.90.33.73 in Falkenstein, Germany.
The TLS certificate from YR1 is valid and has 85 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Angie, C and Perl. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for ipaspot.app in the checks that ran.
Domain · RDAP/WHOIS
ipaspot.app was registered on 8 Jun 2024 via Sav.com, LLC - 10. The registry returned 1 status value and 2 nameservers from https://pubapi.registry.google/rdap/domain/ipaspot.app.
| Registered | since 8 Jun 2024 |
|---|---|
| Created | 8 June 2024 |
| Updated | 24 May 2026 |
| Expires | 8 June 2027 |
| Registrar | Sav.com, LLC - 10 |
| Status | active |
| Nameservers | ns1.park-my-domain.net, ns2.park-my-domain.net |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/ipaspot.app |
Nameserver ns1.park-my-domain.net is published for ipaspot.app in the registration record from https://pubapi.registry.google/rdap/domain/ipaspot.app.
Nameserver ns2.park-my-domain.net is published for ipaspot.app in the registration record from https://pubapi.registry.google/rdap/domain/ipaspot.app.
DNS
ipaspot.app has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 157.90.33.73, 157.90.33.74 |
|---|---|
| AAAA | — |
| NS | ns1.park-my-domain.net, ns2.park-my-domain.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 157.90.33.73 answers for ipaspot.app at resolver 1.1.1.1:53.
IPv4 address 157.90.33.74 answers for ipaspot.app at resolver 1.1.1.1:53.
A random label under ipaspot.app also resolved, which means wildcard DNS is on.
Hosting and geo
ipaspot.app is placed in Falkenstein, Germany by the local geolocation database (db-ip).
| Address | 157.90.33.73 |
|---|---|
| Country | Germany |
| City | Falkenstein |
| Source | db-ip |
SSL/TLS
The certificate for ipaspot.app is valid, with 85 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | ipaspot.app |
| Valid from | 26 October 2026 |
| Valid until | 24 January 2027 |
| Days left | 85 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.ipaspot.app, ipaspot.app.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Angie · Web servers
- C · Programming languages
- Perl · Programming languages
Angie is filed under Web servers.
C is filed under Programming languages.
Perl is filed under Programming languages.
On-page checks
The homepage returned HTTP 200 in 3 ms. The target title is 0 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 3 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 2 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | — |
| Robots meta | noindex,noarchive,nofollow |
| Canonical | — |
| Language | en |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 ipaspot.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 | 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 0 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 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 Falkenstein.
- October 2026: geo country changed from empty to Germany.
Questions
Is ipaspot.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 ipaspot.app?
ipaspot.app is placed in Falkenstein, Germany.
When does ipaspot.app expire?
ipaspot.app expires on 8 June 2027 according to https://pubapi.registry.google/rdap/domain/ipaspot.app.
Who owns ipaspot.app?
The registry did not return a person or a company for ipaspot.app. RDAP often redacts the registrant. The registrar on file is Sav.com, LLC - 10.
Sources
- RDAP source https://pubapi.registry.google/rdap/domain/ipaspot.app at 2026-10-30T13:31:31Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:31:31Z
- TLS source tls:443 at 2026-10-30T13:31:31Z
- HTTP source https://ipaspot.app/ at 2026-10-30T13:31:31Z
- Tech source wappalyzergo at 2026-10-30T13:31:31Z
- Geo source db-ip at 2026-10-30T13:31:31Z
- Safety source family DNS and local lists at 2026-10-30T13:31:31Z
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.