bodsforthemods.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 404Family DNS blockedSSL: 71 days left22 years old
40
bodsforthemods.com was registered on 9 Aug 2004 via GoDaddy.com, LLC and the registry expiry is 6 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bodsforthemods.com.
bodsforthemods.com publishes 2 nameservers. DNSSEC is not signed.
bodsforthemods.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 71 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
bodsforthemods.com was registered on 9 Aug 2004 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bodsforthemods.com.
| Registered | since 9 Aug 2004 |
|---|---|
| Created | 9 August 2004 |
| Updated | 23 September 2026 |
| Expires | 6 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | edna.ns.cloudflare.com, noah.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bodsforthemods.com |
bodsforthemods.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.
bodsforthemods.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.
bodsforthemods.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.
bodsforthemods.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 edna.ns.cloudflare.com is published for bodsforthemods.com in the registration record from https://rdap.verisign.com/com/v1/domain/bodsforthemods.com.
Nameserver noah.ns.cloudflare.com is published for bodsforthemods.com in the registration record from https://rdap.verisign.com/com/v1/domain/bodsforthemods.com.
DNS
bodsforthemods.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | edna.ns.cloudflare.com, noah.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.bodsforthemods.com is "v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:[email protected];".
IPv4 address 188.114.96.4 answers for bodsforthemods.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for bodsforthemods.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for bodsforthemods.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for bodsforthemods.com at resolver 1.1.1.1:53.
Hosting and geo
bodsforthemods.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for bodsforthemods.com is valid, with 71 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bodsforthemods.com |
| Valid from | 12 October 2026 |
| Valid until | 10 January 2027 |
| Days left | 71 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bodsforthemods.com, bodsforthemods.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 404 in 72 ms. The target title is 9 characters and the page has 0 H1 headings.
| Status | 404 |
|---|---|
| TTFB | 72 ms |
| Title length | 9 yes |
| Quoted title | "Not Found" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en-us |
| 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.
Security
Family DNS for bodsforthemods.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for bodsforthemods.com. That resolver covers adult and malware names.
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 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 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 0 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 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
- October 2026: http status_class changed from empty to 4xx.
- October 2026: tech added Cloudflare.
- October 2026: tech added HTTP/3.
Questions
Is bodsforthemods.com safe?
Cloudflare family DNS returned a block for bodsforthemods.com. That resolver covers adult and malware names.
Who hosts bodsforthemods.com?
bodsforthemods.com is placed in Toronto, Canada.
When does bodsforthemods.com expire?
bodsforthemods.com expires on 6 June 2027 according to https://rdap.verisign.com/com/v1/domain/bodsforthemods.com.
Who owns bodsforthemods.com?
The registry did not return a person or a company for bodsforthemods.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/bodsforthemods.com at 2026-10-30T13:47:29Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:29Z
- TLS source tls:443 at 2026-10-30T13:47:29Z
- HTTP source https://bodsforthemods.com/ at 2026-10-30T13:47:29Z
- Tech source wappalyzergo at 2026-10-30T13:47:29Z
- Geo source db-ip at 2026-10-30T13:47:29Z
- Safety source family DNS and local lists at 2026-10-30T13:47:29Z
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.