DOMAIN DETAILS
roblox.com
okMonitoring history
Historical measurements from RelayPing probes, not a universal speed score.
Latest status
—
HTTP TTFB
—
Probe duration
—
Server-Timing
—
Loading monitoring history…
| Checked | Probe | Status | Method | TTFB | Probe duration | DNS | HTTP | Server-Timing |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
TTFB is measured from the listed probe and includes network time as well as server response time; it is not server processing time alone. Probe duration also includes connection setup. Server-Timing is shown only when one unambiguous duration is reported; that metric may describe one server phase, not total backend processing time. Measurements are timestamps in UTC.
DNS records
A
128.116.44.3
MX
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
NS
nspx2.roblox.net
nspx3.roblox.us
nspx4.roblox.co.uk
nspx1.roblox.com
TXT
"stripe-verification=d9a22bf4ff3fa1e244325bc511ff7832423ea2312809396df010807307102d73"
"hcp-domain-verification=4fe724b224f8665817b970b4cf9d41432119d0a8d7df547ab9d855405ed98df0"
"atlassian-domain-verification=TRNSmfCcYn22IqU1Q7y4OOU8BMHhZJru/qaj1RRP09wybG/vli6QA/GlDy5DiHlC"
"wrike-verification=Mzc5OTIyMTo2MjJkODg0ODc4ZGMzODM1OWUzZWY4NmNkZjRmN2JkNWQwMjQ3MjliYmQ5MjIyMGI2ZDBmY2E3NzJlNzdhMDE5"
"v=spf1 include:_spf.google.com ip4:50.232.73.154/32 ip4:64.124.125.0/26 ip4:208.185.173.0/24 ip4:208.185.116.0/25 ip4:64.125.149.0/24 ip4:8.42.96.0/24 ip4:216.200.230.0/24 ip4:8.42.100.0/24 include:_spf_20190122.roblox.com include:mail.zendesk.com -all"
"MS=ms35973480"
"rpaii9qhgu8k5o721gogq8h4b7"
"zendeskverification.roblox.com"
"_a9cffqfxf1959e73i8s27rbks5e14gg"
"_nglrwy78ihfxn8jlvnzokktgjrh4d36"
CAA
0 issue "globalsign.com"
0 issue "letsencrypt.org"
0 issue "pki.goog"
0 issue "sectigo.com"
0 iodef "mailto:[email protected]"
0 issue "amazon.com"
0 issue "digicert.com"
Network routing
128.116.44.3
Prefix:
128.116.44.0/24
Origin ASN:
AS22697
DNS records come from the configured resolver. Routing information
comes from
RIPEstat.
Routing data does not confirm that a service is online or establish
the physical location of a server.