drf.com — domain analysis
AdvantageBizMarketing Editorial
October 5, 2026
·
0 min read
drf.com describes itself as "Get the latest horse racing entries, results, and past performances from Daily Racing Form. Place smarter horse bets with expert analysis, stats, and live updates.". It is built on Next.js, registered in 1995, served from Montreal, Canada. It has a valid HTTPS certificate, 2 of 6 common security headers.
What is drf.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- breeders ×4
- racing ×3
- loading ×3
- form ×2
Does drf.com publish the usual trust pages?
None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does drf.com compare with other domains analysed here?
Measured against the 74 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 57% of them (median 486ms) |
|---|---|
| Security headers | More than 67% of them |
| Domain age | Older than 91% of them |
Related domains in this index
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was drf.com registered?
drf.com was registered on 13 June 1995, which makes it about 31 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is GoDaddy.com, LLC.
Registration runs until 12 June 2027.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 13 June 1995 |
|---|---|
| Expires | 12 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Registry status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
Where is drf.com hosted?
The first address resolves to infrastructure in Montreal, Canada.
The network is operated by Fastly, Inc. (AS54113 Fastly, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is drf.com running on?
drf.com exposes 2 identifiable technologies: Next.js, X-Powered-By: Next.js.
The build output indicates a server-rendered JavaScript framework, which means the HTML served to crawlers is generated ahead of time rather than assembled in the browser.
- Next.js
- X-Powered-By: Next.js
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 310ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML alone is 877KB before images, stylesheets or scripts are counted, which is heavy for a document that browsers must parse before anything renders.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 898,109 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 56 characters, inside the range that displays without truncation.
A meta description of 163 characters is present.
No H1 heading was found, so the page offers no single top-level statement of what it is.
All 3 images on the homepage have alt attributes.
| Title | Horse Racing Entries, Results & Bets | Daily Racing Form (56 chars) |
|---|---|
| Meta description | Get the latest horse racing entries, results, and past performances from Daily Racing Form. Place smarter horse bets with expert analysis, stats, and live updates. (163 chars) |
| H1 | — none — (0 on the page) |
| Canonical | https://www.drf.com/home |
| Open Graph title | Horse Racing Entries, Results & Bets | Daily Racing Form |
| Headings / images | 0 H2s, 3 images (0 without alt text) |
Is drf.com served over a valid certificate?
The HTTPS certificate is issued by DigiCert Inc and is
valid until 2027-04-14, which is 191 days from the date of this check. It covers
2 hostnames.
- *.drf.com
- drf.com
The certificate has 191 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
2 of 6 are set (Content Security Policy, Permissions-Policy). Absent: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | yes | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.google-analytics.com |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | yes | browsing-topics=* |
How is DNS configured for drf.com?
| IP addresses | 151.101.2.49, 151.101.130.49, 151.101.194.49, 151.101.66.49 |
|---|---|
| Reverse DNS | 151.101.2.49, 151.101.130.49 |
| Name servers | ns-695.awsdns-22.net, ns-1107.awsdns-10.org, ns-1807.awsdns-33.co.uk, ns-402.awsdns-50.com |
| Mail (MX) | mx-01-us-west-2.prod.hydra.sophos.com (pri 10), mx-02-us-west-2.prod.hydra.sophos.com (pri 20) |
| SPF | v=spf1 mx ip4:67.23.51.216 a:mail.drf.com a:watchmail.dailyracingform.com a:mta.dailyracingform.com include:_spf_uswest2.prod.hydra.sophos.com include:spf.protection.outlook.com include:spf.zoho.com include:transmail.net include:spf-us.emailsignatures365.com ip4:66.193.103.0/24 -all |
| TXT records | 17 |
drf.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 2 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 151.101.2.49, 151.101.130.49, which usually names the hosting provider.
Who runs DNS and mail for drf.com?
DNS is operated by Amazon Route 53 rather than self-hosted name servers.
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about drf.com?
2 email addresses appear in the homepage markup, where address-harvesting crawlers will find them.
The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.
Can drf.com be spoofed in email?
DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
- Organization
- Person
- PostalAddress
- ContactPoint
The homepage publishes 4 structured data types: Organization, Person, PostalAddress, ContactPoint.
What does drf.com load from third parties?
The homepage pulls resources from 4 third-party hosts (a-us.storyblok.com, drf-ops.s3.us-east-1.amazonaws.com, googletagmanager.com, nexus.linkengine.io). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
The page links or refers to X/Twitter, Facebook, Instagram, YouTube.
Does drf.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both drf.com and www.drf.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can drf.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does drf.com run?
No analytics or advertising trackers were detected on the homepage of drf.com, which is unusual for a commercial site.
How does drf.com look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
How are images, fonts and scripts handled?
3 images on the homepage, 1 of them lazy-loaded (33%).
Modern image formats are in use (9 WebP/AVIF references).
The page pulls 4 external stylesheets and 17 external scripts, with 16 carrying defer or async.
Responses carry Varnish/Fastly edge and edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is drf.com accessible and current?
The page uses 2 landmark elements and 92 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index drf.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 18 internal and 1 external link across 1 outside host.
Visible text is only 0.1% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is drf.com delivered?
The HTML is served with Cache-Control: private, no-store, max-age=0, must-revalidate.
Frequently asked questions
Does drf.com set the usual HTTP security headers?
It sets 2 of 6. The ones not present are: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy.
Does drf.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
What is drf.com built with?
The homepage exposes these fingerprints: Next.js, X-Powered-By: Next.js. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own drf.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →
AdvantageBizMarketing Editorial
SEO strategist and content editor at AdvantageBizMarketing.