battleswarmblog.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 75 days left17 years old
70
battleswarmblog.com was registered on 13 Oct 2009 via Bluehost Inc. and the registry expiry is 13 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/battleswarmblog.com.
battleswarmblog.com publishes 2 nameservers. DNSSEC is not signed.
battleswarmblog.com has 1 IPv4 address (50.87.249.26). The geolocation database places 50.87.249.26 in Phoenix, United States.
The TLS certificate from YR2 is valid and has 75 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, Bluehost, MySQL, PHP, WordPress and YouTube. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for battleswarmblog.com in the checks that ran.
Domain · RDAP/WHOIS
battleswarmblog.com was registered on 13 Oct 2009 via Bluehost Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/battleswarmblog.com.
| Registered | since 13 Oct 2009 |
|---|---|
| Created | 13 October 2009 |
| Updated | 27 September 2026 |
| Expires | 13 October 2027 |
| Registrar | Bluehost Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.bluehost.com, ns2.bluehost.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/battleswarmblog.com |
battleswarmblog.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 ns1.bluehost.com is published for battleswarmblog.com in the registration record from https://rdap.verisign.com/com/v1/domain/battleswarmblog.com.
Nameserver ns2.bluehost.com is published for battleswarmblog.com in the registration record from https://rdap.verisign.com/com/v1/domain/battleswarmblog.com.
DNS
battleswarmblog.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 50.87.249.26 |
|---|---|
| AAAA | — |
| NS | ns1.bluehost.com, ns2.bluehost.com |
| MX | battleswarmblog.com (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at battleswarmblog.com is "v=spf1 a mx ptr include:bluehost.com ?all".
IPv4 address 50.87.249.26 answers for battleswarmblog.com at resolver 1.1.1.1:53.
Mail exchanger battleswarmblog.com has preference 0.
Hosting and geo
battleswarmblog.com is placed in Phoenix, United States by the local geolocation database (db-ip).
| Address | 50.87.249.26 |
|---|---|
| Country | United States |
| City | Phoenix |
| Source | db-ip |
SSL/TLS
The certificate for battleswarmblog.com is valid, with 75 days left and 24 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | webdisk.battleswarmblog.com |
| Valid from | 16 October 2026 |
| Valid until | 14 January 2027 |
| Days left | 75 |
| SAN count | 24 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: austineatsout.com, austineatsout.lawrenceperson.com, autoconfig.austineatsout.com, autoconfig.battleswarmblog.com, autodiscover.austineatsout.com, autodiscover.battleswarmblog.com, battleswarmblog.com, battleswarmblog.lawrenceperson.com, cpanel.austineatsout.com, cpanel.battleswarmblog.com, cpcalendars.austineatsout.com, cpcalendars.battleswarmblog.com, cpcontacts.austineatsout.com, cpcontacts.battleswarmblog.com, mail.austineatsout.com, mail.battleswarmblog.com, webdisk.austineatsout.com, webdisk.battleswarmblog.com, webmail.austineatsout.com, webmail.battleswarmblog.com, www.austineatsout.com, www.austineatsout.lawrenceperson.com, www.battleswarmblog.com, www.battleswarmblog.lawrenceperson.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Apache HTTP Server · Web servers
- Bluehost · Hosting
- MySQL · Databases
- PHP · Programming languages
- WordPress · CMS, Blogs
- YouTube · Video players
Apache HTTP Server is filed under Web servers.
Bluehost is filed under Hosting.
MySQL is filed under Databases.
PHP is filed under Programming languages.
WordPress is filed under CMS, Blogs.
YouTube is filed under Video players.
On-page checks
The homepage returned HTTP 200 in 228 ms. The target title is 85 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 228 ms |
| Title length | 85 no |
| Quoted title | "Lawrence Person's BattleSwarm Blog | Attacking so fast they won't know what hit them…" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | — |
| Language | en-US |
| Links | 508 |
| Images | 12 |
| 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 battleswarmblog.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 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
- October 2026: geo city changed from empty to Phoenix.
- October 2026: geo country changed from empty to United States.
Questions
Is battleswarmblog.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 battleswarmblog.com?
battleswarmblog.com is placed in Phoenix, United States.
When does battleswarmblog.com expire?
battleswarmblog.com expires on 13 October 2027 according to https://rdap.verisign.com/com/v1/domain/battleswarmblog.com.
Who owns battleswarmblog.com?
The registry did not return a person or a company for battleswarmblog.com. RDAP often redacts the registrant. The registrar on file is Bluehost Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/battleswarmblog.com at 2026-10-30T13:46:18Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:46:18Z
- TLS source tls:443 at 2026-10-30T13:46:18Z
- HTTP source https://battleswarmblog.com/ at 2026-10-30T13:46:18Z
- Tech source wappalyzergo at 2026-10-30T13:46:18Z
- Geo source db-ip at 2026-10-30T13:46:18Z
- Safety source family DNS and local lists at 2026-10-30T13:46:18Z
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.