signpuddle.net Signpuddle.net

   
SignPuddle Network

Domain Summary

What IP addresses does Signpuddle.net resolve to?

• Signpuddle.net resolves to the IP addresses 104.168.144.56.

Where are Signpuddle.net servers located in?

• Signpuddle.net has servers located in United States.

signpuddle.net Profile

Title:SignPuddle Network Description:> swserver, v1.3.0 May 2nd, 2016 ## About SignWriting is the international script for writing the sign languages of the world. The SignWriting Server provides online resources for SignWriting applications and users. The server accepts HTTP requests and responds with SVG or JSON data. The SignWriting Server is built with the PHP SLIM Framework v2.6. The primary site is available on the Center for Sutton Movement Writing server. * http://signpuddle.net A mirror site is available on Wikimedia Labs. * https://swserver.wmflabs.org ## Features ### SVG images The SignWriting server creates SVG images for individual symbols using symbol keys and completed 2-dimensional signs using Formal SignWriting. Styling strings are supported, offering coloring and sizing customizations. ### Query string transformation to regular expressions Query strings are a concise representation of a much larger and detailed set of regular expressions. Each query string is transformed into one or more regular expressions that can be used to search a text of Formal SignWriting. Additionally, Formal SignWriting strings can be converted into several types of query strings, each of which can be transformed into regular expressions. ### Countries of the world The countries of the world are described with SVG shapes and flag images. Listings of languages and puddle collections are available for each country. ### Puddle collections and sign entries All of the SignPuddle Online data is available as SQLite 3 databases. These databases can be downloaded individually. The various puddle collections can be listed, limited by sign language or individual code. For each sign language, a default public dictionary has been selected so that ISO 639-3 codes can be used rather than a puddle code. With a puddle query, individual entries can be access with sign language directly. With a puddle search, individual entries can be access with spoken language. Additional search options are available for listings of individual signs and terms. Additionally, entries can be retrieved by the dates created or updated. ## Installation Copy the SignWriting Server files to the root web server directory or to a sub-directory. ### Requirements Any server that supports PHP and SQLite 3 will be able to run the SignWriting Server. ### Databases The main database is available from the [SignWriting Server Data project](https://github.com/Slevinski/swserver_data/) with only the symbol information. * install as data/swserver.db The SignPuddle Online databases are available on [SignBank](http://signbank.org/swserver_data/). The main database is available as [swserver.db](http://signbank.org/swserver_data/swserver.db). * install as data/swserver.db The individual databases are available in the [puddle subdirectory](http://signbank.org/swserver_data/puddle/). * install in data/puddle/ A shell script is available to download the main database. * execute data/refresh_main.sh A shell script is available to mirror all of the available puddles on SignBank with a single command. * execute data/refresh_dbs.sh ### Shell Script to Start Server If a web server is not already running, the start server shell script can be used to start the built-in PHP web server. * ./start_server.sh ## Automation Tools The SignWriting Server project documents are created with command-line tools. ### API Blueprint The SignWriting Server API is documented using API Blueprint. This specification offers powerful tooling such as automatic HTML document generation and mock servers. https://apiblueprint.org/ The API Blueprint for the Guide is embedded in the main index.php file. The API Blueprint for the Example document is created using 'curl' with 'curl-trace-parser'. ### JSON Data Examples The SignWriting Server includes example API calls encoded as JSON data. These examples are used to create the API Blueprint for the Example document and the JavaScript function calls for the Run HTML page. ### Requirements * Shell scripts with more, grep, cat, and cut * [jq](https://stedolan.github.io/jq/) - like '''sed''' for JSON data * [curl](http://curl.haxx.se/) - communicate with a server from the command line * [curl-trace-parser](https://github.com/apiaryio/curl-trace-parser) - reformat curl output * [hiro](https://github.com/peterhellberg/hiro) - create HTML documents from API Blueprints * [iglo](https://github.com/subosito/iglo) - create large HTML documents when hiro fails ### Tools * ./buils.sh - Creates the Index and Guide documents. Creates shell script and JavaScript function calls from JSON example data. * ./run.sh - Executes the Example shell script and collates the results into the Example document. * ./release.sh - Calls the build.sh script and then the run.sh script. * ./example.sh - Creates the example html document when hiro fails for large files. ## Filesystem ### Directories * / - root directory with HTML documentation and PHP server * /Slim - directory for the Slim Framework v2.6 code * /include - directory for other PHP files and function libraries * /data - directory for the SignWriting Server databases * /tools - directory for automation and document creation * /tools/input - directory of tool inputs, such as template.html * /tools/output - directory of processed output * /tools/log - directory of example request/response API calls ### Source Files * README.md - read me file in markdown * index.php - main file for handling requests, with embedded API Blueprint * Example.json - example api calls in JSON data format * Run.html - html page uses example api calls to access a server ### Derived Files * index.html - Created from README.md * tools/output/Guide.md - Created from index.php * Guide.html - Created from tools/output/Guide.md * tools/output/Example.sh - Created from Example.json * tools/output/Example.md - Created from output of tools/output/Example.sh * Example.html - Created from tools/output/Example.md * Run.js - Created from Example.json and used in Run.html ## Author Stephen E Slevinski Jr slevin@signpuddle.net http://slevinski.github.io http://www.slideshare.net/StephenSlevinski/presentations ## Reference The Formal SignWriting character encoding used in SignMaker is defined in an Internet Draft submitted to the IETF: [draft-slevinski-signwriting-text]. The document is improved and resubmitted every 6 months. The character design has been stable since January 12, 2012. The current version of the Internet Draft is 06. The next version is planned for May 2016. ## Epilogue This is a work in progress. Feedback, bug reports, and patches are welcomed. ## License MIT ## To Do * expand API for users * expand API for create, update, and delete ## Version History * 1.3.0 - May 2nd, 2016: new world group, added listings for puddle signs and terms * 1.2.0 - Dec 17th, 2015: list puddles, download databases, custom limits, sorting, and date retrieval * 1.1.0 - Nov 25th, 2015: added query and search for puddle data * 1.0.0 - Nov 5th, 2015: initial public release [draft-slevinski-signwriting-text]: http://tools.ietf.org/html/draft-slevinski-signwriting-text [SignWriting 2010 Fonts]: https://github.com/Slevinski/signwriting_2010_fonts [SignWriting List]: http://www.signwriting.org/forums/swlist/ [SignPuddle Online]: http://signpuddle.org [SignWriting 2010 JavaScript Library]: http://slevinski.github.io/sw10js/
Edit Site Info

