sageworld.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
85
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
85
sageworld.com was registered on 15 Jun 1998 via Network Solutions, LLC and the registry expiry is 14 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/sageworld.com.
sageworld.com publishes 2 nameservers. DNSSEC is not signed.
sageworld.com has 1 IPv4 address (208.215.218.211). The geolocation database places 208.215.218.211 in Addison, United States.
The TLS certificate from YR1 is valid and has 46 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Font Awesome, Google Analytics, Modernizr, YouTube, ZURB Foundation, cdnjs, jQuery, jQuery CDN and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for sageworld.com in the checks that ran.
sageworld.com was registered on 15 Jun 1998 via Network Solutions, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/sageworld.com.
| Registered | since 15 Jun 1998 |
|---|---|
| Created | 15 June 1998 |
| Updated | 31 May 2026 |
| Expires | 14 June 2027 |
| Registrar | Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | ns3.qti.com, ns4.qti.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/sageworld.com |
sageworld.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.
Nameserver ns3.qti.com is published for sageworld.com in the registration record from https://rdap.verisign.com/com/v1/domain/sageworld.com.
Nameserver ns4.qti.com is published for sageworld.com in the registration record from https://rdap.verisign.com/com/v1/domain/sageworld.com.
sageworld.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 208.215.218.211 |
|---|---|
| AAAA | — |
| NS | ns3.qti.com, ns4.qti.com |
| MX | smtp-gw.qti.com (5) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at sageworld.com is "v=spf1 mx a ip4:208.215.218.0/23 -all".
The DMARC text record at _dmarc.sageworld.com is "v=DMARC1;p=reject;".
IPv4 address 208.215.218.211 answers for sageworld.com at resolver 1.1.1.1:53.
Mail exchanger smtp-gw.qti.com has preference 5.
sageworld.com is placed in Addison, United States by the local geolocation database (db-ip).
| Address | 208.215.218.211 |
|---|---|
| Country | United States |
| City | Addison |
| Source | db-ip |
The certificate for sageworld.com is valid, with 46 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | www.sageworld.com |
| Valid from | 18 September 2026 |
| Valid until | 17 December 2026 |
| Days left | 46 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: sageworld.com, www.sageworld.com.
Tech detection checked the fetched homepage and named 11 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Font Awesome is filed under Font scripts.
Google Analytics is filed under Analytics.
Modernizr is filed under JavaScript libraries.
YouTube is filed under Video players.
ZURB Foundation is filed under UI frameworks.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
reCAPTCHA is filed under Security.
The homepage returned HTTP 200 in 135 ms. The target title is 55 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 135 ms |
| Title length | 55 yes |
| Quoted title | "SAGE - Promotional Product Research and Marketing Tools" |
| Meta description | "Research, business management, and marketing solutions for the promotional products industry." yes |
| H1 count | 2 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 71 |
| Images | 50 |
| 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 sageworld.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 | yes |
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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
sageworld.com is placed in Addison, United States.
sageworld.com expires on 14 June 2027 according to https://rdap.verisign.com/com/v1/domain/sageworld.com.
The registry did not return a person or a company for sageworld.com. RDAP often redacts the registrant. The registrar on file is Network Solutions, LLC.
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.