perisexscope.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
perisexscope.com was registered on 1 Feb 2020 via Amazon Registrar, Inc. and the registry expiry is 1 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/perisexscope.com.
perisexscope.com publishes 4 nameservers. DNSSEC is not signed.
perisexscope.com has 4 IPv4 addresses (18.245.86.46, 18.245.86.77, 18.245.86.91, 18.245.86.96). The geolocation database places 18.245.86.46 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 174 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon S3, Amazon Web Services, Bootstrap, BootstrapCDN, Cloudflare, Google Tag Manager, Popper, cdnjs, jQuery and jQuery CDN. The fingerprints ran on the homepage that was already downloaded.
perisexscope.com was registered on 1 Feb 2020 via Amazon Registrar, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/perisexscope.com.
| Registered | since 1 Feb 2020 |
|---|---|
| Created | 1 February 2020 |
| Updated | 28 December 2025 |
| Expires | 1 February 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | active |
| Nameservers | ns-1097.awsdns-09.org, ns-1781.awsdns-30.co.uk, ns-387.awsdns-48.com, ns-852.awsdns-42.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/perisexscope.com |
Nameserver ns-1097.awsdns-09.org is published for perisexscope.com in the registration record from https://rdap.verisign.com/com/v1/domain/perisexscope.com.
Nameserver ns-1781.awsdns-30.co.uk is published for perisexscope.com in the registration record from https://rdap.verisign.com/com/v1/domain/perisexscope.com.
Nameserver ns-387.awsdns-48.com is published for perisexscope.com in the registration record from https://rdap.verisign.com/com/v1/domain/perisexscope.com.
Nameserver ns-852.awsdns-42.net is published for perisexscope.com in the registration record from https://rdap.verisign.com/com/v1/domain/perisexscope.com.
perisexscope.com has 4 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.245.86.46, 18.245.86.77, 18.245.86.91, 18.245.86.96 |
|---|---|
| AAAA | — |
| NS | ns-1097.awsdns-09.org, ns-1781.awsdns-30.co.uk, ns-387.awsdns-48.com, ns-852.awsdns-42.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 18.245.86.46 answers for perisexscope.com at resolver 1.1.1.1:53.
IPv4 address 18.245.86.77 answers for perisexscope.com at resolver 1.1.1.1:53.
IPv4 address 18.245.86.91 answers for perisexscope.com at resolver 1.1.1.1:53.
IPv4 address 18.245.86.96 answers for perisexscope.com at resolver 1.1.1.1:53.
perisexscope.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 18.245.86.46 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
The certificate for perisexscope.com is valid, with 174 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | perisexscope.com |
| Valid from | 8 October 2026 |
| Valid until | 23 April 2027 |
| Days left | 174 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: perisexscope.com, www.perisexscope.com.
Tech detection checked the fetched homepage and named 11 products. Source: wappalyzergo.
Amazon CloudFront is filed under CDN.
Amazon S3 is filed under CDN.
Amazon Web Services is filed under PaaS.
Bootstrap is filed under UI frameworks.
BootstrapCDN is filed under CDN.
Cloudflare is filed under CDN.
Google Tag Manager is filed under Tag managers.
Popper is filed under Miscellaneous.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
The homepage returned HTTP 200 in 5 ms. The target title is 12 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 5 ms |
| Title length | 12 yes |
| Quoted title | "PeriSexScope" |
| Meta description | "PeriSexScope" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | https://perisexscope.com/ |
| Language | en |
| Links | 259 |
| Images | 28 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for perisexscope.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 perisexscope.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.
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 0 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for perisexscope.com. That resolver covers adult and malware names.
perisexscope.com is placed in Frankfurt am Main, Germany.
perisexscope.com expires on 1 February 2027 according to https://rdap.verisign.com/com/v1/domain/perisexscope.com.
The registry did not return a person or a company for perisexscope.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.