Check DNS, Urls + Redirects, Certificates and Content of your Website

0 in Queue, 0 of max. 8 Checks (16:33:35)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A

 

Top config

 

Checked:
20.06.2019 23:05:15

 

Older results

 

A - 20.06.2019 15:24:40
O - 20.06.2019 14:39:35
O - 20.05.2019 12:41:36
T - 20.05.2019 12:38:31
O - 20.05.2019 11:07:30
O - 17.05.2019 17:33:55
O - 17.05.2019 17:06:32
N - 17.05.2019 16:59:21
N - 17.05.2019 13:37:20
N - 17.05.2019 13:29:22

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
wpmss.com
A
35.198.176.205
Mountain View/California/US
Hostname: 205.176.198.35.bc.googleusercontent.com
yes
2
0

AAAA

yes


www.wpmss.com
CNAME
wpmss.com
yes
1
0

A
35.198.176.205
Mountain View/California/US
Hostname: 205.176.198.35.bc.googleusercontent.com
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 25266, Flags 256






Public Key with Algorithm 8, KeyTag 59944, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2019, 00:00:00 +, Signature-Inception: 20.06.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: com

com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.07.2019, 17:00:00 +, Signature-Inception: 20.06.2019, 16:00:00 +, KeyTag 25266, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 25266 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 3800, Flags 256






Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.06.2019, 18:25:33 +, Signature-Inception: 11.06.2019, 18:20:33 +, KeyTag 30909, Signer-Name: com






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: wpmss.com

wpmss.com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner wpmss.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 27.06.2019, 04:41:24 +, Signature-Inception: 20.06.2019, 03:31:24 +, KeyTag 3800, Signer-Name: com






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 3800 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 3149, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 61381, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner wpmss.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2019, 09:37:15 +, Signature-Inception: 17.06.2019, 09:37:15 +, KeyTag 3149, Signer-Name: wpmss.com






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 3149 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 3149, DigestType 2 and Digest "Gm261DGU2/8rhWmzFybw2qaJhCAAA0+IWTXQEUpAdyw=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone






RRSIG Type 1 validates the A - Result: 35.198.176.205
Validated: RRSIG-Owner wpmss.com., Algorithm: 8, 2 Labels, original TTL: 120 sec, Signature-expiration: 09.07.2019, 09:37:15 +, Signature-Inception: 17.06.2019, 09:37:15 +, KeyTag 61381, Signer-Name: wpmss.com






RRSIG Type 16 validates the TXT - Result: google-site-verification=dIDdsw1A0sqwGLT4xwK0UGynQ-ykpHdLq7FPsBApcHI
Validated: RRSIG-Owner wpmss.com., Algorithm: 8, 2 Labels, original TTL: 120 sec, Signature-expiration: 09.07.2019, 09:37:15 +, Signature-Inception: 17.06.2019, 09:37:15 +, KeyTag 61381, Signer-Name: wpmss.com






RRSIG Type 257 validates the CAA - Result: 5|issueletsencrypt.org
Validated: RRSIG-Owner wpmss.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 09.07.2019, 09:37:15 +, Signature-Inception: 17.06.2019, 09:37:15 +, KeyTag 61381, Signer-Name: wpmss.com






RRSIG Type 50, expiration 2019-07-09 09:37:15 + validates the NSEC3 RR that proves the not-existence of the CNAME RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA






RRSIG Type 50, expiration 2019-07-09 09:37:15 + validates the NSEC3 RR that proves the not-existence of the AAAA RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA






RRSIG Type 50, expiration 2019-07-09 09:37:15 + validates the NSEC3 RR that proves the not-existence of the TLSA RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA



Zone: www.wpmss.com

www.wpmss.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
wpmss.com
•  ns-cloud-c1.googledomains.com
216.239.32.108
Bellevue/Nebraska/US		•

• 
2001:4860:4802:32::6c
Mountain View/California/US		•

•  ns-cloud-c2.googledomains.com
216.239.34.108
Bellevue/Nebraska/US		•

• 
2001:4860:4802:34::6c
Mountain View/California/US		•

•  ns-cloud-c3.googledomains.com
216.239.36.108
Bellevue/Nebraska/US		•

• 
2001:4860:4802:36::6c
Mountain View/California/US		•

•  ns-cloud-c4.googledomains.com
216.239.38.108
Bellevue/Nebraska/US		•

• 
2001:4860:4802:38::6c
Mountain View/California/US		•
com
•  a.gtld-servers.net
•

•  b.gtld-servers.net
•

•  c.gtld-servers.net
•

•  d.gtld-servers.net
•

•  e.gtld-servers.net
•

•  f.gtld-servers.net
•

•  g.gtld-servers.net
•

•  h.gtld-servers.net
•

•  i.gtld-servers.net
•

•  j.gtld-servers.net
•

