lynxdefense.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 77 days left16 years old
95
lynxdefense.com was registered on 12 Jul 2010 via Cloudflare, Inc. and the registry expiry is 12 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/lynxdefense.com.
lynxdefense.com publishes 2 nameservers. DNSSEC is signed.
lynxdefense.com has 3 IPv4 addresses (104.26.2.193, 104.26.3.193, 172.67.72.28) and 3 IPv6 addresses (2606:4700:20::681a:2c1, 2606:4700:20::681a:3c1, 2606:4700:20::ac43:481c). The geolocation database places 104.26.2.193 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 77 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Alpine.js, Cloudflare, Cloudflare Browser Insights, HSTS, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache and PayPal. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for lynxdefense.com in the checks that ran.
Domain · RDAP/WHOIS
lynxdefense.com was registered on 12 Jul 2010 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/lynxdefense.com.
| Registered | since 12 Jul 2010 |
|---|---|
| Created | 12 July 2010 |
| Updated | 2 April 2024 |
| Expires | 12 July 2027 |
| Registrar | Cloudflare, Inc. |
| Status | client transfer prohibited |
| Nameservers | henry.ns.cloudflare.com, natasha.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/lynxdefense.com |
lynxdefense.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 henry.ns.cloudflare.com is published for lynxdefense.com in the registration record from https://rdap.verisign.com/com/v1/domain/lynxdefense.com.
Nameserver natasha.ns.cloudflare.com is published for lynxdefense.com in the registration record from https://rdap.verisign.com/com/v1/domain/lynxdefense.com.
DNS
lynxdefense.com has 6 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.2.193, 104.26.3.193, 172.67.72.28 |
|---|---|
| AAAA | 2606:4700:20::681a:2c1, 2606:4700:20::681a:3c1, 2606:4700:20::ac43:481c |
| NS | henry.ns.cloudflare.com, natasha.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at lynxdefense.com is "v=spf1 include:amazonses.com include:_spf.google.com ~all".
The DMARC text record at _dmarc.lynxdefense.com is "v=DMARC1;p=quarantine;rua=mailto:[email protected]".
IPv4 address 104.26.2.193 answers for lynxdefense.com at resolver 1.1.1.1:53.
IPv4 address 104.26.3.193 answers for lynxdefense.com at resolver 1.1.1.1:53.
IPv4 address 172.67.72.28 answers for lynxdefense.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:2c1 answers for lynxdefense.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:3c1 answers for lynxdefense.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:481c answers for lynxdefense.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
lynxdefense.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.2.193 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for lynxdefense.com is valid, with 77 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | lynxdefense.com |
| Valid from | 18 October 2026 |
| Valid until | 16 January 2027 |
| Days left | 77 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.lynxdefense.com, lynxdefense.com.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Alpine.js · JavaScript frameworks
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HSTS · Security
- HTTP/3 · Miscellaneous
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- PayPal · Payment processors
Alpine.js is filed under JavaScript frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
PayPal is filed under Payment processors.
On-page checks
The homepage returned HTTP 200 in 201 ms. The target title is 34 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 201 ms |
| Title length | 34 yes |
| Quoted title | "Lynx Defense | USA Made Range Bags" |
| Meta description | "Lynx Defense builds premium USA-made range bags, rifle cases and pistol bags, sewn in Selma, North Carolina, to organize and protect your gear." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1 |
| Canonical | https://lynxdefense.com/ |
| Language | en |
| Links | 266 |
| Images | 121 |
| Favicon | yes |
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 lynxdefense.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 | yes |
| 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 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 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 lynxdefense.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 lynxdefense.com?
lynxdefense.com is placed in Toronto, Canada.
When does lynxdefense.com expire?
lynxdefense.com expires on 12 July 2027 according to https://rdap.verisign.com/com/v1/domain/lynxdefense.com.
Who owns lynxdefense.com?
The registry did not return a person or a company for lynxdefense.com. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/lynxdefense.com at 2026-10-30T14:02:23Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:02:23Z
- TLS source tls:443 at 2026-10-30T14:02:23Z
- HTTP source https://lynxdefense.com/ at 2026-10-30T14:02:23Z
- Tech source wappalyzergo at 2026-10-30T14:02:23Z
- Geo source db-ip at 2026-10-30T14:02:23Z
- Safety source family DNS and local lists at 2026-10-30T14:02:23Z
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.