Verifying active database connections and transactions...
Sync & Encryption Engine
Checking
Checking multi-service snapshot schema, revision management, and DEK/KEK encryption keys...
Email Delivery (SMTP)
Checking
Checking mailer transport readiness for signup verification, 2FA codes, and password resets...
Security & Rate Limiting
Checking
Verifying brute-force prevention, token security, and request throttling rules...
Clock Synchronization
Checking
Comparing local client clock with server time to detect time skew...
Technical Subsystem Diagnostics
Subsystem Component
Description
Status
Data Encryption Keys (keys)
Dedicated Data Encryption Key storage per account
Checking
Snapshots (snapshots)
Encrypted notes data storage table
Checking
Multi-Service Partitioning
Multi-service workspace isolation and independent sync
Checking
Rate Limiting Engine
Flood & brute-force protection table
Checking
Two-Factor Authentication (2FA)
Configurable login OTP & verification columns
Checking
Password Reset Workflow
Secure password change tokens & key re-wrapping
Checking
Sync History Permissions
Account-level sync history inspection permissions
Checking
Legacy v1 Compatibility Mirror
Real-time backward compatibility bridge for older extensions
Checking
Troubleshooting & FAQ
What should I do if a service is reported as Offline?
1. Check your local internet connection and ensure your browser or ad-blocker is not blocking API requests
to notefox.eu.
2. If the API or Database is temporarily unavailable, maintenance might be currently underway. Please wait a
few moments and click "Run Check Again".
3. If the problem persists, feel free to report it directly via our support channels.
Why does Clock Synchronization matter?
While Notefox Account v2 uses smart revision counters and conflict detection (HTTP 409) rather than relying
exclusively on device timestamps, keeping your device's clock synchronized with network time ensures that
your local edit history and logs reflect accurate times.