runninglevel.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 81 days left6 years old
85
runninglevel.com was registered on 30 Apr 2020 via GoDaddy.com, LLC and the registry expiry is 30 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/runninglevel.com.
runninglevel.com publishes 4 nameservers. DNSSEC is not signed.
runninglevel.com has 1 IPv4 address (173.255.226.130) and 1 IPv6 address (2600:3c03::2000:7eff:fe86:def8). The geolocation database places 173.255.226.130 in Hanover (Cedar Knolls), United States.
The TLS certificate from YE1 is valid and has 81 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, Google Analytics and HSTS. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for runninglevel.com in the checks that ran.
Domain · RDAP/WHOIS
runninglevel.com was registered on 30 Apr 2020 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/runninglevel.com.
| Registered | since 30 Apr 2020 |
|---|---|
| Created | 30 April 2020 |
| Updated | 1 May 2026 |
| Expires | 30 April 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1196.awsdns-21.org, ns-1750.awsdns-26.co.uk, ns-261.awsdns-32.com, ns-848.awsdns-42.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/runninglevel.com |
runninglevel.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.
runninglevel.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.
runninglevel.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.
runninglevel.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 ns-1196.awsdns-21.org is published for runninglevel.com in the registration record from https://rdap.verisign.com/com/v1/domain/runninglevel.com.
Nameserver ns-1750.awsdns-26.co.uk is published for runninglevel.com in the registration record from https://rdap.verisign.com/com/v1/domain/runninglevel.com.
Nameserver ns-261.awsdns-32.com is published for runninglevel.com in the registration record from https://rdap.verisign.com/com/v1/domain/runninglevel.com.
Nameserver ns-848.awsdns-42.net is published for runninglevel.com in the registration record from https://rdap.verisign.com/com/v1/domain/runninglevel.com.
DNS
runninglevel.com has 2 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 173.255.226.130 |
|---|---|
| AAAA | 2600:3c03::2000:7eff:fe86:def8 |
| NS | ns-1196.awsdns-21.org, ns-1750.awsdns-26.co.uk, ns-261.awsdns-32.com, ns-848.awsdns-42.net |
| MX | — |
| SPF | present |
| DMARC | absent |
| CAA | iodef mailto:[email protected], issue letsencrypt.org |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at runninglevel.com is "v=spf1 -all".
IPv4 address 173.255.226.130 answers for runninglevel.com at resolver 1.1.1.1:53.
IPv6 address 2600:3c03::2000:7eff:fe86:def8 answers for runninglevel.com at resolver 1.1.1.1:53.
Hosting and geo
runninglevel.com is placed in Hanover (Cedar Knolls), United States by the local geolocation database (db-ip).
| Address | 173.255.226.130 |
|---|---|
| Country | United States |
| City | Hanover (Cedar Knolls) |
| Source | db-ip |
SSL/TLS
The certificate for runninglevel.com is valid, with 81 days left and 3 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | runninglevel.com |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 81 |
| SAN count | 3 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: beta.runninglevel.com, runninglevel.com, www.runninglevel.com.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Apache HTTP Server · Web servers
- Google Analytics · Analytics
- HSTS · Security
Apache HTTP Server is filed under Web servers.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
On-page checks
The homepage returned HTTP 200 in 41 ms. The target title is 47 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 41 ms |
| Title length | 47 yes |
| Quoted title | "Running Level - Calculator, Times and Standards" |
| Meta description | "Calculate your running level for distances including 5k, 10k, 1 Mile, Half Marathon and Marathon. Compare your performance with runners of the same age and sex." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | https://runninglevel.com/ |
| Language | en |
| Links | 36 |
| Images | 6 |
| 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 runninglevel.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 | 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 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.
Change history
- October 2026: dns a changed from 172.239.123.192 to 173.255.226.130.
- October 2026: dns aaaa changed from 2600:3c13::2000:e9ff:fe45:8f69 to 2600:3c03::2000:7eff:fe86:def8.
- October 2026: geo city changed from empty to Hanover (Cedar Knolls).
- October 2026: geo country changed from empty to United States.
Questions
Is runninglevel.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 runninglevel.com?
runninglevel.com is placed in Hanover (Cedar Knolls), United States.
When does runninglevel.com expire?
runninglevel.com expires on 30 April 2027 according to https://rdap.verisign.com/com/v1/domain/runninglevel.com.
Who owns runninglevel.com?
The registry did not return a person or a company for runninglevel.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/runninglevel.com at 2026-10-30T14:12:28Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:12:28Z
- TLS source tls:443 at 2026-10-30T14:12:28Z
- HTTP source https://runninglevel.com/ at 2026-10-30T14:12:28Z
- Tech source wappalyzergo at 2026-10-30T14:12:28Z
- Geo source db-ip at 2026-10-30T14:12:28Z
- Safety source family DNS and local lists at 2026-10-30T14:12:28Z
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.