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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
25.04.2019 23:31:26


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
buildingmanagementsolutionsinc.com
A
23.239.211.110
No Hostname found
yes
2
0

AAAA

yes


www.buildingmanagementsolutionsinc.com
CNAME
buildingmanagementsolutionsinc.com
yes
1
0

A
23.239.211.110
No Hostname found
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 12.05.2019, 00:00:00 +, Signature-Inception: 21.04.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: 08.05.2019, 20:00:00 +, Signature-Inception: 25.04.2019, 19: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: 07.05.2019, 18:25:33 +, Signature-Inception: 22.04.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: buildingmanagementsolutionsinc.com
buildingmanagementsolutionsinc.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "ggcejfpp0g6ombh6gq8rht019kd86ag6" between the hashed NSEC3-owner "ggce39j7q2n26rj83a90hm8649iqakgo" and the hashed NextOwner "ggcesfjlj2qltb5npq1lvmr7c9bknls6". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ggce39j7q2n26rj83a90hm8649iqakgo.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.04.2019, 04:41:05 +, Signature-Inception: 22.04.2019, 03:31:05 +, KeyTag 3800, Signer-Name: com



0 DNSKEY RR found




Zone: www.buildingmanagementsolutionsinc.com
www.buildingmanagementsolutionsinc.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
buildingmanagementsolutionsinc.com
X  dns1.name-services.com / pdns22.dns.sjl.prod.tucows.net
98.124.243.1

X 
2620:10f:5000:5002:98:124:243:1

  dns2.name-services.com / pdns23.dns.ash.prod.tucows.net
64.98.151.1

T 
2604:4000:4000:0:64:98:151:1

X  dns3.name-services.com / pdns22.dns.sjl.prod.tucows.net
98.124.243.2

X 
2620:10f:5000:5002:98:124:243:2

  dns4.name-services.com / pdns23.dns.ash.prod.tucows.net
64.98.151.2

X 
2604:4000:4000:0:64:98:151:2

X  dns5.name-services.com / pdns22.dns.sjl.prod.tucows.net
98.124.243.3

X 
2620:10f:5000:5002:98:124:243:3
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:1556227856
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


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


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


Domain:buildingmanagementsolutionsinc.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:buildingmanagementsolutionsinc.com
Zone-Name:
Primary:dns1.name-services.com
Mail:info.name-services.com
Serial:1552152062
Refresh:172800
Retry:900
Expire:1814400
TTL:3600
num Entries:9


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://www.buildingmanagementsolutionsinc.com/
23.239.211.110
301
http://buildingmanagementsolutionsinc.com/
0.264
D
Server: nginx
Date: Thu, 25 Apr 2019 21:39:22 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: http://buildingmanagementsolutionsinc.com/
X-Powered-By: PleskLin

• http://buildingmanagementsolutionsinc.com/
23.239.211.110
200

0.837
H
Server: nginx
Date: Thu, 25 Apr 2019 21:39:21 GMT
Content-Type: text/html
Content-Length: 105068
Last-Modified: Thu, 10 Jan 2019 06:37:26 GMT
Connection: close
ETag: "5c36e826-19a6c"
X-Powered-By: PleskLin
Accept-Ranges: bytes

• https://www.buildingmanagementsolutionsinc.com/
23.239.211.110
301
https://buildingmanagementsolutionsinc.com/
1.266
B
Server: nginx
Date: Thu, 25 Apr 2019 21:39:25 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://buildingmanagementsolutionsinc.com/
X-Powered-By: PleskLin

• https://buildingmanagementsolutionsinc.com/
23.239.211.110
200

2.050
I
Server: nginx
Date: Thu, 25 Apr 2019 21:39:23 GMT
Content-Type: text/html
Content-Length: 105068
Last-Modified: Thu, 10 Jan 2019 06:37:26 GMT
Connection: close
ETag: "5c36e826-19a6c"
X-Powered-By: PleskLin
Accept-Ranges: bytes

• http://www.buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
23.239.211.110
301
http://buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.263
D
Visible Content:
Server: nginx
Date: Thu, 25 Apr 2019 21:39:27 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: http://buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Powered-By: PleskLin

• http://buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
23.239.211.110
404

0.313
A
Not Found
Visible Content:
Server: nginx
Date: Thu, 25 Apr 2019 21:39:26 GMT
Content-Type: text/html
Content-Length: 162
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "buildingmanagementsolutionsinc.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: one preferred version: non-www is preferred
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (3 urls)
http://buildingmanagementsolutionsinc.com/ 23.239.211.110


Url with incomplete Content-Type - header - missing charset
https://buildingmanagementsolutionsinc.com/ 23.239.211.110


Url with incomplete Content-Type - header - missing charset
http://buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.239.211.110


Url with incomplete Content-Type - header - missing charset
Bhttps://buildingmanagementsolutionsinc.com/ 23.239.211.110
200

