bill4time.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

40risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

3Low

2Info

Collected 18 hours ago6.1sfrom cache

Certificate Transparency12
DNS resolution22
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs123
Registration
DNS posture2
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis9

noteFound 14 addresses; enriching the first 12.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
note9 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.bill4time.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.bill4time.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.bill4time.com/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: bill4time.com
development.development.azure.b4t.bill4time.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: development.development.azure.b4t.bill4time.com
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.bill4time.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: bill4time.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: bill4time.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: bill4time.com

final https://www.bill4time.com/status 200time 1433msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
✓SPFends in -all
v=spf1 ip4:198.2.128.0/18 include:spf.protection.outlook.com include:spf.mandrillapp.com include:servers.mcsv.net include:_spf.google.com include:mail.zendesk.com include:sendgrid.net -all
!DMARCp=none
v=DMARC1; p=none
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
dee.ns.cloudflare.com kurt.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC20.5 years old
bill4time.com
✓Registration expiry201 days
2027-03-26
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
dee.ns.cloudflare.com kurt.ns.cloudflare.com

Address	Ports	Edge	Network
162.159.135.42 bill4time.com +3	80443205220532082208320862087+5	Cloudflare~	—
162.159.134.42 bill4time.com +3	80443205220532082208320862087+5	Cloudflare~	—
104.18.4.194 hello.bill4time.com +6	80443205220532082208320862087+5	Cloudflare~	—
104.18.5.194 hello.bill4time.com +5	80443205220532082208320862087+5	Cloudflare~	—
216.198.53.11 support.bill4time.com +2	80443205220532082208320862087+5	Cloudflare~	—
216.198.54.11 support.bill4time.com +2	80443205220532082208320862087+5	Cloudflare~	—
104.16.204.155 reviews.bill4time.com +1	80443205220532082208320862087+5	Cloudflare~	—
104.16.205.155 reviews.bill4time.com +1	80443205220532082208320862087+5	Cloudflare~	—
104.16.206.155 reviews.bill4time.com +1	80443205220532082208320862087+5	Cloudflare~	—
54.210.189.113 meetings.bill4time.com +3	80443	direct	—
3.217.23.207 meetings.bill4time.com +3	80443	direct	—
34.202.109.167 meetings.bill4time.com +2	80443	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

bill4time.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames