Help
RSS
API
Feed
Maltego
Contact
Domain > usehtmldoc.surge.sh
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2024-11-19
138.197.235.123
(
ClassC
)
Port 80
HTTP/1.1 200 OKServer: SurgeSurge-Cache: HITSurge-Stamp: 576::1681058640064-076f6ef4306e04b488facd312e5fe55bAge: 2084722Date: Sat, 20 Jul 2024 18:43:42 GMTCache-Control: public, max-age0, must-revalid !doctype html>html classno-js lang>head> meta charsetutf-8> meta http-equivx-ua-compatible contentieedge> title>HTMLDoc - a standard for documenting HTML/title> meta namedescription content> meta nameviewport contentwidthdevice-width, initial-scale1, shrink-to-fitno> link relmanifest hrefsite.webmanifest> link relstylesheet hrefcss/normalize.css> link relstylesheet hrefcss/styles.css> link relapple-touch-icon sizes180x180 href/assets/apple-touch-icon.png> link relicon typeimage/png sizes32x32 href/assets/favicon-32x32.png> link relicon typeimage/png sizes16x16 href/assets/favicon-16x16.png> link relmanifest href/assets/manifest.json> link relmask-icon href/assets/safari-pinned-tab.svg color#5bbad5> meta nametheme-color content#ffffff>/head>body> header> h1>@use HTMLDocspan> - a standard for documenting HTML/span>/h1> /header> article> h2>Introduction/h2> p>Wouldnt it be nice if there was a consistent markup standard for code comments in HTML?/p> p>Some scenarios where rigorous code comments could be useful:/p> ul> li>Non-intuitive or hackish usage of HTML tags, elements and attributes, where explanation would help/li> li>Other uses of non-visual elements/li> li>Accessibility features/li> li>Search engine optimisation (SEO) features/li> /ul> p>Introducing HTMLDoc - a simple markup language for augmenting HTML tags and attributes with descriptive comments, which can be used to generate structured documentation./p> h2>The Standard/h2> h3>Tags/h3> p>Tags are marked with @tag tag, followed by a space, then a description of the tag./p> p>Example:/p> code> pre> <!-- @tag input input for amount paid --> <input typenumber idamountPaid /> /pre> /code> h3>Attributes/h3> p>Attributes are marked up with the @attribute tag, followed by a space, then a description of the attribute./p> p>Example:/p> code> pre> <!-- @tag input @attribute step Allows en
Port 443
HTTP/1.1 200 OKServer: SurgeSurge-Cache: HITSurge-Stamp: 588::1681058640064-076f6ef4306e04b488facd312e5fe55bAge: 2084722Date: Sat, 20 Jul 2024 18:43:42 GMTCache-Control: public, max-age0, must-revalid !doctype html>html classno-js lang>head> meta charsetutf-8> meta http-equivx-ua-compatible contentieedge> title>HTMLDoc - a standard for documenting HTML/title> meta namedescription content> meta nameviewport contentwidthdevice-width, initial-scale1, shrink-to-fitno> link relmanifest hrefsite.webmanifest> link relstylesheet hrefcss/normalize.css> link relstylesheet hrefcss/styles.css> link relapple-touch-icon sizes180x180 href/assets/apple-touch-icon.png> link relicon typeimage/png sizes32x32 href/assets/favicon-32x32.png> link relicon typeimage/png sizes16x16 href/assets/favicon-16x16.png> link relmanifest href/assets/manifest.json> link relmask-icon href/assets/safari-pinned-tab.svg color#5bbad5> meta nametheme-color content#ffffff>/head>body> header> h1>@use HTMLDocspan> - a standard for documenting HTML/span>/h1> /header> article> h2>Introduction/h2> p>Wouldnt it be nice if there was a consistent markup standard for code comments in HTML?/p> p>Some scenarios where rigorous code comments could be useful:/p> ul> li>Non-intuitive or hackish usage of HTML tags, elements and attributes, where explanation would help/li> li>Other uses of non-visual elements/li> li>Accessibility features/li> li>Search engine optimisation (SEO) features/li> /ul> p>Introducing HTMLDoc - a simple markup language for augmenting HTML tags and attributes with descriptive comments, which can be used to generate structured documentation./p> h2>The Standard/h2> h3>Tags/h3> p>Tags are marked with @tag tag, followed by a space, then a description of the tag./p> p>Example:/p> code> pre> <!-- @tag input input for amount paid --> <input typenumber idamountPaid /> /pre> /code> h3>Attributes/h3> p>Attributes are marked up with the @attribute tag, followed by a space, then a description of the attribute./p> p>Example:/p> code> pre> <!-- @tag input @attribute step Allows en
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]