Missing HSTS-Header
Bhttps://www.buildingmanagementsolutionsinc.com/ 23.239.211.110
301

Missing HSTS-Header
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Dhttp://www.buildingmanagementsolutionsinc.com/ 23.239.211.110
301
http://buildingmanagementsolutionsinc.com/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.239.211.110
301
http://buildingmanagementsolutionsinc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Ihttps://buildingmanagementsolutionsinc.com/ 23.239.211.110
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: dns4.name-services.com / 2604:4000:4000:0:64:98:151:2: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
XFatal error: Nameserver doesn't support TCP connection: dns1.name-services.com / 98.124.243.1: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
XFatal error: Nameserver doesn't support TCP connection: dns3.name-services.com / 98.124.243.2: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
XFatal error: Nameserver doesn't support TCP connection: dns5.name-services.com / 98.124.243.3: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
XFatal error: Nameserver doesn't support TCP connection: dns3.name-services.com / 2620:10f:5000:5002:98:124:243:2: Fatal error (-14). Details: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
XFatal error: Nameserver doesn't support TCP connection: dns1.name-services.com / 2620:10f:5000:5002:98:124:243:1: Fatal error (-14). Details: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
XFatal error: Nameserver doesn't support TCP connection: dns5.name-services.com / 2620:10f:5000:5002:98:124:243:3: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host

2. DNS- and NameServer - Checks

AGood: Nameserver supports Echo Capitalization: 10 good Nameserver
XNameserver Timeout checking EDNS512: dns2.name-services.com / 2604:4000:4000:0:64:98:151:1
XNameserver Timeout checking EDNS512: dns4.name-services.com / 2604:4000:4000:0:64:98:151:2
Nameserver doesn't pass all EDNS-Checks: dns2.name-services.com / 2604:4000:4000:0:64:98:151:1: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok (pdns23.dns.ash.prod.tucows.net). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: dns4.name-services.com / 2604:4000:4000:0:64:98:151:2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (pdns23.dns.ash.prod.tucows.net). COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. 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: 259163 milliseconds, 259.163 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
buildingmanagementsolutionsinc.com
23.239.211.110
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
buildingmanagementsolutionsinc.com
23.239.211.110
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=buildingmanagementsolutionsinc.com

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


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

www.buildingmanagementsolutionsinc.com
23.239.211.110
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=buildingmanagementsolutionsinc.com

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


9. Certificates

1.
1.
CN=buildingmanagementsolutionsinc.com
25.04.2019
24.07.2019
1166 days expired
buildingmanagementsolutionsinc.com, www.buildingmanagementsolutionsinc.com - 2 entries
1.
1.
CN=buildingmanagementsolutionsinc.com
25.04.2019

24.07.2019
1166 days expired
buildingmanagementsolutionsinc.com, www.buildingmanagementsolutionsinc.com - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:036B7B2AAD1B8391A8E21572713832C0955D
Thumbprint:00D957B7A7C9B0B8564E639B56AC44DE4C91649C
SHA256 / Certificate:lSOgyNFQ6sUU5hFlheT1zPTU+NUp6IzChwNU8zEATvs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):f9e130b3ad7775c890a6c7ab254c0a5ab7ce25bdc63d7d666f81b1e973b37b1f
SHA256 hex / Subject Public Key Information (SPKI):f9e130b3ad7775c890a6c7ab254c0a5ab7ce25bdc63d7d666f81b1e973b37b1f
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
564 days expired


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

17.03.2021
564 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
367 days expired


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

30.09.2021
367 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)

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.


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

Small Code Update - wait one minute


12. 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.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.buildingmanagementsolutionsinc.com



1
0
buildingmanagementsolutionsinc.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
buildingmanagementsolutionsinc.com
google-site-verification=dvp48t3YblYsR8XXxJosWmBO5e379BJQMgz4Wr_Z_5c
ok
1
0
www.buildingmanagementsolutionsinc.com
google-site-verification=dvp48t3YblYsR8XXxJosWmBO5e379BJQMgz4Wr_Z_5c
ok
1
0
_acme-challenge.buildingmanagementsolutionsinc.com

missing entry or wrong length
1
0
_acme-challenge.www.buildingmanagementsolutionsinc.com

missing entry or wrong length
1
0
_acme-challenge.buildingmanagementsolutionsinc.com.buildingmanagementsolutionsinc.com

perhaps wrong
1
0
_acme-challenge.www.buildingmanagementsolutionsinc.com.www.buildingmanagementsolutionsinc.com

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. 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=704bc714-630f-4da7-86a4-befd77f89e6a


Last Result: https://check-your-website.server-daten.de/?q=buildingmanagementsolutionsinc.com - 2019-04-25 23:31:26


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

<a href="https://check-your-website.server-daten.de/?q=buildingmanagementsolutionsinc.com" target="_blank">Check this Site: buildingmanagementsolutionsinc.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