loadout.tf
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 46 days left13 years oldTranco #490863
75
loadout.tf was registered on 21 Sep 2013 via OVH and the registry expiry is 21 Sep 2027. WHOIS data came from RDAP at https://rdap.nic.tf/domain/loadout.tf.
loadout.tf publishes 2 nameservers. DNSSEC is not signed.
loadout.tf has 1 IPv4 address (5.196.64.130) and 1 IPv6 address (2001:41d0:a:6082::). The geolocation database places 5.196.64.130 in Roubaix, France.
The TLS certificate from YR2 is valid and has 46 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Nginx and Ubuntu. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for loadout.tf in the checks that ran.
Domain · RDAP/WHOIS
loadout.tf was registered on 21 Sep 2013 via OVH. The registry returned 2 status values and 2 nameservers from https://rdap.nic.tf/domain/loadout.tf.
| Registered | since 21 Sep 2013 |
|---|---|
| Created | 21 September 2013 |
| Updated | 21 September 2026 |
| Expires | 21 September 2027 |
| Registrar | OVH |
| Status | active, auto renew period |
| Nameservers | ns335295.ip-5-196-64.eu, sdns2.ovh.net |
| DNSSEC | unknown |
| Source | https://rdap.nic.tf/domain/loadout.tf |
Nameserver ns335295.ip-5-196-64.eu is published for loadout.tf in the registration record from https://rdap.nic.tf/domain/loadout.tf.
Nameserver sdns2.ovh.net is published for loadout.tf in the registration record from https://rdap.nic.tf/domain/loadout.tf.
DNS
loadout.tf has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 5.196.64.130 |
|---|---|
| AAAA | 2001:41d0:a:6082:: |
| NS | ns335295.ip-5-196-64.eu, sdns2.ovh.net |
| MX | mail.loadout.tf (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at loadout.tf is "v=spf1 ip4:5.196.64.130 ip6:2001:41d0:a:6082:: -all".
The DMARC text record at _dmarc.loadout.tf is "v=DMARC1; p=quarantine; rua=mailto:[email protected]; fo=1;".
IPv4 address 5.196.64.130 answers for loadout.tf at resolver 1.1.1.1:53.
IPv6 address 2001:41d0:a:6082:: answers for loadout.tf at resolver 1.1.1.1:53.
Mail exchanger mail.loadout.tf has preference 10.
Hosting and geo
loadout.tf is placed in Roubaix, France by the local geolocation database (db-ip).
| Address | 5.196.64.130 |
|---|---|
| Country | France |
| City | Roubaix |
| Source | db-ip |
SSL/TLS
The certificate for loadout.tf is valid, with 46 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | loadout.tf |
| Valid from | 18 September 2026 |
| Valid until | 17 December 2026 |
| Days left | 46 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: loadout.tf.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Nginx · Web servers, Reverse proxies
- Ubuntu · Operating systems
Nginx is filed under Web servers, Reverse proxies.
Ubuntu is filed under Operating systems.
On-page checks
The homepage returned HTTP 200 in 15 ms. The target title is 30 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 15 ms |
| Title length | 30 yes |
| Quoted title | "Loadout.tf - Test TF2 loadouts" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| 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.
Security
Family DNS for loadout.tf 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 10 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 Roubaix.
- October 2026: geo country changed from empty to France.
Questions
Is loadout.tf 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 loadout.tf?
loadout.tf is placed in Roubaix, France.
When does loadout.tf expire?
loadout.tf expires on 21 September 2027 according to https://rdap.nic.tf/domain/loadout.tf.
Who owns loadout.tf?
The registry did not return a person or a company for loadout.tf. RDAP often redacts the registrant. The registrar on file is OVH.
Sources
- RDAP source https://rdap.nic.tf/domain/loadout.tf at 2026-10-30T15:14:40Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:14:40Z
- TLS source tls:443 at 2026-10-30T15:14:40Z
- HTTP source https://loadout.tf/ at 2026-10-30T15:14:40Z
- Tech source wappalyzergo at 2026-10-30T15:14:40Z
- Geo source db-ip at 2026-10-30T15:14:40Z
- Safety source family DNS and local lists at 2026-10-30T15:14:40Z
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.