Source
Checks, locations & failure confirmation — found from sitemap — updown.io
Checked for updown.io on 1 Nov 2026
- Page
- https://updown.io/features/dns-record-checks
- Checked
- 1 Nov 2026, 10:42 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:63667524a52bbeb1e24a7b3e606f604d947f3d5ecf2a3c58ec8266bdb1debc2e
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Dns record checks status Report an error
“Feature Requests DNS record checks UNDER REVIEW”
-
Dns check planned Report an error
“This is something we're thinking about but is not planned yet.”
-
Dns via tcp http checks Report an error
“through TCP/HTTP checks updown.io is already relying on DNS to reach the monitored target.”
-
Periodic checks Report an error
“The current monitoring seems to use resolvers with "hot" caches - hot means they are populated already by the periodic checks.”
-
Company origin Report an error
“Made with in Paris, France since 2012”
-
DPA available Report an error
“Terms of Service Privacy Policy DPA”
-
API available Report an error
“Twitter API About Blog Feature requests”
-
Documentation faq Report an error
“Documentation & FAQ Support System Status”
-
Check contains field Report an error
“this allows using the 'contains' field within the check portal to check for the required data.”
Scores citing this record
- The Agency Developer Checks, locations & failure confirmation
- The Customer Support Lead Checks, locations & failure confirmation
- The E-Commerce Operations Manager Checks, locations & failure confirmation
- The SaaS Platform Engineer Checks, locations & failure confirmation
- The Information Security Officer Checks, locations & failure confirmation
- The Skeptic Checks, locations & failure confirmation