MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20250607120442|37",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 47,
"ns": 0,
"title": "Password Attacks",
"pageid": 45,
"logpage": 45,
"revid": 203,
"params": {},
"type": "create",
"action": "create",
"user": "Vegard",
"timestamp": "2025-06-15T05:37:13Z",
"comment": "Created page with \"== Password Attacks == Password attacks target authentication systems by attempting to gain access using valid or guessed credentials. These techniques play a central role in assessing the strength of user access controls, exposing weak password hygiene, misconfigurations, or lack of rate-limiting. Password-based authentication remains the most common form of access control, making it a recurring target for security assessments and enumeration strategies. === Goals ==...\""
},
{
"logid": 46,
"ns": 0,
"title": "Making HTTP Requests",
"pageid": 44,
"logpage": 44,
"revid": 202,
"params": {},
"type": "create",
"action": "create",
"user": "Vegard",
"timestamp": "2025-06-14T14:13:19Z",
"comment": "Created page with \"= Making HTTP Requests = == Introduction == HTTP requests are used to interact with web servers by requesting data, submitting forms, uploading files, or modifying resources. Understanding how each method works enables deeper interaction with web applications and can expose misconfigurations or unintended functionality. This page outlines how common HTTP methods are used in practice, with real-world examples suitable for exploration and testing. == GET == The GET me...\""
},
{
"logid": 45,
"ns": 0,
"title": "HTTP Protocols",
"pageid": 43,
"logpage": 43,
"revid": 197,
"params": {},
"type": "create",
"action": "create",
"user": "Vegard",
"timestamp": "2025-06-14T07:34:43Z",
"comment": "Created page with \"= HTTP Protocols = == Introduction == The Hypertext Transfer Protocol (HTTP) is the application-layer protocol used for communication between clients and servers on the web. It enables retrieval of resources such as HTML, JSON, or binary content by defining a standardized format for request and response messages. HTTP is stateless, meaning each request is independent unless explicitly managed using sessions, cookies, or tokens. == HTTP vs HTTPS == {| class=\"wikitabl...\""
},
{
"logid": 44,
"ns": 0,
"title": "DNS Resolution",
"pageid": 42,
"logpage": 42,
"revid": 194,
"params": {},
"type": "create",
"action": "create",
"user": "91.206.35.72",
"anon": "",
"timestamp": "2025-06-14T06:01:35Z",
"comment": "Created page with \"= DNS Resolution and record types (A Record, CNAME, MX, TXT) = == What is DNS? == DNS (Domain Name System) is the protocol responsible for resolving human-readable domain names (e.g., `example.com`) into machine-readable IP addresses (e.g., `93.184.216.34`). DNS acts as the naming infrastructure of the internet. == DNS Lookup Flow == The process of DNS resolution involves multiple steps from your device to authoritative servers. The system is designed hierarchically...\""
},
{
"logid": 43,
"ns": 0,
"title": "Stateless vs Stateful Firewalls",
"pageid": 41,
"logpage": 41,
"revid": 192,
"params": {},
"type": "create",
"action": "create",
"user": "Vegard",
"timestamp": "2025-06-13T14:32:27Z",
"comment": "Created page with \"= Stateless vs Stateful Firewalls = ; Introduction : Firewalls control how traffic enters or leaves a network. : They inspect packets and decide to allow or block them based on rules. : There are two core types of firewalls \u2014 '''stateless''' and '''stateful'''. : Knowing the difference is key to understanding how filtering works in both simple and complex environments. == Visual Summary == {| class=\"wikitable\" ! Firewall Type !! Tracks Sessions? !! Decision...\""
},
{
"logid": 42,
"ns": 0,
"title": "UDP Protocol",
"pageid": 40,
"logpage": 40,
"revid": 190,
"params": {},
"type": "create",
"action": "create",
"user": "Vegard",
"timestamp": "2025-06-13T13:41:48Z",
"comment": "Created page with \"= UDP Protocols = ; Purpose : UDP (User Datagram Protocol) is one of the two main transport protocols in the TCP/IP suite, alongside TCP. : It provides a simple, fast way to send data over networks without establishing a connection or tracking session state. : Understanding how UDP behaves helps identify when it is used, how it differs from TCP, and what it means when analyzing or generating traffic. == 1. Key Characteristics of UDP == UDP is a connectionless an...\""
},
{
"logid": 41,
"ns": 0,
"title": "TCP/IP Stack",
"pageid": 39,
"logpage": 39,
"revid": 187,
"params": {},
"type": "create",
"action": "create",
"user": "Vegard",
"timestamp": "2025-06-13T13:21:42Z",
"comment": "Created page with \"= TCP/IP Stack \u2014 For Learners Who Want Full Network Understanding = ; Purpose : The TCP/IP stack shows how data travels through a network, from a software application to the physical wire or Wi-Fi signal. : Understanding this structure is key to reading, analyzing, and shaping network traffic with intention. == 1. The Four TCP/IP Layers == Each layer plays a specific role. Together, they handle everything from human-readable data to raw electrical signals. {| cl...\""
},
{
"logid": 40,
"ns": 2,
"title": "User:NATREGTEGH2795786NEYHRTGE",
"pageid": 0,
"logpage": 0,
"params": {
"userid": 4
},
"type": "newusers",
"action": "create",
"user": "NATREGTEGH2795786NEYHRTGE",
"timestamp": "2025-06-13T11:21:34Z",
"comment": ""
},
{
"logid": 39,
"ns": 0,
"title": "OSI Model",
"pageid": 38,
"logpage": 38,
"revid": 181,
"params": {},
"type": "create",
"action": "create",
"user": "84.211.245.84",
"anon": "",
"timestamp": "2025-06-07T17:32:40Z",
"comment": "Created page with \"= OSI Model = The OSI model explains how data travels through a network. It splits this process into **seven layers**. Each layer has its own job \u2014 from moving raw bits to showing a website. Understanding the OSI model helps break down complex systems, and shows where tools, attacks, or failures happen. == OSI Layer Overview == The OSI model goes from Layer 1 (bottom) to Layer 7 (top). Each layer works with the ones above and below it. {| class=\"wikitable\" ! Layer...\""
},
{
"logid": 38,
"ns": 0,
"title": "Subnetting",
"pageid": 37,
"logpage": 37,
"revid": 175,
"params": {},
"type": "create",
"action": "create",
"user": "84.211.245.84",
"anon": "",
"timestamp": "2025-06-07T15:32:18Z",
"comment": "Created page with \"= Subnetting = Subnetting divides an IP network into smaller logical sections called subnets. This structuring improves efficiency, isolates traffic, and defines boundaries between systems and functions. A deep understanding of subnetting reveals how internal environments are organized, and how access and visibility are controlled across segments. == What Subnetting Enables == Subnetting assigns defined IP ranges to roles, departments, or zones. It introduces: * Pre...\""
}
]
}
}