sugarsearch.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 115 days left15 years old
65
sugarsearch.com was registered on 11 Feb 2011 via GoDaddy.com, LLC and the registry expiry is 11 Feb 2032. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
sugarsearch.com publishes 4 nameservers. DNSSEC is not signed.
sugarsearch.com has 4 IPv4 addresses (65.9.130.111, 65.9.130.36, 65.9.130.75, 65.9.130.81). The geolocation database places 65.9.130.111 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M01 is valid and has 115 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon S3, Amazon Web Services and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for sugarsearch.com in the checks that ran.
Domain · RDAP/WHOIS
sugarsearch.com was registered on 11 Feb 2011 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
| Registered | since 11 Feb 2011 |
|---|---|
| Created | 11 February 2011 |
| Updated | 15 October 2025 |
| Expires | 11 February 2032 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1242.awsdns-27.org, ns-1867.awsdns-41.co.uk, ns-576.awsdns-08.net, ns-94.awsdns-11.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/sugarsearch.com |
sugarsearch.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
sugarsearch.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
sugarsearch.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.
sugarsearch.com 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 ns-1242.awsdns-27.org is published for sugarsearch.com in the registration record from https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
Nameserver ns-1867.awsdns-41.co.uk is published for sugarsearch.com in the registration record from https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
Nameserver ns-576.awsdns-08.net is published for sugarsearch.com in the registration record from https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
Nameserver ns-94.awsdns-11.com is published for sugarsearch.com in the registration record from https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
DNS
sugarsearch.com has 4 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 65.9.130.111, 65.9.130.36, 65.9.130.75, 65.9.130.81 |
|---|---|
| AAAA | — |
| NS | ns-1242.awsdns-27.org, ns-1867.awsdns-41.co.uk, ns-576.awsdns-08.net, ns-94.awsdns-11.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 65.9.130.111 answers for sugarsearch.com at resolver 1.1.1.1:53.
IPv4 address 65.9.130.36 answers for sugarsearch.com at resolver 1.1.1.1:53.
IPv4 address 65.9.130.75 answers for sugarsearch.com at resolver 1.1.1.1:53.
IPv4 address 65.9.130.81 answers for sugarsearch.com at resolver 1.1.1.1:53.
Hosting and geo
sugarsearch.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 65.9.130.111 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for sugarsearch.com is valid, with 115 days left and 9 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M01 |
|---|---|
| Subject | sufardaddy.com |
| Valid from | 26 January 2026 |
| Valid until | 24 February 2027 |
| Days left | 115 |
| SAN count | 9 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: eliteandsweet.com, sufardaddy.com, sugardadfy.com, sugardadsy.com, sugardaffy.com, sugardardy.com, sugardasdy.com, sugardsddy.com, sugarsearch.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Amazon CloudFront · CDN
- Amazon S3 · CDN
- Amazon Web Services · PaaS
- HTTP/3 · Miscellaneous
Amazon CloudFront is filed under CDN.
Amazon S3 is filed under CDN.
Amazon Web Services is filed under PaaS.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 8 ms. The target title is 0 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 8 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | "Sugar Daddy & Sugar Baby Dating" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | noindex |
| Canonical | — |
| Language | — |
| Links | 1 |
| 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 sugarsearch.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 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 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: dns a changed from 3.173.161.10,3.173.161.41,3.173.161.57,3.173.161.83 to 65.9.130.111,65.9.130.36,65.9.130.75,65.9.130.81.
Questions
Is sugarsearch.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 sugarsearch.com?
sugarsearch.com is placed in Frankfurt am Main, Germany.
When does sugarsearch.com expire?
sugarsearch.com expires on 11 February 2032 according to https://rdap.verisign.com/com/v1/domain/sugarsearch.com.
Who owns sugarsearch.com?
The registry did not return a person or a company for sugarsearch.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/sugarsearch.com at 2026-10-30T14:15:13Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:15:13Z
- TLS source tls:443 at 2026-10-30T14:15:13Z
- HTTP source https://sugarsearch.com/ at 2026-10-30T14:15:13Z
- Tech source wappalyzergo at 2026-10-30T14:15:13Z
- Geo source db-ip at 2026-10-30T14:15:13Z
- Safety source family DNS and local lists at 2026-10-30T14:15:13Z
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.