What technologies does signpuddle.net use?

These are the technologies used at signpuddle.net. signpuddle.net has a total of 10 technologies installed in 7 different categories.
Web Servers
Apache HTTP Server Apache HTTP Server
UI frameworks
Bootstrap Bootstrap
Operating Systems
CentOS CentOS
CDN
cdnjs cdnjs
CloudFlare CloudFlare
JavaScript Libraries
jQuery jQuery
Web Server Extensions
mod_dav mod_dav
mod_ssl mod_ssl
OpenSSL OpenSSL
Programming Languages
PHP PHP

signpuddle.net Traffic Analysis

There's no enough data about signpuddle.net traffic.
Daily Visitors n/a
Monthly Visits n/a
Pages per Visit n/a
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Visits:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
 n/a
HypeRank:
n/a
*All traffic values are estimates only.
Last update was 70 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with signpuddle.net in any way. Only publicly available statistics data are displayed.

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  signpuddle.net
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
signpuddle.net
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
signpuddle.net
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
signpuddle.net
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is signpuddle.net hosted? ▼

Signpuddle.net may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
104.168.144.56
ASN:
AS54290 
ISP:
Hostwinds LLC. 
Server Location:

United States, US
 

Other sites hosted on 104.168.144.56

How fast does signpuddle.net load? ▼

The average loading time of signpuddle.net is 206 ms. The Desktop speed index is 99 and mobile speed index is 98.
Average Load Time:
206 ms

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Lab Data

Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Time to Interactive 0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Use efficient cache lifetimes  
A long cache lifetime can speed up repeat visits to your page. Learn more
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric

Page Speed (Google PageSpeed Insights) - Mobile

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s)Largest Contentful Paint (LCP) 0%

Lab Data

Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Use efficient cache lifetimes  
A long cache lifetime can speed up repeat visits to your page. Learn more
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive 2.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric

