Two invisible settings sit under a surprising share of bank errors: a clock that has drifted into the wrong day, and a DNS cache confidently sending you to a dead address. Both fix in minutes.
These two causes share a tell: they break the bank while leaving most of the internet apparently fine, because banking is where strictness lives — certificates checked to the day, addresses that must be exactly right. If your error mentions privacy, certificates or dates, suspect the clock. If it says the site cannot be reached while a friend opens it easily, suspect DNS. Neither fix touches the bank, your account, or your other settings.
👆 The flush itself is one line. What it clears — months of stale address records — is what was breaking the bank.
Secure websites prove their identity with certificates that are valid only between two dates. If your computer's clock sits outside that window — after a dead CMOS battery, a botched dual-boot, or a manual change — your browser concludes the bank's genuine certificate is fake and blocks the page, often with a 'Your connection is not private' or date-invalid warning. The bank is fine; your clock is lying.
If the clock keeps drifting wrong after every shutdown on an old desktop, the small coin battery on the motherboard is dying — a cheap part, and the permanent fix.
Before visiting any website, your computer looks up its address using DNS, and caches the answers. When a bank moves servers or your provider's records go stale, the cache can keep sending you to a dead or wrong address — the site 'can't be reached' while it is perfectly up for everyone else. The one-line cure is shown in the panel:
ipconfig /flushdns and press Enter — you should see the success line from the panelRestart the router once as well — it keeps its own DNS cache, and thirty seconds off clears it.
If the flush works only for a day, or the bank fails while other sites crawl, your provider's DNS itself may be the weak link. Switching the computer's DNS to a well-run public resolver (common choices are 1.1.1.1 and 8.8.8.8) is a legitimate, reversible test — done in the network adapter's properties or the router, it takes minutes and can be undone the same way.
Two honest cautions. First, a DNS change fixes lookups, nothing else — it will not cure cookies, VPN blocks or a bank outage, and the split test tells you whether lookups are even your problem. Second, on an office computer, leave DNS exactly as IT set it: internal systems depend on it, and the office failure belongs to the office network anyway.
On Android, Private DNS set to a strict custom hostname can break banking apps when that resolver misbehaves — set it to Automatic as a test. On any phone, the deeper point is simpler: if the app fails on home Wi-Fi but works on mobile data, your phone is innocent and your router or provider is the story — the fixes above belong to them, not to the phone.
Watch the video for the wider access fix — and keep this page for the day a certificate warning or a phantom outage points at your clock or cache.
▶️ Watch Full VideoLook closer — the hour can be right while the date, month or time zone is off, and certificates care about all of them. A dual-boot with Linux, a recently changed CMOS battery, or a manually set date that was never corrected are the usual stories. Setting time and zone to automatic and pressing Sync now removes all doubt in one visit.
Completely. It only empties a cache of address lookups; Windows rebuilds it automatically as you browse. Nothing about your accounts, files or settings changes. It is one of the safest commands in this entire set — which is why it appears early in almost every network fix order.
You can — public resolvers like 1.1.1.1 and 8.8.8.8 are run by large, reputable operators and many people use them permanently. Just remember the change exists: if a work-from-home or streaming service later behaves oddly, DNS is a suspect. And on an office-managed machine, revert it — that network was not yours to reconfigure.