fedbidspeed.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 88 days left17 years old
75
fedbidspeed.com was registered on 9 Jul 2009 via GoDaddy.com, LLC and the registry expiry is 9 Jul 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fedbidspeed.com.
fedbidspeed.com publishes 2 nameservers. DNSSEC is not signed.
fedbidspeed.com has 1 IPv4 address (198.202.211.1). The geolocation database places 198.202.211.1 in San Francisco (South of Market), United States.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3, jQuery and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fedbidspeed.com in the checks that ran.
Domain · RDAP/WHOIS
fedbidspeed.com was registered on 9 Jul 2009 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fedbidspeed.com.
| Registered | since 9 Jul 2009 |
|---|---|
| Created | 9 July 2009 |
| Updated | 10 July 2026 |
| Expires | 9 July 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | pdns13.domaincontrol.com, pdns14.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/fedbidspeed.com |
fedbidspeed.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.
fedbidspeed.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.
fedbidspeed.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.
fedbidspeed.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 pdns13.domaincontrol.com is published for fedbidspeed.com in the registration record from https://rdap.verisign.com/com/v1/domain/fedbidspeed.com.
Nameserver pdns14.domaincontrol.com is published for fedbidspeed.com in the registration record from https://rdap.verisign.com/com/v1/domain/fedbidspeed.com.
DNS
fedbidspeed.com has 1 address record, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 198.202.211.1 |
|---|---|
| AAAA | — |
| NS | pdns13.domaincontrol.com, pdns14.domaincontrol.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.fedbidspeed.com is "v=DMARC1; p=reject; rua=mailto:[email protected]; pct=100;".
IPv4 address 198.202.211.1 answers for fedbidspeed.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
A random label under fedbidspeed.com also resolved, which means wildcard DNS is on.
Hosting and geo
fedbidspeed.com is placed in San Francisco (South of Market), United States by the local geolocation database (db-ip).
| Address | 198.202.211.1 |
|---|---|
| Country | United States |
| City | San Francisco (South of Market) |
| Source | db-ip |
SSL/TLS
The certificate for fedbidspeed.com is valid, with 88 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | fedbidspeed.com |
| Valid from | 30 October 2026 |
| Valid until | 28 January 2027 |
| Days left | 88 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fedbidspeed.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- jQuery · JavaScript libraries
- reCAPTCHA · Security
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
reCAPTCHA is filed under Security.
On-page checks
The homepage returned HTTP 200 in 196 ms. The target title is 42 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 196 ms |
| Title length | 42 yes |
| Quoted title | "Government Contracting Software | Bidspeed" |
| Meta description | "Find, evaluate, manage, and win government contracts with Bidspeed bid intelligence, capture workflows, marketplace reports, and GovReady support." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.bidspeed.com |
| Language | en |
| Links | 40 |
| Images | 16 |
| 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 fedbidspeed.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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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 San Francisco (South of Market).
- October 2026: geo country changed from empty to United States.
Questions
Is fedbidspeed.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 fedbidspeed.com?
fedbidspeed.com is placed in San Francisco (South of Market), United States.
When does fedbidspeed.com expire?
fedbidspeed.com expires on 9 July 2028 according to https://rdap.verisign.com/com/v1/domain/fedbidspeed.com.
Who owns fedbidspeed.com?
The registry did not return a person or a company for fedbidspeed.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/fedbidspeed.com at 2026-10-30T13:54:19Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:19Z
- TLS source tls:443 at 2026-10-30T13:54:19Z
- HTTP source https://fedbidspeed.com/ at 2026-10-30T13:54:19Z
- Tech source wappalyzergo at 2026-10-30T13:54:19Z
- Geo source db-ip at 2026-10-30T13:54:19Z
- Safety source family DNS and local lists at 2026-10-30T13:54:19Z
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.