Does signpuddle.net use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on signpuddle.net are reduced by 75%.
signpuddle.net use gzip compression.
Original size: 19.06 KB
Compressed size: 4.69 KB
File reduced by: 14.37 KB (75%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. signpuddle.net has 62 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  62
Safety Confidence:
  4

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. signpuddle.net supports HTTPS.
 signpuddle.net supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.signpuddle.net
Organization:
Location:
Issuer: R10
Valid from: Apr 29 06:58:49 2025 GMT
Valid until: Jul 28 06:58:48 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 signpuddle.net does not support HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
Date: Wed, 07 May 2025 17:46:22 GMT
Server: Apache/2.2.15 (CentOS) DAV/2 PHP/5.4.45 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips
X-Powered-By: SignWriting Server
Access-Control-Allow-Origin: *
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 4801
Content-Type: text/html;charset=utf-8

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
SOA 10800
Mname ns1.signpuddle.net
Rname postmaster.signpuddle.net
Serial Number 2021110230
Refresh 21600
Retry 3600
Expire 604800
Minimum TTL 86400
TXT google-site-verification=o_tjaqils6ad7-szsuwewb_r_wnu9iosua74j0nspek 86400
MX alt1.aspmx.l.google.com 3600
MX alt3.aspmx.l.google.com 3600
MX aspmx.l.google.com 3600
MX alt2.aspmx.l.google.com 3600
MX alt4.aspmx.l.google.com 3600
A 104.168.144.56 3313
NS cns65080-2.hostwindsdns.com 172513
NS cns65080-1.hostwindsdns.com 172513

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on April 23, 2005 and will expire on April 23, 2026 if not renewed. This website is now assigned through the registrar Pair Domains. The WHOIS data for this website's domain was last updated on March 24, 2025.
Domain Created:
2005-04-23
Domain Expires:
2026-04-23
Domain Updated:
2025-03-24
Domain Age:
20 years 2 months 24 days
Domain Registrar:
Pair Domains
Domain Owner:
GDPR Redacted
WhoIs:
 

    Domain Name: signpuddle.net
    Registry Domain ID: 152478877_DOMAIN_NET-VRSN
    Registrar WHOIS Server: pairdomains.com
    Registrar URL: pairdomains.com
    Updated Date: 2025-03-24T09:15:27+0000Z
    Creation Date: 2005-04-23T16:47:02+0000Z
    Registrar Registration Expiration Date: 2026-04-23T16:47:02+0000Z
    Registrar: Pair Domains
    Registrar IANA ID: 99
    Registrar Abuse Contact Email: email
    Registrar Abuse Contact Phone: +1.4123815195
    Domain Status: ok https://icann.org/epp#ok
    Registrant Name: GDPR Redacted
    Registrant Organization: 
    Registrant Street: GDPR Redacted
    Registrant City:  GDPR Redacted
    Registrant State/Province: PA
    Registrant Postal Code: GDPR Redacted
    Registrant Country: US
    Registrant Phone: GDPR Redacted
    Registrant Fax: GDPR Redacted
    Registrant Email: https://whois.pairdomains.com/contact?domain=signpuddle.net&type=registrant

    Admin Name: GDPR Redacted
    Admin Organization: GDPR Redacted
    Admin Street: GDPR Redacted
    Admin City:  GDPR Redacted
    Admin State/Province: GDPR Redacted
    Admin Postal Code: GDPR Redacted
    Admin Country: GDPR Redacted
    Admin Phone: GDPR Redacted
    Admin Email: https://whois.pairdomains.com/contact?domain=signpuddle.net&type=admin

    Tech Name: GDPR Redacted
    Tech Organization: GDPR Redacted
    Tech Street: GDPR Redacted
    Tech City:  GDPR Redacted
    Tech State/Province: GDPR Redacted
    Tech Postal Code: GDPR Redacted
    Tech Country: GDPR Redacted
    Tech Phone: GDPR Redacted
    Tech Email: https://whois.pairdomains.com/contact?domain=signpuddle.net&type=tech

    Name Server: CNS65080-1.HOSTWINDSDNS.COM
    Name Server: CNS65080-2.HOSTWINDSDNS.COM
    DNSSEC: unsigned
    URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
    >>> Last update of WHOIS database: 2025-05-07T17:22:21+0000Z