Sent with Response.AddHeader("Document-Policy", "force-load-at-top"); so we should always start at the top (should scroll shouldn't scroll)

Your User-Agent String

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)

Your User-Agent string is 103 characters.


Your browser sent the following headers:
Connection: Keep-Alive
Accept: */*
Accept-Encoding: gzip, br
Cookie: handl_url=https%3A%2F%2Flancamentosrj.com%2Ftag%2Fplantas-lancamento-rua-humaita-52%2Ffeed; HandLtestDomainNameServer=HandLtestDomainValueServer; handl_landing_page=https%3A%2F%2Flancamentosrj.com%2Ftag%2Fplantas-lancamento-rua-humaita-52%2Ffeed; handl_ip=3.144.242.149; handl_url_base=https%3A%2F%2Flancamentosrj.com%2Ftag%2Fplantas-lancamento-rua-humaita-52%2Ffeed; user_agent=Mozilla%2F5.0%20AppleWebKit%2F537.36%20%28KHTML%2C%20like%20Gecko%3B%20compatible%3B%20ClaudeBot%2F1.0%3B%20%2Bclaudebot%40anthropic.com%29
Host: webdbg.com
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
cf-ray: 8f5d26b7ef93056f-IAD
x-forwarded-for: 3.144.242.149
CF-IPCountry: US
X-Forwarded-Proto: https
cdn-loop: cloudflare; loops=1
CF-Visitor: {"scheme":"https"}
CF-Connecting-IP: 3.144.242.149
X-Original-URL: /uadisallowSTTF.aspx?refresh=plz

HTTPBrowserCapabilitiesASPNET's HTTPBrowserCapabilities object reports that, based on the User-Agent, your Browser has the following capabilities:
Type = Mozilla
Name = Mozilla
Version = 0.0
Major Version = 0
Minor Version = 0
Platform = Unknown
Is Beta = False
Is Crawler = False
Is AOL = False
Is Win16 = False
Is Win32 = False
Supports Frames = True
Supports Tables = True
Supports Cookies = True
Supports VBScript = False
Supports JavaScript = True
Supports Java Applets = False
Supports ActiveX Controls = False

Supports scroll-to-text-fragment? Try it (Disallow via DocPolicy) ; in a new window in a new noopener window - Purple highlight if target-text Selector is supported
chrome.exe --enable-blink-features=CSSTargetTextPseudoElement https://wpt.live/css/css-pseudo/parsing/target-text.html


more...

Server Date/Time:Sun, 22 Dec 2024 03:51:03 GMT

Your public IP address: 172.71.191.110
navigator.onLine:
navigator.connection:

getUserAgent(): ?
🔋 Battery Status: ?
prefers-color-scheme:
prefers-reduced-motion:
estimated Storage: (null)

Compression Streams

Explainer demo



(accent-color set to red)



CSS Color rebeccapurple Test
Emoji Flags: 🇺🇳 🇺🇸 🇹🇼
 
Image-Formats:  Fail SVG SVGZ Fail APNG Fail:TIFF Fail:jpeg-xr Fail:jpeg-xl Fail WebP  Fail WebPanim   Fail XBM Fail HEIC Fail AVIF


URL whitespace tests

embedded space embedded \t in scheme embedded \r\n embedded \t\r\n

Content-Encoding tests

Fail Zlib-wrapped DEFLATE Fail Brotli HTTPS Brotli on HTTP (should fail)

Cross-Origin-Resource-Policy

You should NOT see all of the images here.
Fail SameOrigin Fail SameSite webdbg.com SameOrigin webdbg.com SameSite

MIME

Willing to run JavaScript from text/html? Nope
Willing to run JavaScript from text/plain? Nope
Willing to run JavaScript from image/svg+xml? Nope
Willing to run JavaScript from image/gif? Nope

IFrame SrcDoc:
Picture:

# Broadcast Channel demo Broadcast a message to other instances:

# Page Visibility & Lifecycle Visibility Docs DiscussionPage Lifecycle API

# Navigation/ResourceTiming

Edge gpu  !!  el  webdbg  domain  _top  Refresh loop MITM?  f  f2  view-source  microsoft-edge edge ms-availablenetworks:
# Ancient UA String Stuff

About the User-Agent String

The User-Agent (or UA) string is sent along in the headers of every HTTP request so the server knows what type of browser is making the request. For a quick refresher on the User-Agent string, check out George Shephard's article in MSDN Magazine. Two MSDN articles describe User-Agent headers: Understanding User-Agent Strings, and Best Practices for detecting the Internet Explorer version.

Want Internet Explorer to simulate another version? 

IE8+ users: Check out the free User-Agent Picker add-on, which enables changing your UA string without restarting the browser.

Otherwise, run one of the following scripts and restart all browser instances to see the change:


The following script commands will generate a text file containing all UA-override registry settings.
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent" /s > Reg.txt
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent" /s >> Reg.txt
reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent" /s >> Reg.txt
reg query "HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent" /s >> Reg.txt
reg query "HKCU\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent" >> Reg.txt
reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent" /s >> Reg.txt
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent" >> Reg.txt


See this page using different modes: X-UA-Compatible: IE=7 X-UA-Compatible: IE=8 X-UA-Compatible: IE=9 HTML5 DTD No DocType Quirks Legacy DTD Quirks


©2003-2022 Eric Lawrence