•  k.gtld-servers.net
•

•  l.gtld-servers.net
•

•  m.gtld-servers.net
•

 

4. SOA-Entries


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1561064694
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:9


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1561064709
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:wpmss.com
Zone-Name:
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://wpmss.com/
35.198.176.205
301
https://wpmss.com/

0.083
A
Date: Thu, 20 Jun 2019 21:06:02 GMT
Server: Apache
Location: https://wpmss.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://www.wpmss.com/
35.198.176.205
301
https://www.wpmss.com/

0.080
A
Date: Thu, 20 Jun 2019 21:06:02 GMT
Server: Apache
Location: https://www.wpmss.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://www.wpmss.com/
35.198.176.205
301
https://wpmss.com/

0.293
A
Date: Thu, 20 Jun 2019 21:06:03 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubDomains
Location: https://wpmss.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://wpmss.com/
35.198.176.205
200


0.413
A
Date: Thu, 20 Jun 2019 21:06:03 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubDomains
Link: <https://wpmss.com/wp-json/>; rel="https://api.w.org/",<https://wpmss.com/>; rel=shortlink
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

• http://wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.198.176.205
301
https://wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.093
A
Visible Content:
Date: Thu, 20 Jun 2019 21:06:04 GMT
Server: Apache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Location: https://wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://www.wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.198.176.205
301
https://www.wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.086
A
Visible Content:
Date: Thu, 20 Jun 2019 21:06:04 GMT
Server: Apache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Location: https://www.wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://www.wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

301
https://wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.264
A
Visible Content:
Date: Thu, 20 Jun 2019 21:06:05 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubDomains
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Location: https://wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://wpmss.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404


0.343
A
Not Found
Visible Content:
Date: Thu, 20 Jun 2019 21:06:04 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubDomains
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <https://wpmss.com/wp-json/>; rel="https://api.w.org/"
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

 

7. Comments


1. General Results, most used to calculate the result

Aname "wpmss.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 63072000 seconds = 730 days
AGood: HSTS has includeSubdomains - directive
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://wpmss.com/ 35.198.176.205
301
https://wpmss.com/
Correct redirect http - https with the same domain name
Ahttp://www.wpmss.com/ 35.198.176.205
301
https://www.wpmss.com/
Correct redirect http - https with the same domain name

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 61070 milliseconds, 61.070 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
wpmss.com
35.198.176.205
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
wpmss.com
35.198.176.205
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=wpmss.com


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


www.wpmss.com
35.198.176.205
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

www.wpmss.com
35.198.176.205
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=wpmss.com


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


wpmss.com
wpmss.com
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

wpmss.com
wpmss.com
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=wpmss.com


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


www.wpmss.com
www.wpmss.com
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

www.wpmss.com
www.wpmss.com
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=wpmss.com


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=wpmss.com
17.05.2019
15.08.2019
2097 days expired		wpmss.com, wpmss.wpmss-multisite.com, www.wpmss.com - 3 entries
1.
1.
CN=wpmss.com
17.05.2019

15.08.2019
2097 days expired


wpmss.com, wpmss.wpmss-multisite.com, www.wpmss.com - 3 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:035441B3D8262909951D48258FA3385E97D5
Thumbprint:66C5A78E571B683CE1A429AA967738551431B309
SHA256 / Certificate:JnzQxbnFE0EWrDrms4qsqOas3a51kuP27vZ84cYS4Xw=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):4f4877686dff2b7ddce824be4d59a71e2cc6dfae1aff6f2eccce6f65a43f9bfa
SHA256 hex / Subject Public Key Information (SPKI):4f4877686dff2b7ddce824be4d59a71e2cc6dfae1aff6f2eccce6f65a43f9bfa
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1517 days expired

2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1517 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1320 days expired

3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1320 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute

 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.wpmss.com
5
issue
letsencrypt.org
1
0
wpmss.com
5
issue
letsencrypt.org
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
wpmss.com
google-site-verification=dIDdsw1A0sqwGLT4xwK0UGynQ-ykpHdLq7FPsBApcHI
ok
1
0
www.wpmss.com
google-site-verification=dIDdsw1A0sqwGLT4xwK0UGynQ-ykpHdLq7FPsBApcHI
ok
1
0
_acme-challenge.wpmss.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.wpmss.com

Name Error - The domain name does not exist
1
0
_acme-challenge.wpmss.com.wpmss.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.wpmss.com.wpmss.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.wpmss.com.www.wpmss.com

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

 

 

Permalink: https://check-your-website.server-daten.de/?i=6fc46941-ae79-4122-a46a-5549278b1722

 

Last Result: https://check-your-website.server-daten.de/?q=wpmss.com - 2019-06-20 23:05:15

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=wpmss.com" target="_blank">Check this Site: wpmss.com</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=wpmss.com

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions