searspabenefits.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe14 years old
35
searspabenefits.com was registered on 22 Aug 2012 via Amazon Registrar, Inc. and the registry expiry is 1 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
searspabenefits.com publishes 4 nameservers. DNSSEC is not signed.
searspabenefits.com has 4 IPv4 addresses (13.33.187.123, 13.33.187.124, 13.33.187.36, 13.33.187.84). The geolocation database places 13.33.187.123 in Frankfurt am Main, Germany.
No safety warning was recorded for searspabenefits.com in the checks that ran.
Domain · RDAP/WHOIS
searspabenefits.com was registered on 22 Aug 2012 via Amazon Registrar, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
| Registered | since 22 Aug 2012 |
|---|---|
| Created | 22 August 2012 |
| Updated | 27 November 2025 |
| Expires | 1 January 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | active |
| Nameservers | ns-1391.awsdns-45.org, ns-1725.awsdns-23.co.uk, ns-204.awsdns-25.com, ns-685.awsdns-21.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/searspabenefits.com |
Nameserver ns-1391.awsdns-45.org is published for searspabenefits.com in the registration record from https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
Nameserver ns-1725.awsdns-23.co.uk is published for searspabenefits.com in the registration record from https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
Nameserver ns-204.awsdns-25.com is published for searspabenefits.com in the registration record from https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
Nameserver ns-685.awsdns-21.net is published for searspabenefits.com in the registration record from https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
DNS
searspabenefits.com has 4 address records, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 13.33.187.123, 13.33.187.124, 13.33.187.36, 13.33.187.84 |
|---|---|
| AAAA | — |
| NS | ns-1391.awsdns-45.org, ns-1725.awsdns-23.co.uk, ns-204.awsdns-25.com, ns-685.awsdns-21.net |
| MX | searspabenefits-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.searspabenefits.com is "v=DMARC1; p=none; ruf=mailto:[email protected]; pct=100;".
IPv4 address 13.33.187.123 answers for searspabenefits.com at resolver 1.1.1.1:53.
IPv4 address 13.33.187.124 answers for searspabenefits.com at resolver 1.1.1.1:53.
IPv4 address 13.33.187.36 answers for searspabenefits.com at resolver 1.1.1.1:53.
IPv4 address 13.33.187.84 answers for searspabenefits.com at resolver 1.1.1.1:53.
Mail exchanger searspabenefits-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
searspabenefits.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 13.33.187.123 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for searspabenefits.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
remote error: tls: handshake failure
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://searspabenefits.com/": remote error: tls: handshake failure
Security
Family DNS for searspabenefits.com 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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is searspabenefits.com 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 searspabenefits.com?
searspabenefits.com is placed in Frankfurt am Main, Germany.
When does searspabenefits.com expire?
searspabenefits.com expires on 1 January 2027 according to https://rdap.verisign.com/com/v1/domain/searspabenefits.com.
Who owns searspabenefits.com?
The registry did not return a person or a company for searspabenefits.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/searspabenefits.com at 2026-10-30T14:13:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:13:07Z
- TLS source tls:443 at 2026-10-30T14:13:07Z
- HTTP source https://searspabenefits.com/ at 2026-10-30T14:13:07Z
- Tech source not available at 2026-10-30T14:13:07Z
- Geo source db-ip at 2026-10-30T14:13:07Z
- Safety source family DNS and local lists at 2026-10-30T14:13:07Z
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.