logoswar.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
logoswar.com was registered on 9 Sep 2019 via FBS Inc. and the registry expiry is 9 Sep 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/logoswar.com.
logoswar.com publishes 2 nameservers. DNSSEC is not signed.
logoswar.com has 2 IPv4 addresses (104.21.66.207, 172.67.207.66) and 2 IPv6 addresses (2606:4700:3032::ac43:cf42, 2606:4700:3034::6815:42cf). The geolocation database places 104.21.66.207 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 55 days left (TLS 1.3).
Tech detection named Cloudflare, Google Analytics and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for logoswar.com in the checks that ran.
logoswar.com was registered on 9 Sep 2019 via FBS Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/logoswar.com.
| Registered | since 9 Sep 2019 |
|---|---|
| Created | 9 September 2019 |
| Updated | 9 December 2019 |
| Expires | 9 September 2028 |
| Registrar | FBS Inc. |
| Status | active |
| Nameservers | aida.ns.cloudflare.com, jason.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/logoswar.com |
Nameserver aida.ns.cloudflare.com is published for logoswar.com in the registration record from https://rdap.verisign.com/com/v1/domain/logoswar.com.
Nameserver jason.ns.cloudflare.com is published for logoswar.com in the registration record from https://rdap.verisign.com/com/v1/domain/logoswar.com.
logoswar.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.66.207, 172.67.207.66 |
|---|---|
| AAAA | 2606:4700:3032::ac43:cf42, 2606:4700:3034::6815:42cf |
| NS | aida.ns.cloudflare.com, jason.ns.cloudflare.com |
| MX | route2.mx.cloudflare.net (8), route1.mx.cloudflare.net (44), route3.mx.cloudflare.net (83) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at logoswar.com is "v=spf1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.logoswar.com is "v=DMARC1; p=none;".
IPv4 address 104.21.66.207 answers for logoswar.com at resolver 1.1.1.1:53.
IPv4 address 172.67.207.66 answers for logoswar.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:cf42 answers for logoswar.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::6815:42cf answers for logoswar.com at resolver 1.1.1.1:53.
Mail exchanger route2.mx.cloudflare.net has preference 8.
Mail exchanger route1.mx.cloudflare.net has preference 44.
Mail exchanger route3.mx.cloudflare.net has preference 83.
logoswar.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.66.207 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for logoswar.com is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | logoswar.com |
| Valid from | 28 September 2026 |
| Valid until | 27 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.logoswar.com, logoswar.com.
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 503 in 48 ms. The target title is 35 characters and the page has 1 H1 heading.
| Status | 503 |
|---|---|
| TTFB | 48 ms |
| Title length | 35 yes |
| Quoted title | "www.logoswar.com | Just a moment..." |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex, nofollow |
| Canonical | — |
| Language | — |
| Links | 0 |
| 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.
Family DNS for logoswar.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.
Availability 10 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 5 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
logoswar.com is placed in Toronto, Canada.
logoswar.com expires on 9 September 2028 according to https://rdap.verisign.com/com/v1/domain/logoswar.com.
The registry did not return a person or a company for logoswar.com. RDAP often redacts the registrant. The registrar on file is FBS 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.